2703(d) Order

The 2703(d) order occupies the middle rung of the Stored Communications Act ladder. It exists because Congress recognised that not all non-content data is equally sensitive: the fact that an account exists is different from a detailed log of everywhere it connected from.

What a 2703(d) order reaches

It compels records concerning an electronic communication service or remote computing service. That is the transactional layer sitting between basic subscriber data and content:

  • Connection logs and session records
  • Addressing and routing information, such as who a user communicated with and when
  • Length and type of service used
  • Device and network identifiers associated with an account

What it does not reach is the content of communications. That boundary is the point of the tiered structure.

Where it sits between a subpoena and a warrant

2703(d) orderSubpoena
Legal standardSpecific and articulable factsRelevance to an investigation
Who issues itA judge or magistrateProsecutor, grand jury, or agency
Prior judicial reviewYesNot generally
Reaches transactional recordsYesLimited to basic subscriber information
Reaches contentNoNo

Understanding the ladder matters at intake because requesters do not always ask for what their instrument can compel. A subpoena that demands detailed connection logs is asking for records that generally require a 2703(d) order, and a company producing them anyway has disclosed more than the law required of it.

What it means for a company receiving one

  • Check the instrument against the ask. The most common problem is scope creep, where the attached request asks for content the order cannot compel.
  • Note the date range. Transactional records accumulate quickly, and an unbounded range is worth pushing back on.
  • Check for a separate non-disclosure order. A 2703(d) order can be accompanied by a § 2705(b) order restricting notice, but it does not restrict notice on its own.

Why it is contested

The tiering was designed in 1986, and technology moved. Location data was the sharpest example: cell site location information was long obtained under 2703(d), until the Supreme Court held in Carpenter v. United States (2018) that acquiring historical cell site records is a search requiring a warrant. That decision did not dismantle the 2703(d) framework, but it established that some categories of record are sensitive enough to demand probable cause regardless of which tier they nominally occupy. Similar arguments continue over other categories of transactional data.

Frequently asked questions

What does specific and articulable facts mean in practice?

It requires the government to point to concrete facts supporting a reasonable belief that the records are relevant and material to an ongoing criminal investigation. It is more than a hunch and more than mere relevance, but it does not require showing that a crime probably occurred, which is what probable cause demands.

Can a 2703(d) order compel message content?

No. Content requires a search warrant. A 2703(d) order reaches records concerning an account (logs, connection records, addressing information, service use) but not what was written or stored inside it.

Who issues a 2703(d) order?

A court. Unlike a subpoena, which a prosecutor or agency can issue directly, a 2703(d) order requires a judge or magistrate to review the government’s factual showing and decide that the standard is met.

See what
we can do
for you.

Request a demo