Google shares data for the first time on geofence warrants received from US authorities: 8.3K in 2019, 11K in 2020; federal law enforcement made up 4% of total
Zack Whittaker / TechCrunch : Tweets: @goyal_abhei and @zackwhittaker Tweets: Abhishek Goyal / @goyal_abhei : Geofence warrants in US help to identify people of interest who were in the near vicinity of a scene of crime. Via court order, Police ask Google to turn over details of who was in a area, at a certain point in time, to identify suspects. - TechCrunch https://techcrunch.com/... Zack Whittaker / @zackwhittaker : New: For the first time, Google has published the number of geofence warrants it's received from U.S. authorities. Google got 20,932 demands in 3 years, at times that's about one-quarter of all U.S. demands. https://techcrunch.com/...
Context & Ripple Effects
Google's Sensorvault location database became the engine of police investigations after the 2019 Sensorvault explainer detailed how agencies sweep up everyone near a crime scene, and by mid-2020 the growing volume of geofence requests was already drawing court challenges in California and Virginia. What was missing was any sense of scale: Google had never said how many of these warrants it actually received.
This disclosure fills that gap — 20,932 demands over three years, rising from 8,300 in 2019 to 11,000 in 2020 — and the federal share of just 4% shows the practice is overwhelmingly driven by state and local police, the very users whose nonviolent casework later surfaced in the five-state warrant review.
First-order effects
- State and local investigators — 96% of the demand side — now have a public benchmark confirming their reliance on geofence warrants is growing year over year, giving defense counsel and courts a concrete number to weigh against Fourth Amendment challenges already pending in CA and VA.
- Google's transparency team shifts from refusing to confirm volumes (as in the 2018 FBI gag-order case) to publishing annual counts, setting a precedent other platform holders of location data will be pressed to match.
Second-order effects
- Prosecutors leaning on geofence evidence in marquee cases — including the 45 criminal cases citing geolocation data from the Jan. 6 Capitol investigation — face heightened scrutiny now that the warrant volume is public and the technique is framed as mass collection rather than targeted investigation.
- Courts handling the CA and VA challenges gain usage data to rule on, and an adverse ruling would force Google and police to redesign how warrants are scoped rather than merely how many are filed.
Third-order effects
- If the growth curve held, the structural endpoint was always a product decision rather than a legal one — and the corpus shows it arrived: after changing how Maps stores location data, Google confirmed it would no longer respond to geofence warrants, collapsing the practice's main data source.
- The broader pattern points to location surveillance migrating from platform-held historical databases toward device-side or shorter-retention storage, leaving law enforcement to seek data from sources that still retain it — and regulators to weigh retention mandates against privacy defaults.
The trend: Law enforcement's dependence on platform-held location histories is colliding with platforms' ability to simply stop retaining the data, making retention architecture the real battleground over geofence surveillance.