The problem with “secure” messengers
If there is any server, relay, or bootstrap node, you must trust it. Trust is a vulnerability.
- Metadata: servers know who talks, when, how often.
- Compromise: servers can be hacked or seized.
- False promises: “we don’t store” — unverifiable.
- Control: servers can censor, block, rate-limit.
- Signal: E2EE is strong, but all delivery and presence still go via Signal servers.
- Telegram: most chats are cloud-stored (not E2EE), and even Secret Chats depend on Telegram infrastructure.
- Matrix / Element: federated servers; you must trust your homeserver and its operators.
Pure P2P: no middlemen, no trust
Each app runs its own tiny server. Messages live only on the two devices. That’s it.
- No servers: nothing and no one in the middle.
- Local storage only: your device = your archive.
- No metadata: no third-party logs, no exhaust.
- Honest trade-off: privacy prioritized over comfort.
Mobile & desktop constraints
Delivery timing
Messages deliver only when both peers are online. Otherwise they remain queued locally.
No push
OS push = central servers. We don’t use them. You see new messages when you open the app and your peer is online.
Sleep / power
Sleeping or powered-off devices cannot accept messages. That’s the cost of no middlemen.
Ready for honest privacy?
Join the community and help shape the pure P2P messenger.