On 11 May 2026, Google and Apple each published matching announcements that end-to-end encrypted Rich Communication Services (RCS) messaging had begun rolling out in beta. Google’s post, by Elmar Weber, GM of Android and Business Communications, said Google Messages has had end-to-end encryption between Android devices for years and that the companies had led a cross-industry effort to bring the same property to RCS, the profile that replaces traditional SMS for capable devices. Apple’s Newsroom post the same day said iPhone users on iOS 26.5 would begin seeing a lock icon in RCS chats when messages are end-to-end encrypted. What was announced, by whom, and on what date is therefore clear. Google and Apple, on 11 May 2026, said the beta applies to iPhone users running iOS 26.5 with supported carriers and to Android users on the latest Google Messages. Encryption is on by default and “will be automatically enabled over time for new and existing RCS conversations,” in both companies’ wording. When it is on, they said, messages cannot be read while they are sent between devices. Google Messages users were told they would see the same lock icon already used in Android-to-Android RCS. Apple added that iMessage remains end-to-end encrypted and “the best way to communicate between Apple devices.” What was not confirmed is equally important. Neither post published a list of Bangladeshi or South Asian carriers, a completion date for leaving beta, or a guarantee that every existing RCS thread would encrypt on day one. Availability is explicitly tied to carrier support. A conversation encrypts only if both sides’ networks and clients support the feature. SMS and MMS, which RCS is meant to replace for capable users, were not described as end-to-end encrypted. Group chats, business messaging, and RCS to devices that are not on iOS 26.5 or current Google Messages were not given the same default promise in the text loaded here. Apple’s post is a “quick read” update; it does not specify the cryptographic protocol in that page. Industry coverage has pointed to GSMA RCS Universal Profile 3.0 and Messaging Layer Security; those details are not treated as Apple or Google announcements unless they appear on the two official pages, and the Newsroom and Keyword posts loaded for this item do not name MLS. The beta label is doing real work. Features in beta can stall, remain carrier-gated, or behave inconsistently. Users should look for the lock in each thread rather than assuming the software update finished the job. Apple’s later support articles, not loaded as primary sources for this briefing, have described a Settings toggle for RCS end-to-end encryption; the 11 May Newsroom post itself only describes the lock icon and default-on behaviour. Cross-platform encryption does not make RCS equivalent to iMessage or to Signal. Identity is still bound to phone numbers and carrier profiles. Metadata such as who messaged whom, and unencrypted SMS fallback when RCS is unavailable, remain in the older model. Device compromise still yields plaintext. Neither company claimed that lawful intercept at the carrier for non-RCS messages had changed. What this means in practice If you run iOS 26.5 and a contact runs current Google Messages, open the thread and look for the lock before sending anything sensitive. If the lock is missing, treat the chat as you would SMS. Keep Google Messages and iOS updated. Do not interpret this announcement as a Bangladesh-wide carrier mandate; check your operator. Cyber71 cannot enable RCS encryption at a carrier, certify a thread, or recover messages. What is still unclear The fraction of conversations that have actually upgraded, the GSMA parameter sets on each carrier, how long beta will last, and whether feature-phone or dual-SIM edge cases break encryption were not in the two official posts. Google’s footnote that the capability is “available on devices that support the RCS standard and have end-to-end encryption enabled” is a tautology until carriers publish support matrices. Independent protocol analysis of the deployed MLS profile is outside this announcement-only item.

Sources

  1. Google Keyword Blog — End-to-end encrypted RCS messaging begins rolling out today for Android and iPhone users2026-09-24
  2. Apple Newsroom — End-to-end encrypted RCS messaging begins rolling out today in beta2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All research

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help