Email aliasing, self-hostable, crypto accepted.
Session
No phone number. No email. Just an ID. Decentralized encrypted messenger.
getsession.org
- No routine KYC
- CH
- Evidence and facts →
No phone number. No email. Just an ID. Decentralized encrypted messenger.
Evidence and facts
Evidence and facts
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 generates a pseudonymous Account ID without phone/email signup. Quarkslab's scoped app audit is from 2021; major findings were addressed then, which does not establish current client/network assurance or complete Protocol v2 migration.
The Swiss Session Technology Foundation stewards the project. Seeds, push and opt-in calls have distinct IP/account-token exposure, and public Communities are not E2EE. Development resources remain constrained; October updates say Pro is on hold. The project's regulatory-relocation account is provider-reported, not independently established police causation.
People wanting phone-free, email-free messaging who are tracking the project's funding runway as an ongoing risk factor.
Corporate identity
Provider statements; Other cited research. Not audited. Each claim links its own source.
- LEGAL ENTITY
- Session Technology Foundation (Session Technology Stiftung)provider statement ↗
- INCORPORATED IN
- Switzerland (Zug)provider statement ↗
- REGISTERED ADDRESS
- Bahnhofstrasse 7, 6300 Zug, Switzerlandprovider statement ↗
- Oxen Privacy Tech Foundation (OPTF), former Australian project steward
Frequently Asked Questions
Is identity verification required?
No identity verification is recorded for typical use. No phone, email or identity-document signup for the pseudonymous Session AccountID. Terms require age18+ (or local majority if older). Store, voluntary support/newsletter and any future paid gateways have separate identity/data surfaces.
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. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is partial evidence, last reviewed 2026-11-08, 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.