End-to-end encryption has become the baseline expectation for private messaging, yet the protection it offers depends heavily on which app you use and how it is configured. In practice, only the sender’s device and the recipient’s device can read an encrypted message, leaving the servers in between with content they cannot decipher. According to each service’s official documentation, WhatsApp, Signal, iMessage and personal Messenger chats enable this by default, and RCS conversations increasingly do as well. Telegram does not, except in its manually opened secret chats. In none of these apps does end-to-end encryption, on its own, cover backups or the metadata revealing who you talk to and when.
- Default protection varies: WhatsApp, Signal, iMessage and personal Messenger chats are encrypted end-to-end by default, while Telegram applies it only to secret chats.
- RCS is catching up: Encrypted RCS between iPhone and Android began rolling out in beta in May 2026, but requires compatible devices, carriers and updated apps.
- Backups are the weak link: WhatsApp cloud backups are only encrypted if you enable the option, and standard iCloud backups can retain the iMessage key.
- Metadata stays exposed: Encryption hides message content, not the timing, frequency or participants of a conversation, with Signal standing out as the clearest exception.
How end-to-end encryption actually works
The core distinction lies in who holds the keys. With end-to-end encryption, the message is encrypted on your device and decrypted only on the recipient’s, so intermediary servers transport content they cannot read. Google’s Messages help pages describe the process clearly: a secret key is generated on both devices, never shared with Google, regenerated for each message and deleted after use. WhatsApp’s encryption documentation describes the same model, with keys changing per message and encryption and decryption occurring entirely on the device.
This contrasts with encryption in transit and at rest, where data travels protected but the company retains the keys and can decrypt it. That is the default model for much of the cloud services market. Most encrypted messengers also let users verify that no one has inserted themselves into the conversation: WhatsApp displays a 60-digit code and a QR code per conversation, while Google Messages offers a verification code.
The current landscape, based on official sources, places WhatsApp, Signal, iMessage and Messenger in the default end-to-end category for personal conversations, with RCS joining when specific conditions are met. Telegram remains the outlier, applying end-to-end encryption only to secret chats and calls. Its own FAQ confirms that standard private and group chats use client-to-server encryption. Secret chats are end-to-end encrypted but work only on the device where they were created, and Telegram recommends them for users concerned about personal security.
The practical result is a mismatch in expectations: many users assume Telegram is the most secure option, when by default it protects less than WhatsApp. The issue is not the quality of the cryptography but who holds the keys.
Encrypted RCS between iPhone and Android deserves separate attention. Apple states that encryption is enabled by default and is being applied progressively to new and existing conversations. The lock icon is the indicator to watch: if it does not appear, encryption is not active, and the same applies if a chat falls back to SMS.
Where end-to-end encryption stops protecting you
End-to-end encryption protects content while it travels. It does not protect unencrypted backups, metadata, or an unlocked phone in someone else’s hands. These are the three gaps through which most exposure occurs.
Backups remain the most common weak point
In WhatsApp, if you store backups in your Google account, end-to-end encryption is an option you must enable, protected by a passkey, password or 64-digit key, according to the service’s backup documentation. WhatsApp is also testing its own storage that, per the same page, is always encrypted. If you lose the password, WhatsApp cannot recover it. In iMessage, the fine print sits in Apple’s iCloud security documentation. Messages in iCloud is end-to-end encrypted, but under standard protection, an enabled iCloud backup includes the Messages key and Apple holds the backup keys. Advanced Data Protection, available since iOS 16.2, closes that gap by raising the number of end-to-end encrypted categories from 15 to 25, including iCloud backup. The trade-off is that Apple can no longer help recover data if you lose access.
Metadata reveals the pattern of your conversations
Encryption conceals what you say, not necessarily with whom, when or from where. WhatsApp’s privacy policy for Europe, in force since 2 July 2026, states that the company collects the time, frequency and duration of your activities, the hours you make and receive calls and exchange messages, and data such as your IP address or phone model. Signal is the clearest exception. Its legal request page explains that it encrypts both content and much of the metadata end-to-end, and that in a 2016 case it could only provide the account creation date and last connection date.
The device and the person on the other end
Encryption ends at the screen. Anyone who unlocks your phone reads what you read. If the recipient takes a screenshot or forwards the message, encryption does not prevent it. And if you report a message on Messenger, Meta can see it, as its own announcement confirms.
End-to-end encryption should no longer be a marketing argument but a minimum requirement for any messaging app. The real battle has shifted to backups and metadata, where differences between apps are enormous. If only one setting can be changed today, it should be encrypting the WhatsApp backup or enabling Advanced Data Protection on iPhone, since those are the places where the most people remain exposed without realizing it.