# Five Hundred Ninety-Two Million **Deck:** The Supreme Court of the United States will decide within the next thirty days whether the Fourth Amendment permits the government to search the location records of 592 million people to find one suspect. Chatrie v. United States, argued April 27, asks whether a geofence warrant — an order directing a technology company to identify every device within a geographic area during a specified time window — violates the Constitution's prohibition on unreasonable searches. The Fourth Circuit and Fifth Circuit have reached opposite conclusions. The Fourth Circuit, sitting en banc, split 7-7 on whether a search even occurred — issuing a one-sentence per curiam decision accompanied by 126 pages of concurring and dissenting opinions, the deepest judicial disagreement without resolution in a digital privacy case. The Fifth Circuit, in United States v. Smith, ruled that geofence warrants are "modern-day general warrants" that are "categorically prohibited by the Fourth Amendment" — invoking the writs of assistance used by British colonial authorities that were the direct provocation for the Fourth Amendment's ratification. The case arises from a credit union robbery in Midlothian, Virginia. Law enforcement obtained a geofence warrant directing Google to search its Sensorvault database — containing the location history of approximately 592 million individual accounts — for every device within 150 meters of the bank during a one-hour window. The search returned 19 accounts, which Google narrowed to 9, then provided identifying information for 3 — including Okello Chatrie's. The 150-meter radius encompassed not only the credit union but an adjacent church, its parking lot, nearby hotels, and residential homes. The warrant captured location data from people attending church services, staying at hotels, and living in the neighborhood. The structural question is not whether geofence warrants are effective investigative tools. They are. The question is whether the Fourth Amendment permits the government to search everyone in order to find someone. Traditional warrants identify a suspect and search for evidence. Geofence warrants identify a location and search for suspects. That inversion — from searching a person's data to searching everyone's data — is the constitutional question the Court will resolve. At oral argument, the justices appeared divided. The implications extend beyond location data. Amicus briefs from the ACLU, EFF, Brennan Center, and CDT warn that the constitutional standard set in Chatrie will govern "reverse warrants" for keyword searches, AI chatbot conversations, video viewing histories, and cloud-stored documents. If the Court holds that voluntarily sharing location data with Google eliminates Fourth Amendment protection, the same logic applies to every query you type into an AI assistant, every document you store in the cloud, and every search you run on any platform. The most consequential digital privacy ruling since Carpenter v. United States in 2018 will arrive within thirty days. The architecture that does not store the data the warrant seeks is the architecture that cannot be searched — regardless of what the Court decides. **By:** URnetwork editorial **Dateline:** San Francisco — May 27, 2026 **Category:** News / Analysis --- ## Five hundred ninety-two million The number is the search. In 2019, law enforcement investigating a credit union robbery in Midlothian, Virginia obtained a geofence warrant directing Google to search its entire Sensorvault database — approximately 592 million individual accounts with Location History enabled — to identify every device that was within 150 meters of the bank during a one-hour window around the robbery. The search returned 19 accounts. Google narrowed those to 9. Identifying information was provided for 3 — including Okello Chatrie, who was arrested and convicted. The ratio is the constitutional question. 592 million accounts searched to identify one suspect. The other 591,999,999 were searched without individual suspicion, without probable cause, and without any prior indication they were connected to the crime. They were searched because they existed in a database and the database was searchable. The Supreme Court heard oral arguments on April 27, 2026. A decision is expected before the term ends in late June — within the next thirty days. ## The reverse warrant Traditional warrants work in one direction. Law enforcement identifies a suspect, establishes probable cause, and obtains a warrant to search that suspect's property, records, or data. The warrant names the person. The search seeks the evidence. Geofence warrants invert this. Law enforcement identifies a location and a time window. The warrant directs a technology company to search every user's data to determine who was present. The warrant does not name a person. The search seeks the suspect. The Fifth Circuit, in United States v. Smith, named this inversion explicitly: geofence warrants are "the exact sort of general, exploratory rummaging that the Fourth Amendment was designed to prevent." The court drew a direct line from geofence warrants to the writs of assistance — open-ended search authorizations used by British colonial authorities that allowed officers to search any location without specific cause. The writs of assistance were the direct provocation for the Fourth Amendment. The Fourth Circuit, confronted with the same question in Chatrie's case, could not agree. The full court split 7-7, producing 126 pages of opinions without a majority position on any major issue. The one-sentence per curiam decision — affirming the conviction without resolving the constitutional question — was the most extensive judicial disagreement without resolution in the history of digital privacy law. The Supreme Court granted certiorari to resolve the split. ## The 150-meter radius The warrant in Chatrie specified a 150-meter radius around the credit union and a one-hour time window. Within that radius: the credit union, an adjacent church, the church parking lot, nearby hotels, and residential properties. The people whose location data was captured include: church attendees at a service, hotel guests, residents of nearby homes, shoppers at adjacent businesses, and anyone who walked or drove through the area during the specified hour. None of these people were suspects. None had any connection to the robbery. Their location data was searched because they existed within a circle on a map. This is the particularity problem. The Fourth Amendment requires that warrants "particularly describe the place to be searched, and the persons or things to be seized." A geofence warrant describes a place — but it does not describe a person. It seizes data from everyone in the area and then identifies persons of interest from the results. The identification comes after the search, not before it. ## What the justices said At oral argument on April 27, the Court appeared divided along familiar lines with unexpected crosscurrents. Chief Justice Roberts asked why users could not simply disable location tracking — framing the issue as voluntary disclosure. Justice Alito emphasized the third-party doctrine, suggesting that sharing location data with Google constitutes a voluntary transfer that eliminates the expectation of privacy. Justice Sotomayor challenged the voluntariness argument, questioning whether users understand the privacy controls they are agreeing to when they set up their phones. Justice Kagan asked why the Fourth Amendment would protect "patterns of life" but not a single visit to a political rally or an abortion clinic. Justice Gorsuch posed the question that extends the case beyond location data: "If we rule that voluntary exposure to Google allows unfettered government access to location history, would that ruling apply equally to email?" Petitioner's counsel confirmed it would extend to cloud-stored data. Justice Kavanaugh praised the detective's three-step narrowing process — from 19 accounts to 9 to 3 — as "good police work," suggesting a possible middle path where the warrant's methodology mitigates its breadth. The oral argument signals suggest the Court is unlikely to adopt either extreme position — neither a categorical ban on geofence warrants nor blanket permission. The most likely outcome is a fact-specific ruling establishing constitutional guardrails for time, space, and particularity. But even a narrow ruling will set the precedent that governs every reverse-search warrant for a generation. ## Beyond location The amicus briefs filed in Chatrie number more than 29. The ACLU, Electronic Frontier Foundation, Brennan Center for Justice, Center for Democracy and Technology, Google, Microsoft, and X Corp. all filed. So did the Cato Institute and the National Association of Criminal Defense Lawyers. The briefs warn that the constitutional standard set in Chatrie will not be limited to location data. The same "reverse warrant" logic applies to: Keyword warrants — orders directing a search engine to identify everyone who searched for a specific term during a specific period. Google has received keyword warrants for search terms related to arsons, bomb threats, and other crimes. AI chatbot histories — orders directing an AI company to identify every user who asked a specific question or discussed a specific topic. Every conversation with Claude, ChatGPT, Gemini, or any other AI assistant is stored server-side by default. Cloud document searches — orders directing a cloud storage provider to identify every user whose documents contain specific content. Every file in Google Drive, iCloud, OneDrive, or Dropbox is potentially searchable under a reverse warrant theory. Video viewing histories — orders directing a streaming platform to identify everyone who watched a specific video. This implicates the Video Privacy Protection Act but a constitutional holding in Chatrie could override statutory protections. The structural point: if the Court holds that sharing data with a technology company eliminates Fourth Amendment protection, every digital interaction that passes through a third-party server is constitutionally unprotected. The reverse warrant becomes the default investigative tool for the digital age. ## Google changed its architecture In December 2023, Google announced it would move Location History data from its centralized Sensorvault servers to individual users' devices. By mid-2025, the transition was complete. Google no longer possesses the aggregated location database that made the Chatrie geofence warrant possible. This is architecturally significant. Google solved the problem that Chatrie presents — not through law, not through policy, but through design. By moving the data to the user's device, Google eliminated the centralized database the government could search. The architecture is the defense. But the constitutional question survives the architectural change. Law enforcement has already turned to telecommunications carriers — AT&T, T-Mobile, Verizon — for tower-based location data. Forbes reported in early 2024 that law enforcement shifted to telecoms after Google's policy change. These carriers operate with less privacy-protective architecture than Google's on-device model. The Chatrie ruling will set the constitutional floor for all reverse-location searches, not just Google-specific ones. And the reverse-warrant principle extends to every database, on every platform, for every type of data. Google moved the location data to the device. The AI conversation histories, keyword searches, and cloud documents remain server-side. ## The architecture that cannot be searched The constitutional ruling in Chatrie — whatever it is — will set the floor. It will define the minimum protection the Fourth Amendment provides against reverse warrants. The architecture that provides protection above the floor is the architecture this publication has been documenting. End-to-end encrypted messaging where the server holds ciphertext and cannot respond to a content-based reverse warrant because the content is not accessible. Signal's protocol. Matrix's encryption. Briar's peer-to-peer transport. Local-inference AI where the query never leaves the user's device. The reverse warrant for "everyone who asked about X" cannot reach a conversation that never reached a server. On-device data storage where the location history, search history, and document library reside on hardware the user controls. Google's December 2023 architectural change — moving Location History to the device — is the model. The data that is not centralized cannot be searched with a single warrant. Self-hosted services where the user controls the server. A reverse warrant served on the user's own infrastructure is a conventional search warrant requiring individual probable cause — not a dragnet. Peer-to-peer overlays where the transport does not traverse an intermediary that stores data. URnetwork's overlay does not accumulate location data, conversation histories, or search records because the architecture does not include a centralized data store for any of those categories. The Chatrie decision will tell us what the Constitution requires. The architecture tells us what is possible regardless. 592 million accounts were searchable because 592 million accounts existed in a single database. The architecture where that database does not exist is the architecture where the warrant finds nothing — not because the Court prohibited the search, but because the data was never there. --- *URnetwork is a peer-to-peer overlay for censorship-resistant transport. The URnetwork overlay does not accumulate centralized location data, conversation histories, or search records. A reverse warrant served on the overlay finds nothing because the data does not exist at the intermediary layer.* *https://ur.io* --- ## References - [SCOTUSblog: Chatrie v. United States case page](https://www.scotusblog.com/cases/case-files/chatrie-v-united-states/) - [TechCrunch: SCOTUS appears split on geofence warrants](https://techcrunch.com/2026/04/28/scotus-chatrie-geofence-search-warrant-ruling-arguments/) - [Brookings: Supreme Court weighs constitutionality of geofence warrants](https://www.brookings.edu/articles/supreme-court-weighs-constitutionality-of-geofence-warrants/) - [Brennan Center: Chatrie v. United States](https://www.brennancenter.org/our-work/research-reports/okello-chatrie-v-united-states-america) - [CDT: A Fork in the Road for the Fourth Amendment](https://cdt.org/insights/a-fork-in-the-road-for-the-fourth-amendment-how-the-chatrie-case-could-shape-location-surveillance-and-reverse-warrants-for-the-digital-age/) - [IBTimes: Supreme Court ruling could expose AI chats to police](https://www.ibtimes.com/supreme-court-geofence-ruling-could-expose-ai-chats-keyword-searches-police-3803251) - [Supreme Court: Question presented (PDF)](https://www.supremecourt.gov/qp/25-00112qp.pdf) - [Harvard Law Review: Much Ado About Geofence Warrants](https://harvardlawreview.org/blog/2025/02/much-ado-about-geofence-warrants/) --- ## Publication notes (for the supervisor) This article centers on Candidate 1 from the 20-candidate pool. Chatrie v. US has never been covered in any prior edition and is the most consequential pending digital privacy case. The decision is expected within 30 days. The 592-million ratio is the most powerful single number available. The extension to AI chatbots, keyword searches, and cloud documents makes this relevant to every reader. The "reverse warrant" framing is analytically distinctive. Google's architectural change (moving data to device) provides the user-side response that connects to the publication's thesis. Full research and iteration logs in blog-research/2026-05-27-03/.