Most messengers assign every account a persistent identifier: a phone number, username, public key or internal ID. SimpleX takes a different approach. It creates separate pairwise message queues for connections, so the network does not need one identifier representing a user across all conversations.
This design targets metadata—the information about who communicates with whom—not only message content.
Key takeaways
- No global user profile ID exists at the protocol level. Contacts use pairwise connection data rather than one reusable network identity.
- Relay servers store undelivered data, not user accounts. Messages remain end-to-end encrypted.
- User data primarily lives on devices. Backup and transfer are the user’s responsibility.
- No identifier does not mean perfect anonymity. Devices, IP traffic, notification services, contacts and public behavior can still reveal information.
How messages are routed
SimpleX Messaging Protocol uses unidirectional queues. Sending and receiving can use separate queues and servers, reducing the shared identifiers an observer could correlate. The application layer builds bidirectional conversations over those transport primitives.
Encryption and recovery
SimpleX documents double-ratchet end-to-end encryption with forward secrecy and post-compromise recovery properties. Encryption protects content, but local database protection and device security remain essential. Deleting an app or losing an unbacked-up device can mean losing profiles and history.
What the design improves
A server cannot simply query a central account table to learn every contact belonging to a user. One-time and temporary invitation links also reduce unsolicited contact. Users can choose relay operators or run their own infrastructure.
Where privacy can still fail
- A compromised device can expose decrypted messages and contacts.
- Push notifications may introduce platform metadata.
- An IP address may be visible to a relay unless transport protection such as Tor is used.
- A contact can screenshot, forward or disclose a conversation.
- Public groups protect participation differently from private chats.
Privacy products earn trust by defining limits as clearly as features. Crynet helps technical teams explain those boundaries through Web3 positioning and messaging.
Sources
This article explains documented architecture and does not guarantee anonymity in every threat model.
