Chatrie v. United States: What the Geofence Warrant Decision Actually Held

Correction, October 7, 2026: This article now incorporates an overlapping pre-decision guide and reflects the Court’s June 29 ruling. The earlier coverage forecast an outcome and described the technique too broadly. Chatrie v. United States grew out of a reverse-location investigation. Instead of starting with a known suspect and requesting that person’s records, police asked Google for devices recorded near a Virginia credit-union robbery and used the results to identify possible suspects. That direction matters. A reverse search can expose records belonging to people who were near an event but were not previously under suspicion. It also makes the technical steps between a broad first return and a named person central to any legal analysis. How the identification process worked Chatrie’s opening brief describes a staged demand for Google Location History: Google searched for devices in a defined area and time and returned anonymized records. Investigators selected devices and requested a wider time window for them. Google supplied subscriber information for the narrowed group. The official docket records the later Supreme Court proceedings and the return of the case to the Fourth Circuit. The sequence is useful because appellate decisions often answer one issue while leaving the rest of a case open. What the opinion resolved The opinion held that obtaining Chatrie’s Google Location History was a Fourth Amendment search. The Court rejected the government’s attempt to treat the short collection window and Google’s custody as reasons that no search occurred. The Court did not decide that every geofence warrant is invalid. It vacated the judgment and left the Fourth Circuit to address the remaining analysis, including whether the warrant’s stages satisfied probable-cause and particularity requirements. Describing the outcome as either approval or a categorical ban would therefore add a conclusion the Court did not reach. Why Google’s storage change matters The investigation used a centrally available Location History system. Google’s current support documentation describes a different design: Timeline is off by default, saves precise Timeline data on eligible devices when enabled, and offers an optional encrypted backup. That change affects what Google can retrieve from the former system, but it does not make every location trail disappear. Google warns that deleting Timeline does not necessarily remove information saved through other settings, such as Web & App Activity. Apps, carriers, device platforms, vehicles, and data brokers may also hold records created through different systems. The storage architecture should therefore be part of the reporting. A statement that a company “has location data” is incomplete without identifying the product, the setting, the time period, where the records reside, and what the recipient of a legal demand can actually access. A checklist for reading the next reverse-search case Before comparing another dispute with Chatrie, establish five facts: Starting point: Did investigators begin with a named person, or search a pool of unknown devices or accounts? Record source: Was the information created by GPS, Wi-Fi, cell towers, an app, a vehicle, or a commercial dataset? Custody: Did the provider hold the records centrally, or did investigators obtain them from a device or another party? Narrowing: Who chose which anonymous records advanced to a later stage, and under what limits? Identification: At what point did subscriber information or a longer movement history enter the process? Those questions keep the analysis tied to the actual system. They also prevent a case about one discontinued Google workflow from becoming a shortcut for claims about every form of location surveillance.