A New Era of Secure Messaging: End-to-End Encryption for RCS Between iPhone and Android

Introduction

For years, communication between iPhone and Android users relied on outdated SMS technology, leaving messages vulnerable to interception. That changes now. With the release of iOS 26.5, Apple has introduced support for end-to-end encryption (E2EE) in Rich Communication Services (RCS), bringing robust privacy to cross-platform chats. This long-awaited upgrade fulfills a joint promise from Apple and Google to secure everyday conversations.

A New Era of Secure Messaging: End-to-End Encryption for RCS Between iPhone and Android — Source: www.eff.org

What the Update Brings

This update ensures that messages exchanged between Apple’s Messages app and Google Messages on Android are automatically encrypted end-to-end, provided the carrier supports both RCS and encrypted messaging. RCS itself replaced SMS in 2024, vastly improving image and media quality. Now, those conversations gain the same level of security that makes it impossible for Google, Apple, or cellular carriers to read the contents.

The encryption relies on both companies supporting the GSMA RCS Universal Profile 3.0, which implements the Messaging Layer Security (MLS) protocol. This open standard provides strong cryptographic guarantees for group and one-to-one chats.

How It Works Under the Hood

The rollout depends on carrier cooperation and device software versions. When all conditions are met—your Android phone running the latest Google Messages, your iPhone updated to iOS 26.5, and your carrier enabling encrypted RCS—a padlock icon and the word “Encrypted” appear at the top of the conversation. Until then, messages remain unencrypted.

It’s important to note that the feature is still labeled as beta on Apple devices. This means some users may not see the encryption immediately. You can check carrier compatibility on Apple’s support page or Google’s list of supported operators.

Privacy Limitations: Metadata and Backups

While message content is now secure, metadata—such as who you’re talking to, when, and for how long—may still be collected and stored by carriers or platform providers. For conversations that demand absolute privacy, third‑party apps like Signal remain a stronger choice because they also encrypt metadata.

Another consideration: cloud backups. On iOS, if you back up iMessage to iCloud, the encryption may be lost unless you enable Advanced Data Protection (ADP). Google Messages encrypts the text of backups but not the media, leaving photos and videos potentially exposed. We hope Google follows Apple’s lead with a similar full‑backup encryption option.

Nevertheless, this update protects the content of billions of daily messages from prying eyes—a significant privacy win for mainstream users.

What to Expect During the Rollout

Because the feature is carrier‑dependent, adoption will be gradual. If you don’t see the encryption indicator yet, don’t worry—your chats are still using standard RCS without E2EE. Once the infrastructure is in place, every new RCS conversation between compatible devices will automatically become encrypted. No settings need to be toggled; it works seamlessly in the background.

To verify, look for the lock icon and “Encrypted” text at the top of the conversation view. If you see it, you can be confident that only you and the recipient can read the messages.

Conclusion: A Major Step for Privacy

We applaud Apple and Google for delivering on their promise to encrypt cross‑platform communications. While not perfect—metadata and backup gaps remain—this move dramatically raises the security baseline for hundreds of millions of users. It proves that tech giants can collaborate on difficult privacy challenges. We encourage other companies to follow suit, and we look forward to further improvements like full backup encryption and metadata protection.

For now, enjoy the peace of mind that your RCS chats are finally encrypted. It’s about time.

Tags: