Can You Subpoena Verizon, AT&T, or T-Mobile for Text Messages?

What carriers actually keep vs. what they don't

Carriers generally do keep metadata for some period of time — records showing that a text was sent from one number to another, and when, sometimes called call detail records or CDRs. That metadata is genuinely obtainable in many cases through the right legal process, and it can be useful on its own (establishing frequency or timing of contact, for example, even without the words themselves).

What carriers generally do not keep is the content of the message — the actual words. A standard SMS or MMS is transmitted through the carrier's network and delivered to the recipient's device; it isn't typically warehoused by the carrier as a stored copy afterward. That's a structural difference from an over-the-top messaging app like iMessage, WhatsApp, or Facebook Messenger, where message content (or an encrypted version of it) may pass through or be held on the company's own servers, or where a cloud backup of message content exists separately from the device. Exactly how long any given carrier retains metadata, and whether it retains any content at all, is the kind of detail that varies and changes over time — this is a general description of the pattern, not a specific retention schedule for any one carrier, and it's worth confirming directly with counsel or the carrier's own current published policy if the exact window matters to your case.

The bigger obstacle: the Stored Communications Act

Even setting the retention question aside, there's a federal law that specifically limits what a provider can be compelled to hand over. The Stored Communications Act, 18 U.S.C. § 2701 et seq., generally restricts electronic communications providers from disclosing the content of stored communications in response to an ordinary civil subpoena — as opposed to a warrant meeting a higher standard, typically available only in a criminal investigation. In plain terms: a family-law litigant's subpoena to a carrier or a tech platform asking for the words of a conversation is frequently refused, with the provider citing the SCA, no matter how properly the subpoena was issued under your state's civil procedure rules. State civil procedure gives you the power to issue a subpoena; it doesn't override a federal statute that tells the recipient it can't comply with the content request.

This is well-established as a general principle — courts that have addressed civil subpoenas seeking private message content have repeatedly recognized the SCA as a real bar, not just a technicality providers raise to be difficult. The specific contours (which kinds of accounts and storage count as covered communications, and in what circumstances) can get technical, which is exactly the kind of question worth putting in front of an attorney rather than assuming either way.

What actually works instead

The SCA problem is specifically about compelling a third party — the carrier or platform — to hand over someone else's content without their cooperation. It doesn't apply the same way to:

• A request for production or subpoena directed at the person who actually has the messages, rather than the carrier. That request goes to a party (or witness) with a legal duty to respond, and it isn't blocked by the SCA the same way a third-party provider request is.
• A forensic examination of the device itself — with the device owner's cooperation or a court order — which can sometimes recover message content directly from the phone, sidestepping the carrier question entirely.
• Your own copy of a conversation you were part of. Getting your own messages isn't a third-party disclosure problem at all — it's your data. The SCA issue only shows up when you're trying to compel a stranger to the conversation (a carrier or platform) to turn over someone else's content.

We cover the person-and-device-focused approach in more detail, including how it fits into the broader discovery process, in how to get the other parent's text messages through discovery.