E2EE means servers should not read message bodies. It does not
automatically hide metadata, contact discovery, cloud backups, or
device compromise.
Centralized apps (Signal) optimize UX; federated (Matrix) optimize
control; peer-to-peer designs trade features for topology. Pick
based on who must not learn your social graph.
Transparency: Most links are non-affiliate
official or directory URLs.
Sponsorship FAQ.
Signal's Protocol is widely studied and powers E2EE for messages
and calls. Registration requires a phone number—metadata and
contact discovery are Signal's known trade-offs.
Pros
Excellent E2EE defaults
Voice/video calls included
Nonprofit foundation governance
Cons
Phone number as identifier
Centralized service
Cloud backups on mobile need careful settings
Privacy notes: Disable insecure SMS fallbacks.
Review linked-device list regularly.
Ideal for: Contacts you can move off
WhatsApp/SMS.
Pricing: Free. Platforms: iOS,
Android, desktop.
Why it's here: Best practical upgrade path for
mainstream users.
SimpleX avoids persistent user IDs, using ephemeral connections
and queues. Novel design—smaller community but interesting for
metadata minimization research.
Matrix is a protocol; Element is a common client. Host your own
homeserver for data residency or join public
instances—understand federation trust boundaries.
Pros
Federation and bridges
Self-hostable
Rooms, spaces, E2EE in supported configs
Cons
Complexity for casual users
E2EE not universal across all room types historically
Server admin sees metadata
Ideal for: Teams and communities with technical
admins.
Pricing: Free; Element Cloud/hosting paid
options. Platforms: All major platforms.
Why it's here: Best when you need ownership of
the server.
Threema uses anonymous IDs instead of phone numbers and charges
a small app fee—aligning incentives away from ads. Closed-source
client with published cryptography summaries.
Pros
No phone number required
No ads business model
Swiss jurisdiction
Cons
Paid app barrier
Closed client source
Smaller network than Signal
Ideal for: European users wanting paid, ad-free
model.
Briar syncs directly between devices over Bluetooth, Wi‑Fi, or
Tor—no central server required for many modes. Built for
censorship-resistant scenarios.
Pros
Works without central server in many modes
Tor sync option
Open source
Cons
Not a WhatsApp replacement for everyone
Both parties need Briar
Feature set focused on security over stickers
Ideal for: High-risk offline or censored
environments.
Delta Chat uses existing email infrastructure as transport with
Autocrypt-style encryption. Clever for decentralization;
deliverability and metadata in email headers remain
considerations.
Pros
No new centralized network
Works with any email provider
Open source
Cons
Email metadata exposure
Setup friction
Not identical to Signal UX
Ideal for: Communities already living in email.
Pricing: Free.
Platforms: Mobile and desktop.
Why it's here: Shows transport diversity beyond
bespoke servers.
Telegram is ubiquitous; secret chats offer E2EE but cloud chats
are not E2EE by default. Listed last to discourage mistaking
popularity for security defaults—not as a recommendation.
Pros
Huge network
Channels and bots ecosystem
Optional secret chats
Cons
Cloud chats not E2EE by default
Custom MTProto vs. Signal protocol adoption
Metadata rich central service
Privacy notes: Do not treat regular Telegram
chats as equivalent to Signal.
Ideal for: Public channels only—use another app
for sensitive DMs.
Pricing: Free. Platforms: All
major platforms.
Why it's here: Honesty about what billions
actually use—and its limits.
