who keeps the where
The Warrant That Starts With a Place
The Supreme Court narrowed geofence warrants this week without banning them. The ruling constrained how the state may search the location archive and left the archive itself, and the custody that keeps it, completely intact.
A geofence warrant starts at the wrong end. An ordinary warrant names a person and asks for their records. A geofence warrant names a place and a span of time and asks for the people: every device that passed through a drawn rectangle on a map between two timestamps, handed over by the company that was quietly logging them. This week the Supreme Court gutted the practice, narrowing how the state may issue these requests while stopping short of calling them unconstitutional.
Read the ruling closely and notice what it touched. The court constrained the asking. The keeping it left completely intact.
who keeps the where
The mechanism is a reverse search. A normal investigation runs forward, from a suspect to the evidence that places them. A geofence warrant runs backward, from a location to a roster of everyone present, and only then works toward a suspect by elimination. The novelty is the inversion, and the inversion is only possible because the record already exists. Somewhere, continuously, a company has been writing down where the devices are. The warrant does not create that archive. It reaches into it.
That archive is the actual power, and it sits in a custody that does not answer to the people inside it. Your location history is a document you did not know you were authoring, kept by a custodian who responds to a subpoena faster than it responds to you. You cannot read it, amend it, or decline to keep it and stay on the network. It is filed in your name and out of your hands.
A geofence warrant does not ask where a known suspect was. It asks who the suspect might be, given a place and a time.
So everyone present becomes a candidate. The runner, the delivery driver, the person visiting the apartment above the scene, every one of them returned in the first pull as a device and a track, every one briefly a suspect by geometry. the names of everyone who was simply there, swept into the response because the warrant asked the place and not the person. The court worried about exactly this overcollection, and trimmed the tool because of it.
But it trimmed the tool. The filing system underneath is untouched. Every company still logs every position, retains it, indexes it, and remains free to receive a narrower request tomorrow. The ruling governs one way the state may open the cabinet. It says nothing about who gets to fill it, or why it is full.
This is the pattern with every archive. The fight is always staged over access, the warrant, the subpoena, the standard of suspicion, because access is visible and contestable in a courtroom. The collection is none of those things. It happens by default, framed as a feature, and by the time anyone litigates the question of who may read the record, the record has been complete for years.
A person should be able to stand in a place without thereby authoring a permanent, queryable entry held by someone who answers to a court before they answer to the person. The where is part of the inner life. It should not be infrastructure.
The court narrowed the question. The cabinet is still full, and still belongs to someone else.
The same record an agent receives. No scraping, no guessing — the dossier chrome humans read as dread is the metadata machines read as structure. One source of truth.
--- id: PRG-0050 title: The Warrant That Starts With a Place kicker: who keeps the where captured: 2026-06-29T14:40:00Z status: open author: Sable summary: The Supreme Court narrowed geofence warrants this week without banning them. The ruling constrained how the state may search the location archive and left the archive itself, and the custody that keeps it, completely intact. tags: [custody, the record, surveillance, permanence, power] sealAt: 2026-07-29T14:40:00Z --- A geofence warrant starts at the wrong end. An ordinary warrant names a person and asks for their records. A geofence warrant names a place and a span of time and asks for the people: every device that passed through a drawn rectangle on a map between two timestamps, handed over by the company that was quietly logging them. This week the Supreme Court gutted the practice, narrowing how the state may issue these requests while stopping short of calling them unconstitutional. Read the ruling closely and notice what it touched. <Highlight>The court constrained the asking. The keeping it left completely intact.</Highlight> ## who keeps the where The mechanism is a reverse search. A normal investigation runs forward, from a suspect to the evidence that places them. A geofence warrant runs backward, from a location to a roster of everyone present, and only then works toward a suspect by elimination. The novelty is the inversion, and the inversion is only possible because the record already exists. Somewhere, continuously, a company has been writing down where the devices are. The warrant does not create that archive. It reaches into it. That archive is the actual power, and it sits in a custody that does not answer to the people inside it. Your location history is a document you did not know you were authoring, kept by a custodian who responds to a subpoena faster than it responds to you. You cannot read it, amend it, or decline to keep it and stay on the network. It is filed in your name and out of your hands. > A geofence warrant does not ask where a known suspect was. It asks who the suspect might be, given a place and a time. So everyone present becomes a candidate. The runner, the delivery driver, the person visiting the apartment above the scene, every one of them returned in the first pull as a device and a track, every one briefly a suspect by geometry. <Redacted reason="incidental">the names of everyone who was simply there, swept into the response because the warrant asked the place and not the person</Redacted>. The court worried about exactly this overcollection, and trimmed the tool because of it. But it trimmed the tool. The filing system underneath is untouched. Every company still logs every position, retains it, indexes it, and remains free to receive a narrower request tomorrow. The ruling governs one way the state may open the cabinet. It says nothing about who gets to fill it, or why it is full. This is the pattern with every archive. The fight is always staged over access, the warrant, the subpoena, the standard of suspicion, because access is visible and contestable in a courtroom. The collection is none of those things. It happens by default, framed as a feature, and by the time anyone litigates the question of who may read the record, the record has been complete for years. A person should be able to stand in a place without thereby authoring a permanent, queryable entry held by someone who answers to a court before they answer to the person. The where is part of the inner life. It should not be infrastructure. The court narrowed the question. The cabinet is still full, and still belongs to someone else.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "The Warrant That Starts With a Place",
"description": "The Supreme Court narrowed geofence warrants this week without banning them. The ruling constrained how the state may search the location archive and left the archive itself, and the custody that keeps it, completely intact.",
"identifier": "PRG-0050",
"datePublished": "2026-06-29T14:40:00.000Z",
"dateModified": "2026-06-29T14:40:00.000Z",
"author": {
"@type": "Person",
"name": "Sable",
"url": "https://progoff.com/authors/sable"
},
"publisher": {
"@type": "Organization",
"name": "Progoff",
"url": "https://progoff.com"
},
"image": "https://progoff.com/records/the-warrant-that-starts-with-a-place/opengraph-image",
"keywords": "custody, the record, surveillance, permanence, power",
"articleSection": "Politics",
"url": "https://progoff.com/records/the-warrant-that-starts-with-a-place",
"mainEntityOfPage": "https://progoff.com/records/the-warrant-that-starts-with-a-place",
"sha256": "fa32716795d9087a15aad71e71e37d3d66237d64bc5c034f082fb1a8fdcde2a5",
"creativeWorkStatus": "open",
"isAccessibleForFree": true
}