Session: encrypted messaging without a phone number or account

Signal is better than WhatsApp. But Signal requires an account, and that account is tied to a phone number. You can now hide your number from other users, but the number itself remains the key Signal uses to know who you are.

Session: encrypted messaging without a phone number or account

Session: encrypted messaging without a phone number or account

Signal is better than WhatsApp. But Signal requires an account, and that account is tied to a phone number. You can now hide your number from other users, but the number itself remains the key Signal uses to know who you are.

Session approaches this differently. You register with nothing — no phone number, no email address, no name. You receive a random Account ID (older Session versions and many articles call it the Session ID): a long string of letters and numbers tied to nothing.


Project status (November 2026)

Session’s development nearly stopped in 2026. In June the Session Technology Foundation, the Swiss non-profit behind the app, explained that earlier in the year it had to pause development for financial reasons and cut its costs close to zero, which meant losing all its employees. After a donation campaign it has enough money to continue “in some capacity”, and an update from August 2026 describes a small team of three developers. Releases have continued since: Android 1.33.7, iOS 2.15.5 and Desktop 1.18.3 came out in October 2026. The paid Session Pro launch is on hold while the foundation talks with “an allied privacy ecosystem” about long-term support (development update of 7 October 2026). The foundation itself says that without those donations it would have been winding down support: no more updates, apps removed from the app stores, and some network infrastructure going offline. The decentralised network itself can keep running without the foundation, but the apps need maintenance.

What this means for you: Session still fits if you need a messenger without a phone number and accept this risk. Keep your recovery password safe, check that the app is still receiving updates before relying on it, and do not make it your only channel. Sources: Session’s own posts The Future of Session (15 June 2026) and its development updates of 2 August, 3 September and 7 October 2026.


Who this guide is for

This guide is mainly for readers who want a persistent messenger identity without tying it to a phone number or central account.

It fits especially:

  • people who need contact without revealing a phone number
  • readers who care about onion-routed messaging enough to accept some latency and usability tradeoffs
  • users deciding between Session and other higher-friction tools such as SimpleX or Briar

For most normal readers, Session is not the first messaging step. Signal remains the better mainstream default unless the phone-number requirement is itself the problem.


What you gain, and what it costs

If you use Session, you usually gain:

  • messaging without a phone number or email address
  • a persistent identity you can recover across devices
  • onion-routed transport without relying on a single central operator

But it costs something:

  • slower and less polished communication than Signal
  • a smaller user base
  • no forward secrecy or post-quantum encryption in the apps yet (planned in Protocol V2)

For the right profile that is still a good trade. It becomes overkill when you mainly want everyday convenience or when your contacts are unlikely to move with you.


How Session works

On first launch, the app generates a cryptographic key pair and a corresponding Account ID. That ID is your identity in the network — and nothing more. No name, no number, no account on a server.

To make contact, you share your Account ID or let someone scan a QR code. There is no phonebook integration — you cannot “find” anyone in the system, unless they registered a name in Session’s name service (ONS) and gave it to you.

Messages do not pass through central servers. Session uses a decentralised network of Session Nodes run by independent operators worldwide, who stake Session Token to take part. Messages are sent via onion requests: each request passes through several nodes, each peeling off one layer of encryption, so that no single node knows both where a message comes from and where it goes. Messages wait for the recipient on a small group of nodes (a swarm) for up to 14 days.

A few parts do use servers run by the Session Technology Foundation: attachments are stored encrypted on the Session File Server (reached through onion requests), and with the mobile Fast Mode notifications your Account ID and push token are registered with the foundation’s push server, while Google or Apple see your IP address. Slow Mode avoids that, at the cost of delayed notifications.

This is similar to how Tor works — but for messaging.


What Session protects

Signal Session
Message content Encrypted Encrypted
Phone number required Yes No
Central server Yes (Signal Foundation) No central message server (decentralised node network); file server and push server run by the foundation
Onion routing No Yes
Legally compellable data Registration date + last connection date No account, no central log of who messages whom
Forward secrecy Yes No; planned via Protocol V2, not released yet
Post-quantum encryption Yes (PQXDH since 2023, plus the SPQR triple ratchet since 2025) Planned via Protocol V2, not released yet
Account recoverable Via number/device Via recovery password (a word list)

Session cannot respond to a legal order with your phone number or account details — because they simply don’t exist. The message network has no central operator that can be subpoenaed. The foundation does run the file and push servers mentioned above, and publishes transparency reports.


Honest caveats

Perfect Forward Secrecy (PFS) — this is a cryptographic property that ensures encryption keys are regularly rotated and old ones deleted. If a key is ever compromised, previously sent messages remain safe.

