Who Can Actually Read Your Texts: Carriers, Apple, Google, Police

Short answer

For plain SMS and MMS, yes — your carrier processes the contents in order to deliver them, and retains records for some period. For iMessage and for encrypted RCS, the content is unreadable to them, though who you messaged and when is not. Encryption also does nothing about backups, the other person's phone, or anyone holding an unlocked device.

Start with the protocol, not the company

Nearly every article on this subject answers the wrong question. “Can my carrier read my texts” has no single answer, because “texts” covers three systems with completely different properties. The company is not the variable. The protocol is.

SMS and MMS: yes, by design. Not through any special access or surveillance programme — it is how delivery works. Your message travels to the carrier’s message centre, which stores it, works out where the recipient is, and forwards it. The content sits in that system in readable form as an ordinary part of being delivered. There is no encryption anywhere in the process. If a message was queued because the recipient was offline, it sits there readable until it is delivered.

Carriers also retain records. How much and for how long varies by company and by jurisdiction, and it is generally longer for the metadata — who, when, which numbers — than for content.

iMessage: no. Encrypted end to end between Apple devices. The content is not readable by your carrier — it does not go through them as a message at all, only as ordinary internet traffic. It is not readable by Apple either, with an important exception covered below.

RCS: it depends, and this is the whole reason this site exists. RCS without end-to-end encryption is carried by the network in a form the network can process, which puts it closer to SMS than people assume. RCS with encryption active is closer to iMessage. Which one you have depends on both phones and on whether your carriers have shipped the encrypted variant, and the honest answer for a specific conversation is usually “check the padlock”. Our checker walks that.

What encryption does not protect

This section matters more than the yes-or-no, because people consistently overestimate what they are buying, and the gaps are where things actually go wrong.

Backups. This is the biggest one. If your messages are backed up to a cloud service and that backup is not itself encrypted in a way the provider cannot open, then a readable copy exists somewhere regardless of how well the messages were protected in transit. For iMessage specifically, iCloud Backup without Advanced Data Protection is understood to place a copy in Apple’s hands.

The awkward part is that it takes both of you. Your messages sit in their backup too, and you have no visibility into or control over their settings.

Metadata. Encryption protects the contents of a message, not the fact of it. Who you messaged, when, how often, roughly from where — that has to be readable by whatever is routing the message, or it cannot be routed. Metadata is frequently more revealing than content, and it is retained longer.

The other person’s device. The most common way a private message becomes public is that the recipient shows someone. Encryption is irrelevant to screenshots, forwarding, and a phone left unlocked on a table.

Anyone holding an unlocked phone. The messages are readable on the device by definition. That is what a messaging app is.

Notification previews. A message you thought was private is displayed on a lock screen to anyone standing nearby, encrypted or not.

Party by party

Your carrier. Sees SMS and MMS content. Sees unencrypted RCS content. Does not see iMessage or encrypted RCS content, but sees that a conversation happened, with whom, and when — because it routes it.

Apple. Not in the path for RCS or SMS at all. For iMessage, cannot read the conversation itself, but the backup exception above is real and is the case most people are affected by.

Google. Not in the path for iMessage or SMS. For RCS, Google Messages is the client for most Android users and, on many networks, the messaging back end as well — so routing information passes through it even when content does not. If the chat is not encrypted, content passes through whatever back end is carrying it.

Someone on the same Wi-Fi. Essentially no, in every case, and this is the one people worry about disproportionately. Even unencrypted RCS uses a secured connection between your phone and the server; SMS does not go over Wi-Fi at all. The coffee-shop eavesdropper is not the real risk here. The server is.

Law enforcement with a warrant. For SMS and MMS, carriers hold records and can be compelled to produce them within their retention window. For encrypted conversations, content in transit is out of reach, but metadata is not, and neither are backups or either physical device. “End-to-end encrypted” answers one question in that list and none of the others.

What to actually do about it

For most conversations, do nothing. The realistic threat to an ordinary text about dinner is not a carrier employee reading it. It is somebody picking up a phone. Lock your phone, turn off message previews on the lock screen, and you have addressed more real risk than any protocol change.

If it matters, do not rely on a prediction. Do not reason from an article — including this one — that your conversation is probably encrypted. Look for the padlock on the device, or use something where the answer is not conditional.

If it genuinely matters, use a dedicated app. Signal or WhatsApp encrypt everything by default on every platform, with no carrier involvement and no rollout to wait for. Signal additionally minimises the metadata it holds, which RCS by its nature cannot. How the three compare properly.

Sort out your backups. This is the highest-value thing most people can do, and almost nobody does it. If your messages are in an unencrypted cloud backup, the encryption on the wire was largely decorative.

And be realistic about metadata. No mainstream messaging system hides who you talk to from everyone. If that is your requirement, you need a different tool and probably different advice than a website about text messages can responsibly give.

Check your own setup

Get the party-by-party answer for your specific combination of phones and carrier, rather than the general one.

Run the checker

Version facts on this page: not verified yet — the site-wide verification pass has not been completed. See the update log

Related guides

Published 1 September 2026. Last reviewed 1 September 2026. This guide depends on facts F27, F25, F2, F3, F11, F22 in our verification table — if one of those changes, this page gets rewritten and the change is logged in the update log.