GitHub Repos intermediate 3 min read Jun 30, 2026
Public Preview Sign in free for the full digest →

SimpleX Chat: Private Messaging With No Phone Number or Account

“The server that hosts your messages received 12 government data requests in 2025 and replied to zero — not by refusing, but because it had nothing to hand over.”

SimpleX Chat: Private Messaging With No Phone Number or Account
1 Views
0 Likes
0 Bookmarks
Source · github.com

“"SimpleX Chat network can grow into a de facto Internet standard for private and secure communications for both businesses and individual users." — Asymmetric Capital Partners (simplex.chat blog, August 2024, https://simplex.chat/blog/20240814-simplex-chat-vision-funding-v6-priv...”

You know that feeling when you sign up for a messaging app and it demands your phone number, links your account to it, and stores your contact graph on a server you don't control? Every major private messenger — Signal, Telegram, WhatsApp — ties your account to a phone number or at minimum a persistent random ID that relay servers log. Even when messages are end-to-end encrypted, the metadata pattern — who talks to whom, how often — is visible to the relay through your account identifier. A single server breach or legal demand can expose your social graph even if every message stays unreadable.

privacyencryptionmessaginge2eeopen-sourcehaskellsecurity

When you want to connect with someone, you generate a one-time link — like a self-destructing access code. The recipient uses it to open a connection, and both of you get a private channel backed by a pair of disposable message queues on a relay server. The relay sees a queue ID but cannot link two queues belonging to the same person. Messages arrive encrypted, the recipient picks them up, and the server deletes them. For encryption, every single message exchange rotates keys using the double-ratchet algorithm extended with post-quantum key agreement at each step — not just at session setup — so intercepted traffic stays locked even if a quantum computer arrives later. Your contact list, message history, and local profile live only on your device in an encrypted SQLite database.

01
Zero user identifiers at the protocol level — the relay server sees only a queue ID, not your account, phone number, or username; there is nothing to subpoena or leak from the server side
02
Post-quantum double-ratchet at every message exchange, not just at session setup — a quantum computer that breaks today's keys cannot retroactively decrypt any past message from any session
03
Self-hostable SMP relay servers — run your own relay with a single binary and switch which relays your conversations use at any time, removing dependency on SimpleX Chat Ltd. infrastructure
04
Two Trail of Bits security audits with published findings — 2022: 2 medium, 2 low severity; 2024: 3 medium, 1 low, 3 informational — third-party reviewed with results disclosed publicly
05
Zero server-side retention verified under pressure — messages deleted after delivery; the transparency log shows 12 government data requests in 2025 and zero responses because there was nothing to hand over
06
Public channels without subscriber identity (v6.5+) — broadcast to subscribers without either side learning who the other is; your audience cannot be enumerated even by the channel owner
07
XFTP protocol for file transfer — a dedicated file transfer protocol using the same identifier-free design; large files do not get shoehorned through message queues
Who it’s for

If you are a developer building anonymous communication infrastructure — tip platforms, secure internal tooling, or messaging for high-risk contexts — SimpleX gives you an audited protocol and terminal client to build on under AGPL-3.0. It is also relevant if you study double-ratchet or post-quantum messaging protocols, or want to self-host a privacy-preserving relay for a team or community. Skip this if you need user discovery (no username search exists), guaranteed sub-second push delivery, or a widely-federated ecosystem to interoperate with — Matrix covers that use case better.

Worth exploring

SimpleX is production-stable for private one-to-one and group messaging — 4+ years of public deployment, two external audits, 17,072 GitHub stars, and daily commits as of June 2026. The HN community's main concern is the 'World's Most Secure Messaging' marketing claim, which the 2024 Trail of Bits findings (7 issues, two medium-severity accepted without fix) do not support. For the core use case of server-side social graph prevention the protocol delivers on its architectural promise; for mobile daily use, test notification delivery latency on your specific devices before committing — community reports cite delays up to 20 minutes.

Developer playbook
Tech stack, code snippet, sentiment, alternatives.
PM playbook
Adoption angles, user fit, positioning.
CEO playbook
Traction signals, ROI, build vs buy.
Deep-dive insight
Full long-form analysis, no fluff.
Easy mode
Core idea, fast — when you need the gist.
Pro mode
Technical nuance, edge cases, tradeoffs.
Read the full digest
Go beyond the preview

Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.

Underrated tools. Unfiltered takes.

Read the full digest in the Snaplyze app for deep-dive insight, Easy and Pro modes, and the playbooks you can actually use.

Install Snaplyze →