Tech
Texas city demands $2M for public records on Flock usage
Publication: Ars Technica - All content
Author: Ashley Belanger
Source published: 05/10/2026, 20:31:12 UTC
Briefing created: 20/10/2026, 17:34:57 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 06/10/2026, 12:43:24 UTC.
Briefings
Texas city officials in North Richland Hills demanded $2.3 million to access Flock AI surveillance data, claiming the search would require 14 years of labor at $15/hour. This fee was proposed amid bipartisan backlash against Flock's use by police departments, with the Texas Tribune reporting the incident on October 5, 2026. The request highlights a conflict between public transparency demands and the high costs of retrieving AI-generated surveillance logs.
Key points
- North Richland Hills officials charged $2.3 million to retrieve Flock AI surveillance data, citing 14 years of labor at $15 per hour to process terabytes of error and misuse communications.
- The Texas Tribune reported this fee request on October 5, 2026, amidst growing bipartisan opposition to Flock's deployment by law enforcement agencies.
Context
This incident occurred in North Richland Hills, Texas, where city officials sought to access Flock AI surveillance data. The request highlights a tension between public transparency demands and the high costs of retrieving AI-generated surveillance logs, occurring amid broader bipartisan backlash against Flock's use by police departments.
Limitations
Evidence is limited to a single reported incident from October 2026 involving one city and one specific fee request. The article does not provide details on the total number of cities requesting fees, the specific types of Flock data accessed, or the broader scope of the bipartisan backlash beyond the Texas Tribune report.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 20/10/2026, 17:34:57 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeifcmrvw7i4ays43yvsmh6nhbdbkx7e4f342nlfqltqmu7vaspgdl4