Session alternatives: private messaging without a phone number

Published 31 August 2026 by the Nyra team.

If you are searching for a Session alternative, you probably already agree with Session's core idea: a private messenger should not demand your phone number. The question is whether you can keep that without giving up the cryptographic protections Session dropped. This page walks through both halves honestly.

Disclosure first: we are building Nyra, an anonymous end-to-end encrypted messenger listed near the bottom of this page. It is in development and not downloadable yet, so we have every reason to be fair about the apps you can install today.

What Session got right

Session deserves real credit, and any honest alternatives page should start there.

• No phone number. Your identity is a random Session ID derived from keys. Registration asks for nothing personal, no number, no email. Session proved this model can work at scale, and it is the reason many people use it at all.
• Onion routing. Messages travel through a multi-hop node network, so no single relay sees both who you are and who you are talking to. That is meaningful IP-level protection most messengers do not attempt.
• Decentralization. There is no single company server to seize or subpoena. The network is run by many independent node operators, which removes a whole category of single points of failure.

The apps are open source, cross-platform, and reasonably polished. If that were the whole story, nobody would be reading this page.

Why people look for alternatives anyway

The main reason is a protocol decision. Session originally ran on the Signal Protocol. In the rework to its own Session Protocol, the team removed X3DH and the Double Ratchet, and with them forward secrecy.

Forward secrecy sounds academic and is not. In a design like Signal's, every message is encrypted with a fresh key, and old keys are deleted as the conversation moves forward. So even if one of your keys is compromised someday, the messages an attacker recorded earlier stay unreadable. One compromised key should not unlock your past.

In Session's current design, that protection was traded away. If an attacker records your encrypted traffic today and obtains your key later, through a seized device, malware, or any other path, previously captured messages can be decrypted. Session argues the simpler protocol fits its decentralized network better. It is a real engineering argument, but one that has not convinced most cryptographers, and the trade was made on your behalf. Our full comparison covers this in more detail, along with a second caveat: small closed groups in Session are end-to-end encrypted, large public communities are not.

The honest alternatives

Signal, if a phone number is acceptable

On pure cryptography, Signal is the gold standard. X3DH, the Double Ratchet, full forward secrecy, open source clients and server, independently audited and formally analyzed many times, run by a nonprofit with a long track record. The catch is the obvious one: Signal requires a phone number to register. Usernames, added in 2024, can hide the number from other users, but Signal itself still receives and verifies it. If you left Session over forward secrecy rather than the phone number, Signal is the straightforward answer. If the phone number is the whole problem, it is not.

SimpleX Chat, the strongest released option with no identifiers

SimpleX goes further than Session on the identity axis: it has no identifiers at all, not even a random ID. Contacts connect through one-time links or QR codes, and each conversation runs over its own message queues, making it hard for servers to correlate your chats. Crucially for anyone leaving Session over the protocol, SimpleX has full forward secrecy, and it is open source and independently audited. It also offers a self-destruct passcode: enter it at the lock screen and the app opens to an empty profile instead of your real one. The cost is friction, since no stable identity makes adding contacts and using multiple devices more work.

Briar, no server at all

Briar removes the server entirely. It is peer-to-peer, syncing over Tor when you have internet and over Wi-Fi or Bluetooth when you do not, which makes it uniquely resilient during shutdowns. No phone number, no central anything. The tradeoffs: no iOS app (mobile means Android, though a desktop version exists), messages arrive only when both peers are reachable, and battery use is real. A specialist tool, superb at its specialty.

Nyra, in development

Nyra is our attempt to keep what Session got right and restore what it gave up. Registration is a username plus keys derived from a recovery phrase, no phone number, no email, nothing to hand over. The protocol is X3DH plus the Double Ratchet, the Signal construction with forward secrecy intact, built on independently audited cryptographic primitives. Messages disappear by default after 7 days, and the dead switch, a panic PIN that wipes the app, is built into the app build. The security page explains the design in full.

The caveats, stated plainly: Nyra is in development, not released. The code is not yet public, and while the primitives are audited, an independent audit of Nyra itself is planned before launch, meaning it has not happened yet. Judge it when it ships.

Which should you pick?

• The phone number was never your problem: Signal. Best cryptography available, mature, audited, widely used.
• No identifiers and full forward secrecy, today: SimpleX, if you will accept the extra friction.
• You expect network shutdowns or want no server involved: Briar, on Android.
• Session's model with Signal's protocol: that is what Nyra is being built for. Until it ships, pick from the three above; our no-phone-number guide covers the wider field.

Frequently asked questions