Digital Policy

Supreme Court Reviews Use of Geofence Warrants in Chatrie Case

The Supreme Court recently heard oral argument in Chatrie v. United States, a pivotal case addressing the legality of geofence warrants under the Fourth Amendment. These warrants allow law enforcement to demand location data from all mobile devices within a specified geographic area and time frame, potentially implicating hundreds of innocent individuals in a single sweep.

What Are Geofence Warrants?

Geofence warrants are a form of “reverse” digital warrant. Instead of identifying a suspect first, law enforcement requests user data en masse from companies like Google to identify potential suspects after an event. Specifically, police ask Google to provide information on every device that was in a designated area at the time a crime occurred, a process which can capture data on dozens or even hundreds of people.

Google’s Location History feature, enabled by roughly a third of its users worldwide (about 592 million people), stores detailed movement records linked to individual accounts. When served with a geofence warrant, Google examines all accounts with location history enabled to identify devices near the crime scene. Then police narrow down individuals for further investigation, often requesting subscriber data to reveal identities.

In the case at hand, involving a bank robbery, the government’s geofence warrant covered not only the bank but also adjacent locations such as a church and its parking lot. The data collected extended beyond the immediate crime scene, including individuals in hotels, hospitals, and private homes, raising concerns about overbroad surveillance.

Privacy Concerns and Legal Arguments

Michael Price, litigation director for the Fourth Amendment Center at the National Association of Criminal Defense Lawyers, highlighted that geofence warrants function as digital dragnet searches with no initial suspect and a broad sweep of data. He noted that this challenges constitutional protections by allowing the government to sift through private location data without specific probable cause.

Price emphasized that the data stored in Google Location History should be considered private and protected under the Fourth Amendment. He also warned about potential extensions of this practice to other types of cloud-stored personal data, such as emails or messages, if courts uphold geofence warrants without restrictions.

Impact of Google’s Data Policy Changes

In a significant development, Google recently stopped storing Location History data on its servers and now keeps it exclusively on users’ devices, making it technically impossible for Google to comply with geofence warrants as previously requested. This policy shift has practical and legal implications, limiting the government’s ability to conduct such mass data requests through Google.

However, Price noted that the change does not fully moot the legal issues involved or pending cases like Chatrie. Law enforcement has turned to other methods, such as “area dumps,” issuing broad requests to cell service providers using alternative location data, which remains a concern for digital privacy advocates.

Why it matters

The Supreme Court’s decision in Chatrie v. United States could establish crucial limits on digital surveillance practices and clarify the scope of constitutional protections in the digital age. As law enforcement increasingly uses geolocation data to identify suspects, the ruling will affect privacy rights for millions of individuals whose location information is stored by third-party companies.

Sources

This article is based on reporting and publicly available information from the following source:

Read more Digital Policy stories on Goka World News.

Giorgio Kajaia
About the author

Giorgio Kajaia

Giorgio Kajaia writes and publishes news coverage for Goka World News, focusing on technology, business, science, health, space, and major global developments. His work is centered on clear reporting, concise context, and reader-friendly explanations based on publicly available information.

View all posts by Giorgio Kajaia