Signal, WhatsApp and Telegram still tie you to a phone number. theSHFT, like Threema, Session and SimpleX, needs none, and adds a PIN vault, a duress PIN (Pro) and post quantum direct messages.
Nine apps, nine rows, one source per cell, checked 2026-09-18. Scroll sideways on a phone.
| Feature | Signal | Telegram | Threema | Session | SimpleX | Wire | iMessage | theSHFT | |
|---|---|---|---|---|---|---|---|---|---|
| No phone number to sign up | Required in the stable app (usernames optional); phone free signup in an Android beta as of September 2026 | Required | Required | Not required (random Threema ID) | Not required | No user identifiers at all | Email address (personal accounts register with a username, email and password) | Apple Account | Username and PIN only |
| Post quantum encryption on direct messages | Yes, PQXDH since September 2023 | No public technical confirmation | No (secret chats use classical Diffie Hellman) | Not shipped (work with IBM Research announced February 2026) | Not shipped (planned for Protocol V2) | Yes on direct chats since v5.7 (April 2024); not in groups | No post quantum key exchange in production (MLS with cipher suite agility) | Yes, PQ3 since iOS 17.4 | Yes when the recipient's device has published a post quantum key; a bundle without one gives a classical session |
| Post quantum protection after the session starts | Yes, the SPQR triple ratchet, rolling out since October 2025 | No public confirmation | No | No | No | Yes, the KEM runs inside the double ratchet | No | Yes, periodic post quantum rekeying | No, the post quantum secret is mixed at session start only |
| Screenshots | Screen Security blanks captures on Android and hides the app switcher preview; no notice to the other party | View once media and profile photos only; no notice to the other party | Secret chats show a screenshot notice, best effort | Android: the No thumbnails and screenshots privacy setting disables screenshots of select screens and hides the app switcher thumbnail; iOS none; no notice to the other party | Android hides the app switcher preview (FLAG_SECURE while in the background); no capture blanking of the open app; screenshot alerts removed November 2025; no notice to the other party | Protect app screen blanks captures on Android; no notice to the other party | None (the vendor notes the receiver can still take a screenshot) | None | Captures come out blank by default and the other party is told of a screenshot |
| Duress wipe | Not listed | Not listed | Not listed | Not listed | Not listed | Self destruct passcode since v5.1 (May 2023) | Not listed | Not listed | Duress PIN wipes the app and deletes the account (Pro) |
| Disappearing messages shared by both sides | Yes, per chat, with a default for new chats; a preset or a custom time of up to 4 weeks | Yes, 24 hours, 7 days or 90 days; either side can turn it on | Yes, auto delete in any chat since February 2021 (24 hours or 7 days at launch, custom durations since April 2022, a default for new chats since December 2022), erasing for all participants; secret chats add a per message self destruct timer | No shared timer; local auto delete after 1 week to 1 year | Yes, after send or after read, per conversation | Yes, both sides must agree | Yes, in 1:1 and group conversations | None | Yes, one timer per chat; 10 second default; Off, 10 s and 30 s free; 5 s to 24 h with Pro |
| Address book | Optional; matched through a private contact discovery service (SGX enclave) | Uploaded to find contacts | Synced to find contacts; the synced copy can be deleted | Off by default; hashed when turned on | Never (contacts are added by Account ID) | Never (no identifiers to match) | Not checked | Apple contacts | Never asked for (the app has no contacts permission) |
| Open source | Clients and server (AGPL) | Closed | Clients open with reproducible builds; server closed | Clients (AGPL) | Clients and storage server | Clients and server (AGPL) | Clients (GPL) and server (AGPL) | Closed | Encryption module only (stale public copy; the republish with the hash of the shipped file is planned); app and server closed |
| External review | Formal analysis of PQXDH by Cryspen (2023) and published academic analyses | Signal Protocol whitepaper; no public review of the app itself | None listed | Cure53 (2020, 2024) and two university reviews | Quarkslab (report published 2021) | Trail of Bits (2022, 2024) | Kudelski Security and X41 D-Sec (2017, 2018) | Analyses by ETH Zurich and the University of Waterloo, and a third party code review of PQ3 | None |
We are one iOS app with no external audit yet. On this table we win on identity, capture blanking with a notice, and the duress PIN (Pro), and we lose to Signal and iMessage on post quantum depth and to everyone open on source. We would rather you see that here than find it yourself.
Every competitor cell above rests on a vendor page, repository or published review, listed here by row. A cell that says "Not listed" means the vendor's feature page or FAQ named nothing of the kind on the check date. The Signal and Wire help center articles refuse automated readers, so they were read through the vendors' own help center API on the check date. Corrections to support@theshft.app.
No phone number to sign up. Signal: link 1, link 2. WhatsApp: source. Telegram: source. Threema: source. Session: source. SimpleX: source. Wire: source. iMessage: source.
Post quantum encryption on direct messages. Signal: source. WhatsApp: source. Telegram: source. Threema: link 1, link 2. Session: source. SimpleX: source. Wire: link 1, link 2. iMessage: source.
Post quantum protection after the session starts. Signal: source. WhatsApp: source. Telegram: source. Threema: source. Session: source. SimpleX: source. Wire: source. iMessage: source.
Screenshots. Signal: source. WhatsApp: link 1, link 2. Telegram: source. Threema: link 1, link 2, link 3. Session: link 1, link 2, link 3. SimpleX: source. Wire: source. iMessage: source.
Duress wipe. Signal: source. WhatsApp: source. Telegram: source. Threema: source. Session: source. SimpleX: source. Wire: source. iMessage: source.
Disappearing messages shared by both sides. Signal: link 1, link 2. WhatsApp: source. Telegram: link 1, link 2, link 3, link 4. Threema: source. Session: source. SimpleX: source. Wire: link 1, link 2. iMessage: source.
Address book. Signal: source. WhatsApp: source. Telegram: source. Threema: source. Session: source. SimpleX: source. Wire: no primary source fetched on 2026-09-18. iMessage: source.
Open source. Signal: source. WhatsApp: source. Telegram: link 1, link 2. Threema: source. Session: link 1, link 2. SimpleX: source. Wire: source. iMessage: source.
External review. Signal: source. WhatsApp: source. Telegram: source. Threema: source. Session: source. SimpleX: source. Wire: link 1, link 2. iMessage: source.
Encryption protects your messages. But it doesn't protect you.
Many encrypted messengers still tie your identity to a phone number and keep your contact graph. Who you talk to is exposed, even when what you say is not. theSHFT drops the phone number entirely. Just a username and PIN. The whole app is locked behind a PIN plus biometric vault.
A screen lock is common, but few apps in the category protect you under coercion. theSHFT pairs the PIN and biometric lock with a Duress PIN (a Pro feature). Enter it and all data is silently wiped on the spot and your account is deleted. Of the apps compared here, only SimpleX offers a comparable self destruct passcode.
Enter your Duress PIN under pressure and everything is wiped silently. No crash, no error, just math. Your conversations vanish like they never existed.
Download theSHFT and experience privacy that goes beyond encryption.
Download on the App Store