# What Is an Overbroad Request? Definition and Remedies | Kodex

Source: https://www.kodexglobal.com/glossary/overbroad-request

> An overbroad request asks a company for more user data than its legal authority supports. Learn the grounds for objecting and what a provider does about one.

Request Operations

## Overbroad Request

An overbroad request is a request for user data that asks for more than the legal authority behind it supports, such as a wider date range than the matter justifies or a data category that the instrument cannot reach.

Also known as
overly broad request, overbroad subpoena, overbroad warrant

Every instrument has limits. A subpoena reaches the records the statute lists for it, and a warrant reaches what it particularly describes. A request that goes past those limits is overbroad, and the scope of responsive records is the question the company answers before it produces anything.

### What overbreadth looks like

What it looks likeBasis for narrowing

Too many accounts The request names more accounts than the matter connects to the investigation Particularity for a warrant; undue burden for an order or a civil subpoena

Too long a period The date range runs beyond what the matter justifies Unreasonable or oppressive (Fed. R. Crim. P. 17(c)(2)); unusually voluminous (§ 2703(d))

Wrong instrument for the data A subpoena asks for records beyond the list in § 2703(c)(2) Section 2703(c)(1) calls for a warrant or a § 2703(d) order for those records

Vague description The request does not identify the account or the records with precision Warrants must particularly describe the place to be searched and the things to be seized

### The legal bases for objecting

- Warrants. The Fourth Amendment provides that no warrants shall issue but upon probable cause and particularly describing the place to be searched and the persons or things to be seized.

- Criminal subpoenas. On motion made promptly, the court can quash or modify a subpoena if compliance would be unreasonable or oppressive (Fed. R. Crim. P. 17(c)(2)).

- Civil subpoenas. The court for the district where compliance is required must quash or modify a subpoena that subjects a person to undue burden (Fed. R. Civ. P. 45(d)(3)(A)(iv)). Rule 45(d)(1) requires the issuing party to take reasonable steps to avoid imposing undue burden or expense.

- Section 2703(d) orders. On a motion made promptly by the service provider, the court can quash or modify an order if the records requested are unusually voluminous or compliance would otherwise cause an undue burden.

### What a provider does about one

A provider that receives an overbroad request has three routes.

- Ask the requester to narrow it.

- Produce the part that the instrument supports and record what was left out and why.

- Move to quash or modify, within the time the governing rule allows.

For a subpoena, the motion has to come promptly under Rule 17(c)(2), and a civil subpoena carries the 14-day objection window in Rule 45(d)(2)(B).

### Why producing beyond scope is a risk

Section 2702(a) bars a provider from divulging stored contents, and it bars disclosure of subscriber records to a governmental entity, outside the listed exceptions. Section 2703(e) protects a provider that provides information in accordance with the terms of a court order, warrant, subpoena, statutory authorisation or certification. A production past those terms falls outside that protection.

Under § 2707(a), a subscriber aggrieved by a violation committed with a knowing or intentional state of mind can bring a civil action, and § 2707(c) sets damages of at least $1,000 for a plaintiff entitled to recover. Section 2707(e) makes good-faith reliance on a court warrant or order, a grand jury subpoena, a legislative authorization or a statutory authorization a complete defence.

FAQ

### Frequently asked questions

What makes a request overbroad?

A request is overbroad when it asks for more than its instrument reaches. The test depends on the instrument: particularity for a warrant, unreasonable or oppressive compliance for a criminal subpoena, and undue burden for a civil subpoena or a § 2703(d) order.

Can a provider move to quash a § 2703(d) order?

Yes. The final sentence of § 2703(d) provides that a court issuing an order, on a motion made promptly by the service provider, can quash or modify it if the information or records requested are unusually voluminous or compliance would otherwise cause an undue burden on the provider.

Is a provider protected if it produces what a request asks for?

Section 2703(e) bars a cause of action against a provider for providing information in accordance with the terms of a court order, warrant, subpoena, statutory authorisation or certification. A production beyond those terms falls outside that text. Section 2707(e) separately makes good-faith reliance on specified process a complete defence to a civil or criminal action.

Glossary

### Related terms

#### Responsive Records

Responsive records are the documents and data that actually fall within the scope of a specific request. Determining what is responsive is a scoping judgement, and getting it wrong in either direction means either failing to comply or disclosing more of a user’s data than the law required.

#### Subpoena

A subpoena is a legal order compelling a person or company to produce documents or testimony. In data request work it is the lowest-threshold instrument: it does not require a judge’s prior approval and generally reaches basic subscriber information rather than the contents of communications.

#### Geofence Warrant

A geofence warrant is a search warrant that asks a provider for location records of every device inside a defined area during a defined time window, with no named suspect. Investigators use the results to find the devices, and then the people, they want to examine.

#### Redaction

Redaction is the permanent removal of information from records before they are produced, typically to withhold data about third parties or material outside a request’s scope. Effective redaction removes the underlying data rather than obscuring it visually, and failures here are usually technical rather than editorial.

Scope review is where an overbroad request gets caught. See how Kodex structures review and production.
Learn more
