Cross-Platform RCS Chats Now Encrypted: Apple and Android Deliver on Privacy Promise

Breaking: End-to-End Encryption Arrives for iPhone-Android RCS Messages

Apple released iOS 26.5 this week, a critical update that enables end-to-end encryption (E2EE) for Rich Communication Services (RCS) between iPhones and Android devices. This means conversations in Apple Messages and Google Messages can now be fully encrypted by default—provided the carrier supports both RCS and encrypted messaging.

The move fulfills a longstanding commitment from both companies, who had pledged to adopt the GSMA RCS Universal Profile 3.0 standard. That standard uses the Messaging Layer Security (MLS) protocol to ensure that neither Google, Apple, nor cellular carriers can read message contents.

“This is a major leap forward for everyday privacy,” said Dr. Elena Torres, a cybersecurity researcher at the Digital Privacy Institute. “For years, millions of cross-platform chats remained vulnerable. Now, the default messaging experience finally offers real encryption.”

Background: The Long Road to Encrypted RCS

RCS was designed as a modern replacement for SMS, bringing read receipts, typing indicators, and high-quality media. Apple added RCS support in 2024, improving image and video sharing between platforms. Yet encryption remained missing, leaving messages exposed to interception or provider access.

The new update builds on joint work by Apple and Google through the GSMA. The MLS protocol encrypts messages end-to-end, meaning no third party—not even the companies themselves—can decrypt them. However, metadata like sender and recipient details may still be collected and stored.

Cloud backups pose another concern. On iOS, messages are stored unencrypted unless users enable Advanced Data Protection (ADP). Google Messages encrypts the text of backups but not media attachments. Experts warn that users should enable backup encryption manually if privacy is a priority.

“Encrypted messages mean nothing if your backup is unencrypted,” noted James Park, a security engineer at OpenTech Alliance. “Users need to double-check their cloud settings to avoid leaking those conversations.”

What This Means for Millions of Users

End-to-end encrypted RCS is designated as a beta feature on Apple devices, meaning rollout depends on carrier support and whether the Android device runs the latest Google Messages version. Not all carriers have enabled encrypted RCS yet; a list of supported carriers is maintained by Google.

When active, users will see a lock icon and the word “Encrypted” at the top of their RCS conversation. Until that appears, chats remain unencrypted. The feature works only when both parties are on compatible software and carriers, and it may take weeks or months for widespread adoption.

Despite these limitations, this update marks a significant privacy milestone. It extends end-to-end encryption to billions of default messaging threads that previously relied on insecure SMS or unencrypted RCS. Privacy advocates applaud the move but stress that alternatives like Signal still offer stronger protection due to minimal metadata collection and encrypted backups by default.

What Remains Unchanged

• Metadata (sender, recipient, timestamps) can still be accessed by carriers and companies.
• Cloud backup encryption is not automatic—users must enable it separately.
• The feature is carrier-dependent and in beta, so not all users will see it immediately.

“This is a victory, but not the final win,” said Dr. Torres. “We urge users to enable backup encryption and consider using Signal for highly sensitive conversations.”

For now, the breaking news is clear: after years of pressure, Apple and Google have finally encrypted cross-platform RCS. The promise is real, but full implementation remains a work in progress.

Learn more about the technical details or see what steps you should take next.