Secure Drop
Anonymous · Encrypted · No login required
Your message is sealed and anonymous. We cannot identify you. No account or login is needed.
Your message
Max 3 files, 10 MB each
Secure Channel
Anonymous · Bidirectional · Encrypted
Start an anonymous conversation. You'll receive a thread code to check for replies later.
Your message
Max 3 files, 10 MB each
Thread Code
Enter your thread code above to check for replies.

City of Hats vs. The Competition

Secure Messaging — Feature Comparison

Compare City of Hats with Signal, WhatsApp, Telegram, Facebook Messenger, LINE, Threema, Wire, and WeChat across identity, encryption, ephemeral controls, calls, and technical transparency.

Compare every messaging app

Scan the six core areas below, then open any app for its complete source-backed comparison.

App Identity model Default encryption Post-quantum protection Ephemeral controls Voice & video Technical transparency Full comparison
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

Anonymous Intake & Source Protection

CapabilityCity of HatsSignalTelegramWhatsAppFacebook MessengerLINEThreemaWireWeChat
No phone number or email required
Ephemeral disposable identities (Hats)
Works in any browser (PWA) Web app Web app Web appWeb appWeb app
Native Android app
Sealed one-way tip submission
Two-way secure channel LimitedLimited
No cloud backup of messages Optional

Encryption & Ephemerality

CapabilityCity of HatsSignalTelegramWhatsAppFacebook MessengerLINEThreemaWireWeChat
End-to-end encryption (default) Secret chats only Limited
Post-quantum key exchange (ML-KEM-768) PQXDH
Forward secrecy (Double Ratchet)
Burn-after-read (server-side destruction) Timer only Timer only View once Timer onlyLimitedLimitedTimer onlyLimited
9 Security Modes (View Once, Recall, Sealed File, etc.)
Channel auto-expiry
Zero-knowledge server (blind relay)
No metadata or IP stored Sealed sender Limited

Dead Drops & Advanced Delivery

CapabilityCity of HatsSignalTelegramWhatsAppFacebook MessengerLINEThreemaWireWeChat
Asynchronous encrypted dead drops
Time-locked delivery (future unlock)
Multi-path secret sharing (split delivery)
GhostFrame steganography (data in images)
EchoDrop (voice-passphrase retrieval)
E2E encrypted file attachments Secret chats only Limited
Client-side crypto proof log

Identity Verification & Access Control

CapabilityCity of HatsSignalTelegramWhatsAppFacebook MessengerLINEThreemaWireWeChat
Face liveness verification (sender)
Face liveness gate (recipient, API-enforced)
1:1 face matching for recipient (enterprise)
Zero biometric data retention
Safety number verification
PIN-protected local key storage LimitedLimitedLimitedLimited

Voice, Video & Intelligence

CapabilityCity of HatsSignalTelegramWhatsAppFacebook MessengerLINEThreemaWireWeChat
Encrypted voice calls Secret chats only LimitedLimited
Encrypted video calls Group only LimitedLimited
Built-in intelligence bot (CHECK)
Email / phone / domain risk scoring
Warrant canary (transparency)
Supported Not available Yellow Partial / conditional Highlighted rows = City of Hats exclusive

How we compare: Signal protects conversations through phone-bound identity and strong encryption. Telegram prioritizes reach and features over default encryption. WhatsApp uses the Signal protocol but operates under Meta's data practices — metadata, contacts, and usage data are collected.

City of Hats is the only platform that combines anonymous ephemeral identity, end-to-end encryption with post-quantum key exchange, burn-after-read with server-side destruction, asynchronous dead drops with time-lock and multi-path delivery, GhostFrame steganography, EchoDrop voice retrieval, 9 Security Modes, and face liveness verification without biometric data retention — all from a standard browser with no phone number required.