compare
The architecture is the privacy policy.
Cloud messengers promise not to look. FLVSH removes the place where looking happens: no servers, no accounts, no copy of anything outside your phone.
cloud messengers vs flvsh
- Infrastructurecloud messengersTheir servers, their uptime, their rulesflvshNo servers: the phones in the room are the network
- Identitycloud messengersPhone number or email requiredflvshX25519 keypair generated on device — no signup
- Works offlinecloud messengersDead without internetflvshBuilt for airplane mode: BLE only, end to end
- Metadatacloud messengersWho, when, how often — logged server-sideflvshNothing to log with: traffic never leaves the mesh
- Encryptioncloud messengersE2E, but the operator routes every byteflvshPost-quantum PQXDH + Double Ratchet; relays see only ciphertext
- Message historycloud messengersCloud backups you don't controlflvshLocal SQLite only, with disappearing messages
- Rangecloud messengersGlobal, while the grid is upflvshThe room by radio, the crowd by mesh relay
The cryptography is deliberately boring: a PQXDH handshake (X25519 plus ML-KEM-768) feeding a Double Ratchet, with ChaCha20-Poly1305 authenticated encryption from well-established RustCrypto implementations, in one shared Rust core compiled into both apps. No novel primitives, no proprietary protocol. Just a network made of the phones themselves.