Geofence Warrants
How reverse-location searches work, why they differ from traditional suspect-based warrants, what the Supreme Court held in Chatrie v. United States in 2026, and what agencies should understand about location data, probable cause, particularity, minimization, provider architecture, and the future of reverse digital searches.
What this explainer does
Traditional warrants usually begin with a known person, device, account, or place and seek evidence associated with that target. A geofence warrant works in the opposite direction. Investigators begin with a geographic area and a time window and ask a provider to identify devices whose stored location information places them within or near that area.
That “reverse” structure can be extraordinarily useful when police know where and when a crime occurred but do not yet know the offender's identity. It also creates distinctive Fourth Amendment problems because the initial search may involve data associated with people who are not suspected of wrongdoing.
In Chatrie v. United States, decided June 29, 2026, the Supreme Court held that police conducted a Fourth Amendment search when they acquired Chatrie's Google Location History data. The Court did not decide whether the particular multi-step warrant satisfied probable cause and particularity. It remanded those questions for the Fourth Circuit to address in the first instance.
1. Overview
A geofence warrant is a form of reverse-location process: law enforcement identifies a place and time associated with a crime and seeks stored digital location information that can reveal which devices were present.
The technique became associated most prominently with Google's former cloud-based Location History system. In the classic model, investigators served Google with a warrant describing a geographic boundary and time period. Google searched its stored Location History data for devices that reported locations within the geofence, initially returned anonymized device information, and—after narrowing—could provide identifying account information for selected users.
The evidentiary theory is straightforward: the offender may have carried a phone or other device that recorded its location near the crime scene. But unlike a traditional warrant, police do not necessarily know the device or user before the search begins. The search is designed to help identify the suspect.
2. Why Geofence Warrants Are Called “Reverse” Warrants
Investigators identify a person, phone number, account, device, or address and seek records associated with that known target.
Investigators identify a place and time and seek records that will help reveal which unknown devices or users were there.
Reverse searching is not limited conceptually to one provider or one historical Google product. Similar investigative logic can arise whenever a database can be searched backward from an event, location, characteristic, or query to identify people or devices that were previously unknown.
3. What Location Data Is Involved?
Not all location data is the same. The Supreme Court's 2026 Chatrie decision involved Google's historical “Location History” records, not ordinary carrier CSLI. Those technologies can overlap in purpose—both can describe location—but they are generated and stored differently.
| Data Type | How It Is Generated | Typical Precision / Character | Legal Significance |
|---|---|---|---|
| Google Location History / Timeline data | Location signals associated with Google services and devices when the feature is enabled | Can use GPS, Wi-Fi, Bluetooth, and other location signals; historically capable of detailed coordinates | Chatrie held acquisition of the user's protected location data was a Fourth Amendment search |
| Historical CSLI | Carrier records created when a phone communicates with cellular infrastructure | Generally cell-site / sector based, though network technology can affect precision | Carpenter held acquisition of seven days of historical CSLI was a search requiring a warrant in the circumstances presented |
| Real-time / prospective location data | Current or future device or network location information | Varies widely by provider and technique | Requires separate analysis; Chatrie did not establish a complete rule for every real-time method |
| App / platform location records | Generated by applications or services that collect location | Depends on application permissions, sensors, storage, and architecture | Legal process and privacy analysis depend on the specific data and provider |
4. The Classic Multi-Step Geofence Workflow
The warrant in Chatrie used the multi-stage process that became familiar in litigation over Google geofence warrants. The exact procedure depended on the warrant and provider, but the basic structure was intended to narrow a broad first-stage return before revealing identities.
The Chatrie Example
In Chatrie, Google initially returned anonymized data for 19 users within the geofence during the relevant hour. Investigators narrowed that list to nine users and received additional anonymized movement data for a longer two-hour period. They then narrowed the list to three users, after which Google produced identifying information. Chatrie was one of the three.
5. Chatrie v. United States — The 2026 Supreme Court Rule
On June 29, 2026, the Supreme Court decided Chatrie v. United States, No. 25-112. The Court granted review on the question whether police violated the Fourth Amendment by obtaining Chatrie's location data through the geofence process.
What the Court Held
The Court extended the privacy principles of Carpenter v. United States beyond the specific seven-day CSLI context. It rejected the argument that the short duration involved in Chatrie—roughly two hours of location information—automatically removed the data from Fourth Amendment protection.
The Court also rejected a categorical third-party-doctrine argument. It reasoned that location information of this kind was not meaningfully “shared” with Google in the conventional sense simply because the provider possessed it as part of ordinary use of digital services.
What the Court Did Not Decide
The Court did not decide whether the warrant established constitutionally sufficient probable cause for the search at each stage.
The Court did not decide whether the warrant sufficiently constrained the area, data, users, or narrowing process.
The Court did not resolve the exclusionary-rule question and left the Fourth Circuit free to reconsider it in light of the opinion.
This distinction is critical. Chatrie does not say that every possible geofence warrant is categorically invalid, nor does it say that every geofence warrant is valid if signed by a magistrate. It establishes that acquiring the protected location information is a search and therefore places the government's conduct inside the Fourth Amendment framework.
6. Google's 2025 Architecture Change
The modern operational landscape changed even before the Supreme Court decided Chatrie. As the Court itself noted, Google changed its Location History architecture in July 2025. Google now stores that Location History data on individual users' devices rather than in the centralized server architecture at issue in Chatrie.
This means agencies should not treat the old Google Sensorvault workflow as a presently available investigative technique simply because older warrant templates, training materials, or case law describe it. Provider architecture matters. A warrant cannot compel a company to produce historical data that it does not centrally possess or cannot technically retrieve.
Why Chatrie Still Matters
The constitutional rule remains significant even if a particular provider changes its architecture. Other databases, platforms, and future technologies may support reverse-location searches. Chatrie's treatment of personal location information, short-duration tracking, third-party possession, and digital privacy will therefore affect more than one discontinued workflow.
7. Probable Cause in a Reverse Search
Probable cause is unusually difficult in the reverse-warrant context because the government does not begin by identifying a suspect whose records are sought. Instead, the government often asks a provider to search a larger pool of users to identify unknown devices that may include the offender.
The Nexus Problem
A strong affidavit should explain why there is reason to believe the offender carried a device, why the relevant provider or data source is likely to contain responsive information, and why the selected geographic and temporal boundaries are tied to the crime rather than merely convenient.
Explain what is known about the offense, timing, entry and exit routes, witness observations, video, and offender behavior.
Explain why a mobile device is likely associated with the offender based on evidence rather than generic assumptions where possible.
Explain why the selected area and time are reasonably connected to the offense and why broader coverage is necessary.
8. Particularity
Particularity is the requirement that a warrant meaningfully describe the place to be searched and the persons or things to be seized. Reverse digital searches are difficult because the identity of the ultimate target may be unknown when the warrant is issued.
Particularity Variables
| Variable | Narrowing Question | Common Risk |
|---|---|---|
| Geographic boundary | Is the area no larger than reasonably necessary to capture the relevant event? | Including homes, businesses, roads, places of worship, or unrelated locations without sufficient justification |
| Time window | Is the duration tied closely to the known timing of the offense and escape? | Searching hours or days of unrelated movement |
| Data type | What exact location fields or records are being requested? | Requesting all available account information before investigative narrowing |
| Movement outside the geofence | Why is information beyond the original boundary necessary? | Expanding from a scene-specific search to broader movement histories |
| De-anonymization | What objective criteria control which users are identified? | Giving investigators unbounded discretion to select users |
| Narrowing steps | Are later stages constrained by judicially approved criteria? | Leaving key scope decisions solely to investigators after issuance |
9. Minimization and Non-Suspect Data
Because reverse searches can initially encounter records associated with innocent users, agencies should consider minimization procedures addressing what happens to data that is no longer relevant.
Limit who may view the initial return and who may authorize further analysis or de-anonymization.
Restrict use of non-responsive or excluded records to the purpose authorized by the warrant and applicable law.
Define when irrelevant records should be deleted, segregated, or otherwise removed from ordinary investigative access.
Minimization does not substitute for probable cause or particularity. It is an additional safeguard that can reduce harm from a search that necessarily exposes some non-target information.
10. Technical and Investigative Risks
Digital coordinates are estimates. Precision depends on sensors, environment, software, network conditions, and provider methods.
A location record identifies a device or account event; it does not automatically prove who physically carried the device.
A digital location estimate may place a device inside a geofence even when the person was outside the intended physical location.
Employees, residents, customers, commuters, worshipers, delivery drivers, and bystanders may be captured.
Investigators may overinterpret location data as proof of conduct rather than one piece of circumstantial evidence.
Technical capabilities can change faster than warrant templates, policies, and training materials.
11. Investigative Alternatives
Reverse-location process should not become a substitute for conventional investigation. Depending on the case, other techniques may be more targeted, more reliable, or legally simpler.
If investigators identify a suspect or device, targeted location process may avoid searching unrelated users.
Vehicle detections may help identify a suspect vehicle or reconstruct travel where coverage exists.
Commercial video, municipal cameras, doorbells, and officer recordings may identify people, vehicles, or routes.
Known phone numbers, accounts, IP addresses, cloud records, and communications may support targeted legal process.
Interviews, fingerprints, DNA, physical evidence, receipts, and conventional canvassing remain important.
Once a device is known, carrier-based location records may be available subject to appropriate legal process.
12. Governance Framework
Reverse digital searches should have a governance pathway distinct from routine subpoenas or ordinary record requests. The technique implicates complex technology, constitutional law, non-suspect data, and rapidly changing provider practices.
Require supervisory and legal review before seeking reverse-location process.
Confirm what the provider can actually produce before relying on an old affidavit or warrant template.
Maintain centrally approved language and retire outdated forms after major court or provider changes.
Coordinate with prosecutors concerning probable cause, particularity, minimization, and disclosure.
Define access, retention, segregation, and deletion rules for non-suspect data.
Track who sought the warrant, scope, returns, narrowing decisions, de-anonymization, and final disposition of irrelevant data.
Require investigators and reviewers to understand how the location data is generated and its limitations.
Monitor Chatrie proceedings on remand, circuit law, state constitutions, statutes, and provider changes.
Where lawful and operationally appropriate, agencies should be prepared to explain policy safeguards governing reverse searches.
13. Geofence / Reverse-Location Affidavit Checklist
This is not a model warrant. It is a checklist of subjects that investigators, prosecutors, and reviewing counsel should consider when a reverse-location technique is legally and technically available.
| Affidavit Element | What the Affidavit Should Explain |
|---|---|
| Offense | The crime under investigation and facts establishing probable cause that the offense occurred. |
| Known timeline | How investigators determined the relevant start and end times. |
| Geographic area | Exact boundary, map, dimensions, and factual reason for choosing it. |
| Sensitive locations | Whether the geofence includes homes, schools, churches, medical facilities, government buildings, or other sensitive places. |
| Device nexus | Facts supporting the inference that responsive location data is likely to identify evidence or the offender. |
| Provider technology | How the provider generates, stores, and searches the particular location data. |
| Precision / limitations | Known accuracy limitations and why the search area accounts for them without becoming unnecessarily broad. |
| Stage one | Exactly what anonymized or pseudonymous information will be returned initially. |
| Narrowing criteria | Objective, judicially authorized criteria governing exclusion or continued scrutiny of devices. |
| Expanded location data | Why any movement information beyond the original geofence or time window is necessary. |
| Identity disclosure | What must occur before subscriber or account identity is requested. |
| Minimization | How non-responsive records will be restricted, segregated, returned, or deleted where appropriate. |
| Retention | How responsive evidence and irrelevant data will be preserved or disposed of. |
| Audit trail | How investigative decisions during narrowing and de-anonymization will be documented. |
14. Questions Every Agency Should Answer
15. The Future of Reverse Digital Searches
Google's architecture change dramatically reduced the practical relevance of the exact Location History process litigated in Chatrie. It did not eliminate the broader concept of reverse digital investigation.
Apps, platforms, connected devices, vehicles, and commercial services can generate other forms of location information.
Some investigations seek users associated with specified search terms rather than a known suspect account.
Networked vehicle databases can identify vehicles present near a place and time even when the plate is not initially known.
Connected cameras, access systems, Wi-Fi logs, and IoT infrastructure may support event-first investigative searching.
AI can make reverse searching more powerful by correlating large datasets and identifying candidate entities or patterns.
Courts will continue addressing when large-scale database searching becomes a Fourth Amendment search and what limits valid warrants require.
16. Key Terms
17. Related ShieldPST.ai Resources
Full Shield analysis of the Supreme Court's landmark geofence-warrant decision.
Read case analysis →The foundational Supreme Court decision on historical CSLI and digital location privacy.
Read case analysis →GPS tracking, physical trespass, and the modern constitutional debate over aggregated movement data.
Read case analysis →See how location tracking developed from beepers and GPS to CSLI and reverse-location searches.
Open timeline →Preservation, metadata, provider records, discovery, and evidentiary integrity.
Open resource →Return to the Shield Technology Reference Library.
Browse explainers →18. Selected Primary Sources
Controlling Supreme Court decision holding that acquisition of Chatrie's protected cell-phone location data was a Fourth Amendment search and remanding warrant-validity questions.
Read the opinion
Briefs, filings, procedural history, oral argument materials, and case documents.
Open docket
Primary-source explanation of Google's Location History system, geofence-warrant response process, constitutional concerns, and the 2025 change to on-device storage.
Read Google's brief
The divided en banc decision preceding Supreme Court review.
Read Fourth Circuit decision
Argument addressing reasonable expectations of privacy, reverse searching, probable cause, particularity, and the multi-step geofence procedure.
Read transcript
19. Key Takeaways
- A geofence warrant is a reverse-location search designed to identify unknown devices or users based on presence within a defined place and time.
- In 2026, the Supreme Court held in Chatrie that police conducted a Fourth Amendment search when they acquired Chatrie's Google Location History data.
- The Court did not decide whether the Chatrie warrant satisfied probable cause or particularity; those questions were remanded.
- Chatrie rejected the argument that short-duration location data is categorically outside Fourth Amendment protection.
- Google changed Location History storage in July 2025 and represented that it can no longer respond to the historical geofence process used in Chatrie.
- Provider architecture must therefore be verified before investigators rely on old warrant templates or training materials.
- Reverse searches create special probable-cause and particularity problems because investigators initially do not know whose data will be searched.
- Minimization, narrowing criteria, non-suspect-data handling, audit trails, and current prosecutor/counsel review are critical governance safeguards.
- The broader legal significance extends beyond Google: future reverse searches of large digital repositories will continue to test traditional Fourth Amendment doctrine.