Your Green Bubble Just Got a Lock Icon—But Here’s the Catch That Still Lets Your Carrier Read Your ‘Encrypted’ Texts
Apple’s iOS 26.5 beta brings end‑to‑end encrypted RCS to some iPhone↔Android chats—but the lock protects content, not the carrier ecosystem and its metadata.
By TheMurrow Editorial
May 19, 2026
Key Points
- 1Track the signal: the lock/“Encrypted” label applies only to eligible RCS threads, not SMS/MMS—and not all chats qualify yet.
- 2Understand the boundary: E2EE protects message content in transit, but RCS provisioning still involves carriers exchanging identifiers like phone number (and sometimes IP).
- 3Expect inconsistency: encryption is carrier- and contact-dependent, so mixed-carrier group chats can block the “Encrypted” state even after you update.
A small lock icon has become the newest status symbol in the most ordinary place: your group chat.
If you’ve updated to Apple’s latest beta, you may have noticed it sitting above a green-bubble conversation like a quiet promise—“Encrypted.” For years, iPhone-to-Android messaging lived in a technical no-man’s-land: sometimes modern enough to send high-resolution photos, often primitive enough to fall back to SMS/MMS, and almost never private in the way people assume “secure messaging” works.
Apple says that changed on May 11, 2026, when it began rolling out end‑to‑end encrypted (E2EE) RCS messaging in beta with iOS 26.5. RCS—Rich Communication Services—is the carrier-backed successor to SMS/MMS, and it’s the protocol behind many green-bubble messages when iPhones text Android phones. Now, at least for eligible conversations, Apple’s Messages app can label those chats “Encrypted” and show a lock icon. (Apple announced the beta rollout in its newsroom update dated May 11, 2026.)
The lock is real progress. It’s also a perfect trigger for a familiar misunderstanding: encryption does not erase the carrier from the equation. It changes what the carrier can see—and what it can’t.
“The lock icon is a meaningful upgrade. It’s not a magic cloak.”
— — TheMurrow Editorial
What exactly changed in May 2026—and why the lock suddenly appeared
Apple’s announcement is unusually crisp: E2EE RCS messaging began rolling out in beta with iOS 26.5 on May 11, 2026. The change is not a redesign, not a new “mode,” not a brand-new messaging app. It’s a feature upgrade to the protocol that often carries iPhone↔Android messages when both sides can use RCS.
RCS matters because it has become the functional replacement for SMS/MMS—at least when carriers and devices support it. SMS/MMS are decades-old systems designed for a world of short texts and low expectations. They were never built to protect message content from intermediaries. RCS, by contrast, supports modern comforts (typing indicators, better media, read receipts), and now, under the right conditions, can support end-to-end encryption.
Apple’s own documentation underscores the shift. Historically, Apple’s support language stated that RCS was not end-to-end encrypted. After the May 11, 2026 rollout, Apple updated its support page to say E2EE RCS is available (in beta) starting with iOS 26.5, with supported carriers. That’s a major revision in Apple’s public posture—and it explains why readers suddenly see a lock on “green bubble” threads and wonder if everything is private now.
RCS matters because it has become the functional replacement for SMS/MMS—at least when carriers and devices support it. SMS/MMS are decades-old systems designed for a world of short texts and low expectations. They were never built to protect message content from intermediaries. RCS, by contrast, supports modern comforts (typing indicators, better media, read receipts), and now, under the right conditions, can support end-to-end encryption.
Apple’s own documentation underscores the shift. Historically, Apple’s support language stated that RCS was not end-to-end encrypted. After the May 11, 2026 rollout, Apple updated its support page to say E2EE RCS is available (in beta) starting with iOS 26.5, with supported carriers. That’s a major revision in Apple’s public posture—and it explains why readers suddenly see a lock on “green bubble” threads and wonder if everything is private now.
The key date, the key version, and the key UI cue
Four concrete facts anchor what people are noticing:
- May 11, 2026: Apple publicly states encrypted RCS begins rolling out that day (beta).
- iOS 26.5: The beta roll-out is tied to this version.
- RCS only: The lock applies to RCS chats—not to SMS/MMS.
- UI indicator: Messages can show a lock icon and “Encrypted” label for eligible RCS conversations.
That last point is what makes the shift feel sudden. Encryption features often arrive invisibly. A lock icon turns a network change into a daily, emotional experience.
- May 11, 2026: Apple publicly states encrypted RCS begins rolling out that day (beta).
- iOS 26.5: The beta roll-out is tied to this version.
- RCS only: The lock applies to RCS chats—not to SMS/MMS.
- UI indicator: Messages can show a lock icon and “Encrypted” label for eligible RCS conversations.
That last point is what makes the shift feel sudden. Encryption features often arrive invisibly. A lock icon turns a network change into a daily, emotional experience.
May 11, 2026
Apple’s stated start date for the beta rollout of end‑to‑end encrypted RCS messaging.
iOS 26.5
The version Apple ties to the (beta) rollout of E2EE for RCS conversations with supported carriers.
RCS isn’t iMessage—and that difference is the whole story
Apple’s messaging world has long been split by color. Blue bubbles signal iMessage, Apple’s proprietary messaging system. Green bubbles signal messages traveling outside that system—historically SMS/MMS, and more recently RCS.
The lock icon many people now see sits in the green-bubble universe. That’s the first reason the rollout is consequential: it directly addresses the weakest link in most people’s phone life, the conversations that cross the iPhone/Android boundary.
Apple frames this as a standards-based move, not a one-off détente with Google. According to Apple and Google’s positioning, the “rules” for E2EE RCS and the user experience cues are defined in GSMA’s RCS Universal Profile 3.0, published March 13, 2025. That matters because it signals a broader industry direction: carriers and device makers agreeing on a common baseline, rather than each platform inventing its own security scheme.
Still, “standards-based” doesn’t mean “frictionless.” RCS is a carrier-provided service. Carriers support it unevenly, and even where RCS works, encryption depends on whether the other person’s carrier and device can participate.
The lock icon many people now see sits in the green-bubble universe. That’s the first reason the rollout is consequential: it directly addresses the weakest link in most people’s phone life, the conversations that cross the iPhone/Android boundary.
Apple frames this as a standards-based move, not a one-off détente with Google. According to Apple and Google’s positioning, the “rules” for E2EE RCS and the user experience cues are defined in GSMA’s RCS Universal Profile 3.0, published March 13, 2025. That matters because it signals a broader industry direction: carriers and device makers agreeing on a common baseline, rather than each platform inventing its own security scheme.
Still, “standards-based” doesn’t mean “frictionless.” RCS is a carrier-provided service. Carriers support it unevenly, and even where RCS works, encryption depends on whether the other person’s carrier and device can participate.
Green bubbles now have tiers
The green-bubble category contains at least three realities:
- SMS/MMS (unencrypted): fallback mode when RCS isn’t available.
- RCS without E2EE (not encrypted end-to-end): modern features, but not content-protected against intermediaries in the same way.
- RCS with E2EE (“Encrypted” lock): message content protected in transit between devices.
That hierarchy is why the lock icon feels like a new promise—and why it’s crucial to understand what the promise actually covers.
- SMS/MMS (unencrypted): fallback mode when RCS isn’t available.
- RCS without E2EE (not encrypted end-to-end): modern features, but not content-protected against intermediaries in the same way.
- RCS with E2EE (“Encrypted” lock): message content protected in transit between devices.
That hierarchy is why the lock icon feels like a new promise—and why it’s crucial to understand what the promise actually covers.
“Green bubbles were never a single technology. Apple’s lock icon makes that visible.”
— — TheMurrow Editorial
Blue vs. green bubbles (what the lock is actually signaling)
Before
- Blue (iMessage)
- Apple-controlled system
- long associated with end‑to‑end encryption
After
- Green (SMS/MMS or RCS)
- carrier-backed delivery
- encryption varies by mode and eligibility
What end-to-end encryption protects—and what it doesn’t
Apple’s newsroom statement is direct about the benefit: when RCS messages are end-to-end encrypted, they “can’t be read while they’re sent between devices.” That is the core definition most people care about: intermediaries should not be able to read the content of your texts or media in transit.
But the support documentation adds an equally important caveat: RCS is carrier-provided, and the setup process involves your phone communicating with your carrier and their partners to authenticate your device and establish service. During that process, Apple says user identifiers are exchanged—including your phone number and, depending on the carrier, your current IP address.
Those two statements can both be true. End-to-end encryption is designed to protect content (the body of your message, images, videos) from being read by intermediaries. It does not magically prevent a delivery system from learning the basic facts it needs to deliver messages—or the operational metadata networks generate as they function.
But the support documentation adds an equally important caveat: RCS is carrier-provided, and the setup process involves your phone communicating with your carrier and their partners to authenticate your device and establish service. During that process, Apple says user identifiers are exchanged—including your phone number and, depending on the carrier, your current IP address.
Those two statements can both be true. End-to-end encryption is designed to protect content (the body of your message, images, videos) from being read by intermediaries. It does not magically prevent a delivery system from learning the basic facts it needs to deliver messages—or the operational metadata networks generate as they function.
Content vs. metadata: the distinction readers deserve
A precise way to think about the new lock icon:
- Protected: Message content while it travels between devices (Apple’s stated benefit).
- Not eliminated: Carrier involvement in provisioning and routing; identifiers exchanged for authentication; metadata created by the act of sending messages.
Metadata is not a trivial footnote. Even without reading content, a carrier may be able to learn or infer information such as who is messaging whom, when, and sometimes from where (especially if IP address is involved in setup). The research doesn’t claim what any carrier retains or for how long, and a careful reader shouldn’t assume. The key point is structural: networks need routing signals, and those signals create data.
- Protected: Message content while it travels between devices (Apple’s stated benefit).
- Not eliminated: Carrier involvement in provisioning and routing; identifiers exchanged for authentication; metadata created by the act of sending messages.
Metadata is not a trivial footnote. Even without reading content, a carrier may be able to learn or infer information such as who is messaging whom, when, and sometimes from where (especially if IP address is involved in setup). The research doesn’t claim what any carrier retains or for how long, and a careful reader shouldn’t assume. The key point is structural: networks need routing signals, and those signals create data.
The honest headline: better privacy, not perfect invisibility
If you see “Encrypted,” the defensible takeaway—based on Apple’s own language—is that intermediaries should not be able to read the message body while it’s being sent. That’s the win.
The limitation is not that encryption is fake; it’s that encryption has boundaries. It secures content. It doesn’t remove the carrier as a participant in the system.
The limitation is not that encryption is fake; it’s that encryption has boundaries. It secures content. It doesn’t remove the carrier as a participant in the system.
Key takeaway
“Encrypted” in a green-bubble RCS thread is a content-protection signal—not proof the carrier disappears from setup, routing, or metadata generation.
March 13, 2025
Publication date cited for GSMA’s RCS Universal Profile 3.0, which defines expectations for E2EE RCS and UX cues.
Why your carrier still matters, even when the chat says “Encrypted”
Apple’s support page is unusually candid: when an iPhone connects to a cellular network to set up RCS, it communicates with your carrier and their partners, exchanging identifiers to authenticate and provide a connection. Apple explicitly lists phone number, and “depending on the carrier,” current IP address.
That detail is the practical counterweight to the lock icon’s psychological impact. “Encrypted” can easily be read as “no one else is involved.” RCS doesn’t work that way. It’s designed as a carrier service, and carrier services inherently involve carrier infrastructure.
From an editorial perspective, the careful claim is this: your carrier shouldn’t be able to read the content of an end‑to‑end encrypted RCS message, but your carrier can still participate in the system in ways that generate data about the communication.
That detail is the practical counterweight to the lock icon’s psychological impact. “Encrypted” can easily be read as “no one else is involved.” RCS doesn’t work that way. It’s designed as a carrier service, and carrier services inherently involve carrier infrastructure.
From an editorial perspective, the careful claim is this: your carrier shouldn’t be able to read the content of an end‑to‑end encrypted RCS message, but your carrier can still participate in the system in ways that generate data about the communication.
What the carrier can plausibly know without reading content
Apple’s documentation supports several concrete points:
- Your phone number is involved in authentication/provisioning.
- Your IP address may be exchanged depending on carrier.
- Provisioning requires communication with the carrier and its partners.
Even without any speculation about retention policies, these facts imply the carrier ecosystem can observe that RCS service is being set up and used and can associate service to identifiers. Many readers will find that uncomfortable. Others will shrug: carriers already know your number, and your phone already talks to them constantly.
The important move is not to panic readers, but to replace a vague feeling (“the lock means total secrecy”) with an accurate mental model (“the lock mainly protects message content; the network still sees operational signals”).
- Your phone number is involved in authentication/provisioning.
- Your IP address may be exchanged depending on carrier.
- Provisioning requires communication with the carrier and its partners.
Even without any speculation about retention policies, these facts imply the carrier ecosystem can observe that RCS service is being set up and used and can associate service to identifiers. Many readers will find that uncomfortable. Others will shrug: carriers already know your number, and your phone already talks to them constantly.
The important move is not to panic readers, but to replace a vague feeling (“the lock means total secrecy”) with an accurate mental model (“the lock mainly protects message content; the network still sees operational signals”).
“End‑to‑end encryption can block content access while still leaving a trail of operational breadcrumbs.”
— — TheMurrow Editorial
Editor’s Note
This article does not claim what any carrier retains or for how long. It focuses on what Apple’s documentation says is structurally exchanged during RCS setup and use.
When the lock appears—and why it often doesn’t
The lock icon is not a promise Apple can make unilaterally. Apple’s own support language says RCS E2EE is available with supported carriers and will roll out over time. Even if your carrier supports encrypted RCS, each conversation depends on whether your contact’s carrier supports it.
That is the failure mode most people will hit first: “I updated, why do I still not see the lock?” The answer is frequently not on your phone.
That is the failure mode most people will hit first: “I updated, why do I still not see the lock?” The answer is frequently not on your phone.
The “two-sided” nature of encrypted RCS
Unlike iMessage (which Apple controls end-to-end), RCS relies on an ecosystem: carriers, devices, and standards compliance. Encryption status can vary by thread because eligibility is determined per conversation.
A realistic set of reasons the lock might not appear includes:
- Your carrier does not yet support E2EE RCS (Apple says rollout happens over time).
- Your contact’s carrier does not support E2EE RCS, even if yours does.
- The conversation is not using RCS at all and has fallen back to SMS/MMS.
Apple’s documentation also implicitly sets a rule of thumb: if the indicator isn’t there, assume the message is not end-to-end encrypted. That may feel blunt, but it’s better than guessing.
A realistic set of reasons the lock might not appear includes:
- Your carrier does not yet support E2EE RCS (Apple says rollout happens over time).
- Your contact’s carrier does not support E2EE RCS, even if yours does.
- The conversation is not using RCS at all and has fallen back to SMS/MMS.
Apple’s documentation also implicitly sets a rule of thumb: if the indicator isn’t there, assume the message is not end-to-end encrypted. That may feel blunt, but it’s better than guessing.
A real-world example: the “mixed carrier” group chat problem
Consider a family group chat: two iPhones on one carrier, one Android phone on a second carrier, and a fourth person who travels frequently. In that scenario, the thread’s encryption status can be constrained by the least-supported link. A single participant on an unsupported carrier can keep the thread from qualifying for the “Encrypted” state.
That’s not a bug; it’s the nature of standards-based messaging in a carrier world.
That’s not a bug; it’s the nature of standards-based messaging in a carrier world.
Quick reasons you won’t see the lock
- ✓Your carrier hasn’t enabled E2EE RCS yet (rollout over time)
- ✓Your contact’s carrier doesn’t support E2EE RCS
- ✓The thread fell back to SMS/MMS instead of RCS
The standards story: why GSMA Universal Profile 3.0 matters
Apple and Google have both pointed toward an industry-standard approach rather than a proprietary detour. The research notes that GSMA’s RCS Universal Profile 3.0—published March 13, 2025—defines E2EE requirements and user experience conventions.
For readers, the significance is less about GSMA politics and more about longevity. Standards determine whether encryption becomes the default for cross-platform messaging or remains a special feature you only get under ideal conditions.
For readers, the significance is less about GSMA politics and more about longevity. Standards determine whether encryption becomes the default for cross-platform messaging or remains a special feature you only get under ideal conditions.
Interoperability versus control
iMessage’s strongest feature is control: Apple owns the client, the service, and the user experience. RCS is the opposite: it’s interoperable, carrier-backed, and designed to work across vendors. That openness can expand reach, but it also introduces variability—carrier-by-carrier rollout, per-conversation differences, and edge cases that confuse users.
Still, standards are how the industry crawls toward “secure by default.” Universal Profile 3.0 is a sign that E2EE is no longer a boutique feature reserved for single-app ecosystems.
Still, standards are how the industry crawls toward “secure by default.” Universal Profile 3.0 is a sign that E2EE is no longer a boutique feature reserved for single-app ecosystems.
A sober view: standards don’t remove incentives
Even with a standard, carriers remain part of the operational pipeline, and Apple’s own support page stresses that reality. Standards can specify encryption, but they can’t abolish the need for provisioning, authentication, and routing.
That’s why the lock icon should be read as a limited but meaningful signal: content protection in transit, within a carrier-connected system.
That’s why the lock icon should be read as a limited but meaningful signal: content protection in transit, within a carrier-connected system.
3 tiers
Apple’s lock icon effectively reveals three green-bubble realities: SMS/MMS, RCS without E2EE, and RCS with E2EE.
Practical takeaways: how to read the lock, and what to do if you care about privacy
For most people, the lock icon will simply be welcome. It means cross-platform messaging is finally catching up to the expectations set by modern secure apps.
For readers who actually make decisions based on threat models—journalists, activists, people handling sensitive personal situations—the details matter. Apple’s own language provides a clean framework.
For readers who actually make decisions based on threat models—journalists, activists, people handling sensitive personal situations—the details matter. Apple’s own language provides a clean framework.
How to interpret the “Encrypted” label
Use these rules, grounded in Apple’s documentation:
- If Messages shows “Encrypted” for an RCS thread, Apple says messages “can’t be read while they’re sent between devices.”
- If the indicator isn’t present, do not assume end-to-end encryption is active—your chat may be unencrypted RCS or may have fallen back to SMS/MMS.
- Even when encrypted, RCS setup involves communication with your carrier and their partners, and identifiers such as phone number (and sometimes IP address) may be exchanged.
- If Messages shows “Encrypted” for an RCS thread, Apple says messages “can’t be read while they’re sent between devices.”
- If the indicator isn’t present, do not assume end-to-end encryption is active—your chat may be unencrypted RCS or may have fallen back to SMS/MMS.
- Even when encrypted, RCS setup involves communication with your carrier and their partners, and identifiers such as phone number (and sometimes IP address) may be exchanged.
If you’re troubleshooting: what to check first
Practical steps that follow directly from the rollout constraints:
- Confirm you’re on iOS 26.5 (beta) if you expect the feature today.
- Remember it’s carrier-dependent and contact-dependent; your update alone doesn’t guarantee encryption.
- Watch for the UI cue: the lock/“Encrypted” label is the clearest user-facing status signal Apple provides.
- Confirm you’re on iOS 26.5 (beta) if you expect the feature today.
- Remember it’s carrier-dependent and contact-dependent; your update alone doesn’t guarantee encryption.
- Watch for the UI cue: the lock/“Encrypted” label is the clearest user-facing status signal Apple provides.
Who should care most about metadata
Even perfect content encryption doesn’t prevent patterns from being visible to intermediaries. If your concerns include exposure of communication relationships or timing—who you talk to, and when—then metadata matters.
Apple’s support page gives you a reason to treat RCS as more private than SMS/MMS, but not as a system that makes carriers irrelevant.
Apple’s support page gives you a reason to treat RCS as more private than SMS/MMS, but not as a system that makes carriers irrelevant.
A simple way to “read” a green-bubble thread
- 1.Look for the lock/“Encrypted” label; treat it as the only reliable user-facing E2EE signal.
- 2.If there’s no indicator, assume it may be unencrypted RCS or SMS/MMS fallback.
- 3.Remember that even with E2EE, RCS remains carrier-provided, with provisioning and identifiers exchanged.
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering technology.
Frequently Asked Questions
What does the lock icon mean in a green-bubble chat?
A lock icon or “Encrypted” label indicates the conversation is using end‑to‑end encrypted RCS, where Apple says messages “can’t be read while they’re sent between devices.”
Does “Encrypted” mean my carrier can’t read my texts?
It means intermediaries—including carriers—should not be able to read message content in transit for threads marked “Encrypted,” but RCS is carrier-provided and setup can exchange identifiers like phone number and sometimes IP address.
Why don’t I see the lock even after updating?
Apple says E2EE RCS is available with supported carriers and rolls out over time; it can also depend on your contact’s carrier. Without the indicator, the chat may be unencrypted RCS or SMS/MMS fallback.
Is this the same as iMessage encryption?
No. iMessage (blue bubbles) is Apple’s proprietary system. The lock discussed here is tied to RCS (green bubbles) and Apple’s iOS 26.5 beta rollout of E2EE RCS.
What is RCS Universal Profile 3.0, and why does it matter?
GSMA’s RCS Universal Profile 3.0 (published March 13, 2025) defines requirements for RCS features, including E2EE expectations and user experience cues, supporting cross-platform consistency.
If messages are encrypted, what data can still be shared?
Apple says RCS setup involves communication with your carrier and their partners and exchanges identifiers including your phone number and, depending on carrier, your current IP address—metadata needed for provisioning and delivery.