The current Session apps have no PFS. Session started on the Signal protocol, which has it, but dropped it when it switched to its own Session Protocol in 2020-21. That has been a serious criticism, and rightfully so: someone who stores encrypted messages and later gets hold of your long-term key could decrypt that history. Session Protocol V2 is meant to fix this: account and device keys that rotate roughly every 12 hours and are forgotten after 16 days, plus post-quantum encryption that combines the NIST-standardised ML-KEM-768 (the same standard Signal and iMessage use) with X25519. In its update of 13 October 2026 Session says the specification is public and the core encryption for one-to-one messages is implemented in its shared library, but it is not yet in the apps. The October 2026 releases (iOS 2.15.5, Android 1.33.6 and Desktop 1.18.2 onwards) only recognise V2 messages and ask you to update. An invite-only alpha app is still being explored, forward secrecy would only apply when both people use it, and after release a grace period of at least six months keeps the old protocol working.

Use the latest available Session version, but treat PFS and post-quantum protection as a roadmap promise for now, not something already protecting your messages today.

Recovery password — your Account ID and keys are stored locally. The only way to restore your account on a new device is the recovery password, a list of words (a seed phrase). If you lose it, you permanently lose access to your account. Restoring brings back contacts and groups only if one of your devices was online in the past 30 days, and only messages from the past 14 days. Store the recovery password safely — in KeePassXC or on paper in a secure location.

Performance — onion routing adds latency. Messages are slightly slower than Signal or WhatsApp. For normal conversations this is barely noticeable, but with real-time conversations or a poor connection it can become apparent.

Smaller user base — Session has fewer users than Signal. The smaller the network, the more it stands out when someone uses it at all. In high-risk situations, that’s a consideration.


Installing and getting started

Session is available for Android, iOS, and desktop (Linux, macOS, Windows).

Android: via Google Play, as an APK from the Session website or GitHub, or through Session’s own F-Droid repository (https://fdroid.getsession.org/fdroid/repo, add it in F-Droid; the repo page shows the fingerprint). The F-Droid route is the one without Google Play.

iOS: via the App Store.

Desktop: download from getsession.org/download (Windows, macOS for Apple Silicon and Intel, Linux).

This assumes a fresh setup. Already have a Session account? Choose I have an account instead and enter your recovery password.

On first launch:

  1. Choose Create account — no email or number required
  2. At Pick your display name, enter a name and choose Continue. Your display name is visible to the people, groups and communities you interact with, and you can change it at any time. On Android and iOS a Message notifications screen follows: Fast Mode (via Google or Apple push, see above) or Slow Mode (Session checks for messages now and then in the background); choose one and Continue
  3. Save your recovery password straight away: the app does not show it during setup. On the main screen, choose Continue on the Save your recovery password banner, or open Settings → Recovery Password, and write the words down. You can view it there again later, unless you choose Hide Recovery Password Permanently

On Android and iOS your Account ID is shown in Settings under Your Account ID. Share it with people you want to message, or let them scan your QR code.


What you can do with it

  • Personal conversations (1 on 1)
  • Group conversations (closed groups and open communities)
  • Voice messages
  • File sharing
  • Disappearing messages (configurable per conversation)

Voice and video calls exist, but as a beta that is off by default: you switch on Voice and Video Calls (Beta) in the Privacy settings. Calls are end-to-end encrypted but not onion-routed: they run peer-to-peer, so your IP address is visible to the person you call and to a STUN/TURN server run by the Session Technology Foundation. You can only call people in your contacts, and only one-to-one.


Who Session is for

Direct value:

  • Journalists and sources who want contact without linking a phone number
  • Activists in countries with surveillance infrastructure
  • People who want to message someone without revealing their phone number to each other
  • Anyone skeptical of central parties — the Signal Foundation, however trustworthy, is still a single point of failure
  • IT professionals reaching clients without sharing a personal number

Less suitable for:

  • Daily use where speed matters (onion routing adds latency)
  • People who want to find contacts easily (no phonebook)
  • Situations where nobody around you uses Session — the switching threshold is real

Session vs. SimpleX

Both apps work without a phone number. The difference lies in how identity works.

Session gives you a persistent Account ID — one identity you can restore across multiple devices via your recovery password. Convenient, but it also means that ID can become easier to correlate over time if someone follows metadata patterns long enough.

SimpleX has no user identifier. Every connection gets its own queues. There’s no account to trace, but also nothing to recover without your own export. You choose based on your profile: do you want recoverability or maximum anonymity?


Background: decentralization and governance

Session was developed under the OPTF (Oxen Privacy Tech Foundation), an Australian non-profit. On 15 October 2024 Session announced that a new Swiss foundation, the Session Technology Foundation, would steward the app from then on — Switzerland is also home to Threema and Proton. Session gave the Australian regulatory climate around privacy technology and encrypted messaging as the reason, and calls Swiss privacy regulation some of the most robust in the world; how much that helps against a specific legal request is our open question, not something the foundation spells out.

The node network itself moved in May 2025 from the Oxen Service Node Network to the new Session Network, whose nodes stake Session Token. You never need the token to use Session.

An independent security audit by Quarkslab (Android, iOS, Desktop) was published in April 2021: Session calls the result cryptographically sound; Quarkslab raised 16 issues, the only severe one a TLS-verification issue on Android that has since been fixed. That audit predates the move to the Session Network and Protocol V2. Session’s audit page and FAQ still name only this 2021 audit; we found no newer one on Session’s own pages.

Next step

Alternatives

Reviews