The mechanics are unsettling precisely because they are so ordinary. Your phone, if location services are on, periodically estimates where it is using GPS, nearby Wi-Fi networks, and cell towers. For years, if you used Google's "Location History" feature, Google stored that trail in a vast database. Police learned they could ask Google not "where was this suspect" but "give us everyone who was in this rectangle during this hour." That database was reportedly known internally as Sensorvault.
How a Geofence Warrant Works
Google publicly described a three-step process it used to respond to these warrants, designed to limit how much it disclosed up front:
- Anonymous list. Google returns a de-identified list of devices that were within the geographic "fence" during the time window, each tagged with an anonymous device ID and location coordinates.
- Narrowing. Investigators review the list and select the device IDs that look relevant — for example, ones that moved in a pattern consistent with a suspect — and can request additional location context for those.
- Identification. For the narrowed set, police go back with the device IDs and Google provides the subscriber's name and account information.
The intent of the staging was privacy-protective. The problem is structural: step one sweeps in everyone. A geofence over a city block can capture commuters, residents, delivery drivers, and passersby who have nothing to do with the crime.
In a widely reported 2019 case, an Arizona man was arrested for murder largely because a geofence warrant placed his phone near the scene. He was later released — he had simply driven past. A tool that treats "was nearby" as "is a suspect" inverts the presumption of innocence at scale.
The Fourth Amendment Fight
Critics argue geofence warrants are the modern version of the "general warrants" the Fourth Amendment was written to forbid — they lack the particularized probable cause that is supposed to tie a search to a specific person. The legal backdrop is Carpenter v. United States (2018), in which the Supreme Court held that accessing historical cell-site location data is a Fourth Amendment search requiring a warrant, signaling that long-term location tracking gets constitutional protection.
Lower courts then split sharply over geofences specifically:
| Court / Case | Holding |
|---|---|
| 5th Circuit — United States v. Smith (2024) | Geofence warrants are unconstitutional general warrants by their nature. |
| 4th Circuit — United States v. Chatrie (en banc, 2024) | Obtaining the data was not a Fourth Amendment search under the third-party doctrine. |
Two federal appeals courts reaching opposite conclusions in the same year is exactly the kind of split that tends to invite eventual Supreme Court review. As of this writing the doctrine remains genuinely unsettled, and the answer may depend on where you live.
The Change That Mattered More Than the Courts
While the legal fight played out, Google made an engineering decision with outsized practical impact. In late 2023 it announced that Location History (rebranded "Timeline") would be stored on users' own devices by default rather than on Google's servers, with the change rolling out through 2024.
If the location trail lives encrypted on your phone instead of in a central database, there is no central database for a geofence warrant to query.
The effect is that the specific Sensorvault-style dragnet — "give us everyone who was here" — loses its target. Google cannot hand over data it no longer holds in aggregate. This does not eliminate location surveillance: police can still seek data from a specific person's device or account, carriers still hold cell-site records, and data brokers sell location feeds that law enforcement sometimes buys without any warrant at all. But the reverse-search dragnet against Google's central store is largely defanged.
Geofences Have Cousins
The same reverse-search logic powers related techniques you should know about:
- Keyword warrants — instead of a place, police specify a search query and ask which accounts searched for it during a window.
- Tower dumps — a request for every phone that connected to a particular cell tower in a time range, an older and cruder version of the same idea.
- Data-broker purchases — buying commercially available location data to sidestep the warrant requirement entirely, a practice that has drawn scrutiny from lawmakers and regulators.
What You Can Actually Do
You cannot litigate your own Fourth Amendment case from your phone settings, but you can reduce how much reverse-searchable data you generate:
- Review and disable location history features you do not need; audit per-app location permissions and prefer "while using" over "always."
- Turn off ad-personalization identifiers and use MAC address randomization on Wi-Fi.
- Minimize the number of apps that collect background location — they are a common feeder for the data-broker ecosystem.
- Understand that metadata, not message content, is what most of these tools harvest. End-to-end encryption protects what you say; it does not erase where your device has been.
Geofence warrants are a clean illustration of a broader truth: the most consequential surveillance often does not break encryption at all. It exploits the location and metadata exhaust that our devices emit by default. The defenses are partly legal, partly technical, and partly a matter of not generating the trail in the first place.