End-to-end encryption
Only the sender and the recipient can read a message; the service in between cannot.
End-to-end encryption (E2EE) means a message is encrypted on your phone and decrypted only on the recipient's phone. The company that carries it (WhatsApp, Signal, Apple for iMessage) stores and forwards scrambled bytes it cannot read, because the keys exist only on the two devices. That is the difference with ordinary HTTPS, which protects the trip to the server but lets the server read everything once it arrives.
It works with public-key cryptography: each device publishes a public key, and your phone uses the recipient's public key to lock the message so that only their private key opens it. The Signal protocol, used by Signal, WhatsApp and others, adds a trick: keys rotate with every message, so even a key stolen later cannot unlock old conversations.
The limits matter. E2EE hides content, not metadata: the service still knows who talks to whom, when and how often. It does nothing if the phone itself is compromised, if someone screenshots the chat, or if your cloud backup of the chat is not encrypted the same way (check that setting; it is often the weak spot). And when a government asks for a 'backdoor' for investigators, the technical answer is that a door for one party is a door for anyone who finds it.
Practically: your chat app probably already has it on; the setting worth checking is encrypted backups. For email, E2EE is rare and awkward, so treat email as a postcard.
Keep in mind
- Encrypted on one device, decrypted on the other; the service never has the key.
- HTTPS protects the road to the server; E2EE also protects against the server.
- It hides content, not who talks to whom or when.
- Unencrypted cloud backups are the usual gap; check that setting.
