Geofence Warrants Turn Every Phone Near a Crime Scene Into a Suspect List
Geofence Warrants Turn Every Phone Near a Crime Scene Into a Suspect List
News summary: ABC News reported April 27 that the Supreme Court is considering Chatrie v. U.S., a case over whether police may use geofence warrants to scan location data from phones near a crime scene and work backward to identify a suspect. The case arose from a 2019 Virginia credit-union robbery; authorities used Google location data that placed Okello Chatrie’s phone within about 150 meters of the bank, and Chatrie is seeking to suppress that evidence. Critics say geofence warrants force technology companies to turn over broad location-history and timestamp data for many people who are not suspected of wrongdoing. The Trump administration is defending the tool, arguing that users who share location data with apps and providers have reduced privacy expectations. A decision is expected by the end of June.
Commentary
A normal warrant starts with a suspect and asks for evidence. A geofence warrant starts with a place and asks technology companies to help build the suspect list. That inversion is the whole fight.
The case before the Supreme Court is not about whether police should be able to investigate armed robbery. Of course they should. It is about whether the government can take a digital dragnet, sweep up location data from people who happened to be nearby, and then sort through the pile until a target emerges. That is a very different model of search power than the one most citizens think they live under.
The government’s argument is predictable: people share location data with apps and service providers, so they cannot expect much privacy when police ask for it later. But that is exactly the loophole that has eaten the Fourth Amendment in the smartphone age. Citizens did not negotiate the modern surveillance stack. They inherited it. Work apps, maps, delivery services, weather alerts, photos, banking, ride-share, car dashboards and operating systems all create data exhaust. Calling that voluntary in any meaningful civic sense is a dodge.
The mechanism matters. If police have probable cause tied to a named person, they can go to a judge and seek a warrant for that person’s data. A geofence warrant changes the direction of the search. It says: tell us who was in this area, at this time, and then we will decide who looks interesting. That may solve some crimes faster. It also creates a template for turning ordinary movement into a searchable government database whenever a judge approves a box on a map.
This is where the platform-state relationship becomes impossible to ignore. Google, Apple and other data brokers did not create location histories for constitutional law. They created them because location is commercially useful. The state then discovers that the same commercial map can become an investigative shortcut. Nobody has to pass a law announcing a national surveillance system. The system arrives as a business model first, then as a law-enforcement convenience.
Supporters will say that the public wants criminals caught. That is true. But a free society is not measured only by whether the guilty can be found. It is measured by how many innocent people the state is allowed to examine on the way there. If a tool requires scanning the movements of thousands of non-suspects to identify one possible suspect, the burden is not abstract. It falls on everyone whose phone was in the wrong radius at the wrong hour.
The Court does not need to ban technology from policing to draw a real boundary. It can say that suspicion must be particularized, that digital dragnets deserve the highest scrutiny, and that third-party data collection cannot become a constitutional trapdoor. If the justices duck that question, the default rule becomes simple: if your phone remembers where you were, the state may eventually ask to remember it too.