home / messaging
SimpleX
IDs
SimpleX doesn't use account IDs, but each chat has a unique message queue identifier. These chat IDs can be correlated into shadow accounts with a metadata analysis, especially when all traffic is routed through default servers.
Metadata
SimpleX doesn't have any robust metadata protection. Its "private message routing" doesn't hide your IP address from the server which you use to receive messages. In other words, using default SimpleX servers makes you vulnerable to a traffic analysis based on metadata such as an IP address and timestamps. Thus, all your chats can be clustered together into a singe shadow account, which defeats the purpose of not having account IDs.
Centralization
While self-hosting is available, most people use default servers run by SimpleX and its partners, which are officially registered compliant companies based in hostile jurisdictions.
Self-hosting
Since all SimpleX users, including those in public groups, can see the server address you choose to receive new messages, using a self-hosted server uniquely marks you as the admin or member of a certain community.
Community:
Forum:
Session vs SimpleX: fuck the fluff (20+ comments) - A detailed analysis that points out flaws in both architectures and questions legitimacy of the Trail of Bits audit. The article was written in 2025, so a few things have changed since then, but core architectures largely remain the same. Later that year, Session published a V2 roadmap featuring PFS and PQC, but the project encountered serious financial issues in 2026, making the future uncertain.