How End-to-End Encryption Changes Cross-Platform Messaging: RCS on iPhone and Android

This week marks a major milestone in cross-platform messaging privacy. With iOS 26.5, Apple has enabled end-to-end encryption for Rich Communication Services (RCS), meaning conversations between Android and iPhone users are now far more secure—provided carriers support it. Both Google and Apple have long promised this feature, and its arrival is a welcome advancement for billions of messages exchanged daily. Below, we answer key questions about what this means, how it works, and what you should know to maximize your privacy.

What is RCS and why is end-to-end encryption important?

RCS stands for Rich Communication Services, the modern replacement for SMS that supports high-quality images, read receipts, typing indicators, and group chats. Since 2024, Apple has supported RCS, significantly improving media sharing between Android and iPhone. Now, with end-to-end encryption (E2EE) enabled by default, the actual content of those messages—text, photos, videos—cannot be read by Google, Apple, or cellular carriers. Only the sender and recipient have the keys to decrypt the conversation. This is crucial because without E2EE, message content is stored in plaintext on servers or transmitted insecurely, leaving it vulnerable to interception or data breaches.

How End-to-End Encryption Changes Cross-Platform Messaging: RCS on iPhone and Android — Source: www.eff.org

Which carriers support encrypted RCS messages?

End-to-end encryption for RCS requires carrier support in addition to compatible software. Both Apple and Google have published a list of supported carriers where this feature is available. Carriers must implement the GSMA RCS Universal Profile 3.0, which includes the Messaging Layer Security (MLS) protocol. If your carrier is not on the list, or if you’re using a version of Google Messages or iOS older than 26.5, encryption may not activate. It’s important to check the carrier list and keep your apps updated. Over time, more carriers are expected to join, but for now, coverage varies by region and provider.

How does this encryption work technically?

The encryption is powered by the GSMA RCS Universal Profile 3.0, which adopts the Messaging Layer Security (MLS) protocol. MLS is designed for group messaging and provides forward secrecy and post-compromise security—meaning if a key is leaked, past messages remain safe and future messages can be re-secured. Both Apple and Google independently implement this standard in their messaging apps. When an iPhone user sends an RCS message to an Android user, the MLS protocol negotiates encryption keys directly between the two devices, with no intermediary retaining decryption keys. Your carrier cannot read the messages, nor can Google or Apple. Metadata such as sender, recipient, and time stamps may still be visible, but the content itself is encrypted.

What is the current status of this feature?

Apple has labeled end-to-end encrypted RCS as beta in iOS 26.5. This means the feature may not be stable or available for all users immediately. The rollout depends on several factors: your carrier’s support, your Android friend running the most recent version of Google Messages, and both devices being on compatible software. Until those conditions are met, conversations will not be encrypted. Apple’s beta label signals that as carrier support expands and updates roll out, the feature will become more reliable. Users should check for updates on both sides and verify encryption status before assuming a chat is private.

How can users verify that their chats are encrypted?

Once both participants meet the requirements—carrier support, updated apps, and a device running iOS 26.5 or the latest Google Messages—you’ll see a lock icon and the word “Encrypted” at the top of the conversation. This indicator confirms that end-to-end encryption is active. If you do not see this lock, do not assume privacy. Additionally, in Apple’s Messages app, you can tap the conversation header to see more details. For Android’s Google Messages, look for the same icon in the chat window. It’s a simple but vital way to ensure your messages are secure.

Are there any privacy concerns with this new feature?

While the message content is encrypted, metadata (who you talk to, when, how often) is still collected by carriers and possibly Google or Apple. For conversations where even metadata sensitivity matters, alternatives like Signal remain the gold standard. Also, if you enable cloud backups—iCloud for iOS or Google Drive for Android—encrypted messages may be stored without protection unless you specifically turn on Advanced Data Protection (ADP) on iOS. Google Messages encrypts text in backups but not media, so photos and videos could be exposed. So while this is a huge step forward, it is not a complete privacy solution for everyone.

Tags: