Email aliasing, self-hostable, crypto accepted.
Session
No phone number. No email. Just an ID. Decentralized encrypted messenger.
getsession.org
- Zero KYC
- CH
- Evidence and facts →
No phone number. No email. Just an ID. Decentralized encrypted messenger.
Evidence and facts
Evidence and facts
Why evidence is 59/100Formula 3.1
- Source coverageSome material claims still need confirmation
- +42
- Review ageOldest recorded check is 163 days old
- +17
Specs
Review analysis, source material, related services, and history
About
Decentralized encrypted messenger needing no phone number or email, stewarded by a Swiss foundation.
Analysis
Session is a decentralized messenger needing no phone number or email, only a generated Session ID, and its Quarkslab security audit is recorded as published with major findings resolved.
The 2026 funding review notes development resumed only in limited capacity after a donation campaign and long-term runway remains a watch item, and the project relocated from Australia to a Swiss foundation in 2024 after Australian police sought user data from an employee.
People wanting phone-free, email-free messaging who are tracking the project's funding runway as an ongoing risk factor.
Corporate identity
Registry-sourced, not audited. The facts below come from cited web research rather than a direct registry query. Each claim links its own source.
- LEGAL ENTITY
- Session Technology Foundation (Session Technology Stiftung)source ↗
- INCORPORATED IN
- Switzerland (Zug)source ↗
- REGISTERED ADDRESS
- Bahnhofstrasse 7, 6300 Zug, Switzerlandsource ↗
Frequently Asked Questions
Is identity verification required?
No identity verification is recorded for typical use. No phone number, no email. Session ID only. Decentralized message storage.
Which payment methods are accepted?
Please check the provider site for accepted payment methods.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
No. The recorded jurisdiction is CH, which is not a Five Eyes country. This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 0 of 4. A hosted operator is recorded. Jurisdiction is shown as context, not a safety verdict. Evidence confidence is 59/100 and recorded risk is caution.
Sources and history
Terms and privacy policy
No changes to the documents we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.