Ephemeral messaging has become a standard feature — enabled by default in Signal for new conversations, available as an option in WhatsApp and iMessage, and built into Snapchat's entire identity. The idea is intuitive: messages that delete themselves after a timer reduce the accumulation of sensitive conversation history. But "reduces" is the operative word, and understanding exactly what gets reduced requires being precise about which threats you're actually considering.
What the Feature Is Designed to Do
Disappearing messages exist to limit the persistence of conversation history on devices. If a message is set to expire after 24 hours and the timer elapses, the plaintext is deleted from both participants' devices — or is supposed to be. This is the threat model: a device that is later seized, searched, or compromised should not yield a complete archive of past conversations.
That's a legitimate and well-defined goal. Law enforcement obtaining physical access to a device years later, a civil litigant subpoenaing device backups, a partner going through your phone — these are all scenarios where expiring messages provide real protection that standard message history does not.
Disappearing messages protect against retrospective access to device storage. They do not protect against real-time surveillance, backup services, server-side copies, or a recipient who screenshots before the timer runs.
This is worth holding onto as a frame: the feature protects the archive, not the transmission. End-to-end encryption protects the transmission. These are different layers solving different problems.
The Screenshot Problem Has No Technical Solution
Snapchat pioneered ephemeral messaging and simultaneously introduced the "screenshot notification" — an alert sent to the sender when a recipient screenshotted their photo or message. This was and remains fundamentally unenforceable. Screenshots can be taken by a second device pointed at the screen, by screen recorders that operate below the notification layer, or by simply modifying the app.
Signal and WhatsApp offer screenshot prevention in some views (preventing the operating system screenshot API from capturing certain screens), but this is a user-experience nudge, not a cryptographic guarantee. On Android, apps with screen-recording permissions or root access bypass it trivially.
The practical upshot: if the recipient of your message wants to preserve it, they can. Disappearing messages are not a mechanism for controlling what the other person does with your content. They are a mechanism for not building up a local archive neither party intended to maintain.
Backups Are the Silent Gap
Many users enable disappearing messages and then unknowingly back up their entire message history to iCloud or Google One. On WhatsApp specifically, the default backup behavior has historically stored messages in plaintext in iCloud — accessible to Apple and, by extension, any legal process directed at Apple. WhatsApp's 2021 introduction of end-to-end encrypted backups addressed this, but only for users who explicitly opted into the feature.
Even with encrypted backups enabled, the question is what the backup captures. If a backup runs at 3:00 AM and your messages expire at 6:00 AM, that backup contains the messages. Whether those messages survive the next backup cycle depends on implementation details most users have never audited.
| App | Default Backup Behavior | E2EE Backup Available |
|---|---|---|
| Signal | No cloud backup by default (opt-in local backup) | Yes — encrypted local backups; no cloud sync |
| iCloud/Google backup enabled by default | Opt-in — E2EE backup requires explicit user action | |
| iMessage | iCloud backup (unencrypted to Apple) unless Advanced Data Protection enabled | Opt-in — requires iOS Advanced Data Protection |
| Telegram | Server-side storage (cloud chats not E2EE) | No — standard chats are stored on Telegram's servers |
Forward Secrecy Is a Related but Different Concept
Disappearing messages are sometimes conflated with forward secrecy — a cryptographic property that ensures past session keys can't be derived if a current key is compromised. These are related in spirit but distinct in implementation.
Forward secrecy protects against future key compromise exposing past traffic. It operates at the encryption layer — keys rotate frequently, so even if an adversary records your encrypted traffic now and obtains your private key later, they cannot decrypt old messages because the session keys used to encrypt them are long gone.
Disappearing messages operate at the storage layer — plaintext is deleted from device storage after a timer. A service can implement one without the other. Signal implements both. Most other apps implement neither with the rigor Signal does.
What Deletion Actually Means on Modern Operating Systems
When an app deletes a message, it typically removes the record from its database and asks the operating system to free the storage space. On flash storage — which includes every modern phone — the OS may not immediately overwrite that space. SSD and flash controllers use wear-leveling algorithms that spread writes across physical memory cells. "Deleted" data may persist in unallocated space until it's eventually overwritten by other data.
This is not a flaw in disappearing message implementations specifically — it's a property of flash storage that applies to all file deletions. Forensic tools designed for law enforcement can often recover data from unallocated storage blocks. Full-disk encryption (enabled by default on modern iPhones and Android phones) limits this attack because the raw flash blocks are encrypted even if not overwritten, but it's worth understanding that "deleted" is not the same as "unrecoverable."
The storage-layer guarantee of disappearing messages is best understood as "not accessible through normal app interfaces" rather than "cryptographically erased from all physical media."
Practical Guidance: When to Use It
Disappearing messages are most effective when:
- Both parties want it. Ephemeral messaging is a mutual agreement, not a unilateral protection. The recipient can always preserve content if they choose to.
- The threat is future device access, not current interception. If your concern is someone reading your messages months later through device access or backup subpoena, expiring messages reduce that risk meaningfully.
- Backups are disabled or encrypted. Enabling disappearing messages while maintaining an unencrypted cloud backup of your messages is contradictory.
Disappearing messages are less useful when:
- The recipient is the adversary (they'll screenshot before deletion).
- Your threat model is network-level surveillance (use end-to-end encryption for that).
- You're using a service that stores messages server-side regardless of timer (Telegram standard chats, for example).
How Haven Handles Ephemeral Messaging
Haven's encrypted chat uses MLS (Messaging Layer Security) with key rotation on every message epoch — forward secrecy is built into the protocol, not an optional feature. Device-side message deletion is implemented at the database layer, and Haven does not maintain cloud backup copies of chat history. Encrypted email in Haven has full message history, consistent with how email works, and doesn't offer auto-expiry — that's a deliberate design choice reflecting that email and chat serve different persistence expectations.
Other apps with strong ephemeral messaging implementations include Signal (recommended for general use) and Wire (strong enterprise focus). The important thing is understanding what the feature actually does — not what the marketing implies.