|
City of Hats →
|
Hat identities; no phone number or email required |
End-to-end encryption for user-to-user messages, calls, and files |
Hybrid X25519 + ML-KEM-768 key establishment |
Disposable Hats, burn-after-read, and timed delivery controls |
Encrypted voice and video inside Hat channels |
Public security, data-boundary, transparency, and warrant-canary documentation |
Get City of Hats
|
|
Signal →
|
Phone number required for registration; usernames can initiate contact without sharing it |
End-to-end encryption is on by default for messages and calls |
PQXDH plus SPQR/Triple Ratchet adds post-quantum resilience |
Disappearing messages and view-once media |
End-to-end encrypted voice, video, and group calls |
Open-source clients, server, protocols, and published specifications |
Full comparison
|
|
WhatsApp →
|
Phone number-based account and contact discovery |
Default end-to-end encryption for personal messages and calls; some business flows differ |
No current post-quantum chat protocol documented in the cited public materials |
Disappearing messages and View Once media |
End-to-end encrypted personal voice and video calls |
Proprietary application with published security and engineering materials |
Full comparison
|
|
Telegram →
|
Phone number required; number can be hidden and a username shared |
Cloud Chats use client-server encryption; only device-specific Secret Chats are end-to-end encrypted |
No post-quantum chat protocol documented in the cited official materials |
Auto-delete plus self-destruct in Secret Chats |
One-to-one calls support end-to-end encryption; group calling uses a separate design |
Client code is public; server implementation is proprietary |
Full comparison
|
|
Facebook Messenger →
|
Meta/Facebook account identity; regional account options vary |
Default end-to-end encryption for personal chats and calls, with documented exceptions for some surfaces |
No post-quantum Messenger chat protocol documented in the cited public materials |
Disappearing messages in encrypted chats |
End-to-end encrypted personal voice and video calls |
Proprietary service with public help and engineering documentation |
Full comparison
|
|
LINE →
|
Persistent LINE account; registration and linking options vary by device and region |
Letter Sealing is default for supported content; coverage has documented exceptions |
No post-quantum chat protocol documented in the cited official materials |
Message recall and media controls, but no comparable auto-expiring identity model |
Letter Sealing covers one-to-one calls; group calls and meetings are excluded |
Proprietary service with official security and help documentation |
Full comparison
|
|
Threema →
|
Random Threema ID; phone number and email are optional |
End-to-end encryption for messages, files, voice, video, and group communication |
No post-quantum messenger protocol documented in the cited official materials |
Message deletion controls; identity remains persistent unless removed |
End-to-end encrypted voice, video, and group calls |
Open-source applications, published cryptography documentation, and independent audits |
Full comparison
|
|
Wire →
|
Persistent account, often email or organization-managed identity |
End-to-end encryption is always on for messages, calls, and files |
MLS is documented; no post-quantum messenger protocol is documented in the cited materials |
Timed self-deleting messages |
End-to-end encrypted voice, video, and conference calls |
Open-source clients and server with published security documentation |
Full comparison
|
|
WeChat →
|
Persistent WeChat account connected to account and device information |
Official privacy materials describe encryption and safeguards but do not document default end-to-end encryption for standard chats |
No post-quantum chat protocol documented in the cited official materials |
Recall and privacy controls; no comparable disposable identity lifecycle documented |
Voice and video are available; cited materials do not document default end-to-end encryption |
Proprietary service with official privacy, government-request, and data-request policies |
Full comparison
|