Session
Decentralized messenger with no phone number required, onion routing, and community-run infrastructure - truly anonymous messaging
Quick Overview
| Organization | Session Technology Foundation |
|---|---|
| Category | Messaging (Decentralized) |
| Headquarters | Switzerland (Foundation) |
| EU Presence | Yes - Switzerland (European) |
| Data Centers | Decentralized (community nodes worldwide) |
| Open Source | Yes (GPLv3) |
| GDPR Compliant | Yes (no personal data collected) |
| End-to-End Encryption | Yes |
| Main Features | No phone number, onion routing, decentralized network, disappearing messages, open groups |
| Pricing | Free |
| Best For | Privacy-conscious users wanting anonymous messaging without personal identifiers |
| Replaces | WhatsApp, Signal, Telegram |
Detailed Review
Session is a decentralized messenger designed for users who want strong privacy without compromising on usability. Originally forked from Signal, Session has evolved into a distinct platform with its own network architecture and privacy model. The key innovation is that Session requires no phone number, email, or any personal information to create an account - you simply generate an anonymous Session ID and start messaging.
Swiss Foundation and Global Community
Session is developed by the OPTF (Oxen Privacy Tech Foundation), a non-profit organization originally based in Australia. In 2024, the Session Technology Foundation was established in Switzerland to provide stronger legal protection for the project and its users. Switzerland's privacy-friendly jurisdiction and political neutrality make it an ideal home for privacy-focused technology.
The network itself is decentralized and community-run. Node operators around the world, including many in Europe, run the infrastructure that routes messages. This distributed model means there's no single company or jurisdiction that controls the network - it's a global privacy commons.
Anonymous by Design
Session's core privacy feature is that it never asks for any personal information. When you create an account, you receive a randomly generated Session ID - a long string of letters and numbers. This ID is all you share with contacts. Unlike Signal or WhatsApp, there's no phone number linked to your account, so your real identity remains completely separate from your Session identity.
This anonymity is crucial for at-risk users. Journalists protecting sources, activists organizing under surveillance, and ordinary citizens in countries with limited freedoms can communicate without their real-world identity being linked to their messages. Even if Session's servers were compromised, there's no personal data to leak.
Onion Routing for Metadata Protection
Session uses onion routing similar to Tor to protect metadata. When you send a message, it's routed through three random nodes before reaching its destination. Each node only knows the previous and next hop, not the full path. This means no single node knows both who you are and who you're talking to.
This is a significant improvement over messengers that encrypt content but leave metadata exposed. Your ISP and network observers see only that you're using Session, not who you're communicating with or when. The decentralized nature means there's no company storing metadata logs that could be subpoenaed.
Decentralized Network Architecture
Unlike centralized messengers, Session runs on a network of community-operated service nodes. These nodes store and forward encrypted messages for offline users, handle onion routing, and form the backbone of the network. Anyone can run a node, contributing to the network's resilience and decentralization.
The node network is secured through a proof-of-stake mechanism using the Oxen cryptocurrency. Node operators stake Oxen tokens, creating economic incentives for honest operation. This approach provides security without the energy waste of proof-of-work systems while maintaining decentralization.
End-to-End Encryption
All Session messages are end-to-end encrypted using the Session Protocol, which evolved from Signal's protocol. Messages, voice notes, files, and attachments are all encrypted so that only the intended recipients can read them. The service nodes that route messages cannot decrypt the content.
Perfect forward secrecy ensures that compromising current keys doesn't expose past messages. Each message uses unique encryption keys, so capturing one message doesn't help decrypt others. The cryptographic implementation has been audited by Quarkslab, with results publicly available.
Features and Functionality
Session includes the features expected from a modern messenger. One-to-one and group chats support text, images, voice notes, and file attachments. Disappearing messages can be set to auto-delete after a configurable time period. Voice and video calling is available on mobile apps with the same privacy protections as messaging.
Open groups allow larger communities to communicate, functioning similar to Telegram channels or Discord servers. These groups can be public or invite-only, making Session suitable for community building as well as private communication. Group administrators have moderation tools to manage members.
Cross-Platform Availability
Session is available on all major platforms. Mobile apps for iOS and Android provide the primary experience for most users. Desktop apps for Windows, macOS, and Linux allow messaging from computers. All clients maintain the same privacy guarantees and sync securely between devices using the Session ID.
The multi-device experience uses a unique approach where each device has its own encryption keys but can retrieve messages from the network independently. This means you can use Session on multiple devices without compromising security by sharing keys between devices.
Limitations to Consider
Session's decentralized architecture can result in slower message delivery compared to centralized services, especially during network congestion. The onion routing adds latency, though it's generally acceptable for asynchronous messaging. Voice and video calls may experience quality variations depending on network conditions.
The anonymous Session ID, while excellent for privacy, makes it harder to find and verify contacts compared to phone number-based messengers. Users need to share their Session IDs through secure channels. The smaller user base compared to mainstream messengers means you may need to convince contacts to install it.
Who Should Use Session
Session is ideal for users who prioritize anonymity and metadata protection. Journalists, activists, and anyone communicating sensitive information will appreciate the lack of identity requirements. Privacy enthusiasts who object to linking their phone number to a messaging account will find Session liberating. Users in countries with surveillance concerns benefit from the decentralized, censorship-resistant architecture. If you want a messenger that collects nothing about you and leaves no central records of your communications, Session is an excellent choice.
Pros and Cons
Pros
- Onion routing through three nodes hides who talks to whom
- Anonymous Session ID — no phone number or email
- Decentralised, so no company holds subpoena-able metadata logs
- Open source under GPLv3 and free
- Disappearing messages and open groups
Cons
- Slower delivery, especially under network congestion
- Onion routing adds latency to every message
- Session IDs make finding and verifying contacts harder
- Voice and video quality varies with conditions
Alternatives to Session
Looking for other European secure messaging apps? Here are some alternatives worth considering:
Frequently Asked Questions
Simply download the Session app and tap "Create Account." The app will automatically generate a random Session ID for you. There's no sign-up form, no verification, and no personal information required. Your Session ID is your identity on the network.
While Session's encryption protocol evolved from Signal's, they differ significantly in architecture. Signal requires a phone number and runs on centralized servers. Session requires no personal information and runs on a decentralized network with onion routing. Session prioritizes anonymity and metadata protection; Signal prioritizes ease of use with strong encryption.
Your recovery phrase is the only way to restore your Session account on a new device. If you lose it and your device, your account is unrecoverable - this is a feature, not a bug. There's no company that can help you recover it because no one else has access. Always store your recovery phrase securely.
Yes, Session runs on a network of thousands of community-operated service nodes distributed globally. There's no central server that processes messages. The network is maintained through economic incentives (staking) rather than company infrastructure. This makes Session highly resistant to censorship and single points of failure.
All Session messages are end-to-end encrypted, meaning only you and your recipient can read them. The onion routing adds another layer by preventing network observers from knowing who you're talking to. Even Session's service nodes cannot read message content - they only store and forward encrypted data.
Yes, Session supports encrypted voice and video calls on mobile devices. Calls use the same privacy-preserving architecture as messages, though the real-time nature of calls means they route through fewer hops for acceptable latency. Call quality depends on network conditions.
Yes, Session is fully open source under the GPLv3 license. The code for all clients (iOS, Android, desktop) and the network protocol is available on GitHub. Independent security audits have been conducted, and the community can verify that Session works as claimed.
Session IDs must be shared directly between users - there's no phone number search or username discovery. Share your Session ID through a secure channel, or exchange QR codes in person. This friction is intentional: it prevents anyone from knowing who uses Session or building a social graph.
Session is built as a European alternative to WhatsApp: Decentralized messenger with no phone number required, onion routing, and community-run infrastructure - truly anonymous messaging. It will not be a like-for-like feature match in every respect, so check the review above for where the two genuinely differ before switching.
Session is one of several European Messaging (Decentralized) tools covered on this site. See the full Messaging (Decentralized) category page for how it ranks against its closest European competitors.