What end-to-end encryption actually protects
End-to-end encryption keeps messages readable only by the sender and recipient. Learn how the keys work, what metadata still leaks, and where it is misused.
End-to-end encryption means the message is encrypted on the sender's device and decrypted on the recipient's device. The service in the middle can store and forward ciphertext, but it should not be able to read the content.
The basic key exchange
In a simple model, each person has a public key and a private key. The sender encrypts with the recipient's public key; only the matching private key can decrypt. In practice, messaging apps use protocols that combine identity keys, temporary session keys and ratcheting to provide forward secrecy.
Forward secrecy means that if a long-term key is later stolen, past messages are not automatically exposed. Each session or message uses keys that are discarded after use. This is a meaningful improvement over encrypting everything with one static key.
What the provider can still see
End-to-end encryption protects content, not all information. The provider may still see:
- who communicates with whom;
- when messages are sent;
- message sizes and frequency;
- account metadata, device information and IP addresses;
- group membership in some designs.
This metadata can be sensitive even when the words are unreadable. A provider may also collect unencrypted profile data, contacts or backups.
Backups are the weak point
Many apps offer cloud backups. If the backup is not end-to-end encrypted, the provider or anyone who compromises the backup can read the messages. Some apps let you set a backup password; others encrypt backups with a key tied to the account.
Check the backup setting before assuming a conversation is private. The lock icon on a message does not necessarily cover the copy stored in the cloud.
Where the term is stretched
"End-to-end encrypted" is sometimes used for systems that encrypt data in transit and at rest but still let the provider read it. That is encryption, but not end-to-end. Look for a clear statement that the service cannot access message content, and prefer designs with published protocols and independent audits.
Group messaging adds complexity. A group key must be distributed and rotated when membership changes. A poorly implemented group protocol can expose messages to removed members or to the server.
Practical advice
- Use a reputable app with a published protocol and audits.
- Verify safety numbers if the app offers them, especially for high-stakes contacts.
- Turn on encrypted backups or disable cloud backups for sensitive chats.
- Keep devices updated. A compromised endpoint bypasses the encryption.
- Remember metadata. Use a service whose privacy policy matches your threat model.
End-to-end encryption is a strong tool, not a complete anonymity system. It protects content from the service and from network attackers, but it cannot protect a phone that is unlocked or a recipient who forwards the message.
For background, see how the internet works and what an API is.