Top picks by use case
| Use case | Recommended | Why |
|---|---|---|
| Default daily messenger | Signal | Best privacy + good UX |
| Cross-network reach (everyone is on it) | Signal Protocol; massive install base | |
| No phone number required | Threema or Session | Account isn't tied to phone |
| Federated / self-hostable | Matrix (via Element) | Like email but encrypted |
| Apple-to-Apple | iMessage | E2EE within Apple ecosystem |
| Onion-routed (anti-metadata) | Session | No central server, no IDs |
The main contenders
The privacy gold standard. Default E2EE on every message, group, and call. Open-source clients and server. The Signal Protocol is the most-audited messaging encryption in existence. Sealed Sender hides metadata even from Signal's own servers. Non-profit-funded. Polished mobile and desktop apps.
Best for: default daily-driver private messenger.
Uses Signal Protocol for E2EE — message encryption itself is strong. Owned by Meta, which collects substantial metadata (who messages whom, when, how often, via what numbers; backups in iCloud/Google Drive may not be E2EE depending on settings). For "the messenger your non-technical contacts already have," it's the only option in many countries.
Best for: reaching people who won't install another app; international communication where it's the de facto network.
Swiss, paid one-time (~$5 for the app), no phone number or email required. Account is a random Threema ID. E2EE by default. Decent feature set including groups, voice, video, polls. Polished UX. Trade-off: smaller user base; people you message must also have Threema.
Best for: users who want strong privacy without tying account to phone/email.
An open standard for decentralized chat. Element is the most-used Matrix client. E2EE on by default for new rooms. You can use the matrix.org homeserver or host your own. Bridges to Discord, Slack, Telegram, Signal exist. Operationally more complex; team-chat-style UX rather than 1-on-1 messenger.
Best for: communities wanting Slack-like collaboration with E2EE and self-host options.
Onion-routed messenger with no central server and no requirement for phone/email at signup. Accounts are random IDs. Metadata exposure is extremely low — even routing nodes can't see message content or sender/recipient. Trade-off: smaller user base, occasionally laggy message delivery, fewer features than Signal.
Best for: high-threat-model users (journalists, activists in hostile environments) where metadata exposure is the dominant risk.
What you can skip — or use carefully
- Telegram: 1-on-1 chats are not E2EE by default; groups are never E2EE. Great chat platform; not a private messenger. See Signal vs Telegram.
- SMS: cleartext. Use only for verification codes; never for sensitive content.
- Facebook Messenger (default): E2EE rollout is ongoing but not universal. Default chats are not consistently E2EE.
- Discord: not E2EE at all. Server admins and Discord can read all messages.
- "Encrypted" apps with unclear business models: a private messenger has to be funded somehow. Pay, or know who pays.
What actually matters
- Default encryption: off-by-default doesn't help when people forget to turn it on.
- Metadata exposure: who you talk to, when, and how often is sensitive even if the contents are encrypted.
- Backup encryption: if your messages back up unencrypted to a cloud service, your encryption is bypassed. Check backup settings.
- Network effect: the best encrypted messenger is the one your contacts will install. Push privacy-conscious friends to Signal where reasonable.
- Identity model: phone-number-based (Signal, WhatsApp) vs username (Threema, Session). Phone numbers leak identity to people who guess them.
- Disappearing messages: reduce data exposure if a device is later compromised. Most major messengers now support them.
Backups — the silent encryption killer
An E2EE conversation backed up in cleartext to iCloud or Google Drive is no longer E2EE — the backup provider can read it. Check:
- Signal: backups are local-only by default; cross-device sync via QR code linking. No cloud backup by default.
- WhatsApp: iCloud / Google Drive backups can be E2EE if you enable the option (with a passphrase or key). Off by default in many regions.
- iMessage: end-to-end encrypted backups via iCloud are available if Advanced Data Protection is enabled. Off by default.
- Telegram: standard chats live on Telegram servers in cleartext; backups aren't the issue, the primary store is.
Picking quickly
- Most people: Signal as default; WhatsApp for contacts who won't switch.
- Privacy maximalist: Signal + Session for high-stakes conversations.
- Apple household: iMessage (with Advanced Data Protection) + Signal for cross-platform.
- Team / community: Matrix self-hosted, or Signal groups.
- Anonymous identity: Threema (paid) or Session (free).
Frequently Asked Questions
Is WhatsApp encryption real?
Yes — WhatsApp uses Signal Protocol for message E2EE. The encryption itself is solid. The concern is metadata Meta collects around the messages and whether backups are also encrypted (depends on settings).
Can Signal be subpoenaed?
Yes, anyone can be served legal process. Signal's responses to subpoenas (published) show they hold essentially nothing — account creation date, last connection date. No message contents, no contacts, no metadata about who you message.
Is iMessage as private as Signal?
Apple-to-Apple iMessage is E2EE. With Advanced Data Protection enabled, backups are also E2EE. Metadata collection by Apple is modest. For Apple-only conversations, iMessage is competitive with Signal. For cross-platform or maximum independence, Signal is better.
Should I use Telegram for private messaging?
Not for actually-private conversations. Telegram is excellent as a chat platform and community channel — but default chats aren't E2EE and groups never are. Use Signal for privacy; use Telegram for what Telegram is good at.
Is Session usable as a primary messenger?
For many users yes — feature parity with Signal is improving. Smaller user base means fewer of your contacts will be there. Routing through onion-style nodes occasionally adds latency. For high-threat-model use, the trade-offs are worth it.
What about Threema for business?
Threema Work is positioned for business use with admin controls. Used in Switzerland and parts of Europe. Outside that footprint, harder to justify vs Signal or Matrix for org-wide deployment.