A Texas sheriff searched 83,000 license plate cameras looking for one woman
EFF documented a Texas sheriff's office querying data from more than 83,000 automated license plate reader cameras, plus commercial location-tracking tools that can show a visit to a specific address. The technical capability is the story.
One Texas sheriff's office searched 83,000 license plate cameras to find one person.
EFF documented a Texas sheriff's office searching data from more than 83,000 automated license plate reader cameras in a single investigation. Separately, commercial location-tracking tools like Locate X can show that a phone visited a specific address, no warrant-scale surveillance operation required, just a subscription.
What ALPR networks actually let you query
Automated license plate readers log every plate that passes a camera, timestamped and geotagged, feeding a searchable database. 83,000 cameras queried in one case is a scale that has nothing to do with the specific investigation and everything to do with how large these networks have become and how broadly a single query can sweep across them. The technology was built for traffic and stolen-vehicle enforcement. Nothing about the architecture limits it to that.
The access control question
The actual engineering and policy question EFF's piece raises is not whether ALPR networks exist, they clearly do and are widely deployed, but who can query them, under what authorization, and what gets logged about the query itself. Commercial location brokers add a second layer: data collected for one purpose, like ad targeting or fleet tracking, becoming queryable for a completely different one, with far less oversight than a dedicated law enforcement database.
Why a build studio cares
Any system that logs sensitive location or identity data inherits this exact problem: technically capable of broad queries, and only as safe as its access controls and audit logging actually are, not as safe as its stated purpose implies. It is the same design question we ask on any client build that touches location, identity, or query logs: who can search this, and would that search itself be visible after the fact.
Next step: read EFF's full piece on the surveillance tools involved. If a build you're running logs sensitive location or identity data and you want a second look at who can query it, write to us at hello@gattyworks.com.