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
| Property | Cloud messengers | FLVSH |
|---|---|---|
| Infrastructure | Their servers, their uptime, their rules | No servers: the phones in the room are the network |
| Identity | Phone number or email required | X25519 keypair generated on device — no signup |
| Works offline | Dead without internet | Built for airplane mode: BLE only, end to end |
| Metadata | Who, when, how often — logged server-side | Nothing to log with: traffic never leaves the mesh |
| Encryption | E2E, but the operator routes every byte | ChaCha20-Poly1305; relays see only ciphertext |
| Message history | Cloud backups you don't control | Local SQLite only, with disappearing messages |
| Range | Global, while the grid is up | The room by radio, the crowd by mesh relay |
The cryptography is deliberately boring: X25519 key agreement and ChaCha20-Poly1305 authenticated encryption from audited 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.