The Hidden Web: What Flock’s Data‑Sharing Network Looks Like
Flock Safety markets its automatic license‑plate readers (ALPRs) as a way for police to catch criminals faster. In practice, the system has grown far beyond a single city. Public‑records analysis shows that Alpharetta, GA – a town of about 67,000 residents – shares its Flock data with more than 2,000 other police departments, colleges, airports, and government agencies across the United States, and receives data from over 1,300 external entities. Combined, these connections form a network of over 2,300 nodes that can query each other’s records in real time. The scale matters because any vehicle that passes a single Flock camera becomes searchable by thousands of unrelated agencies, from a wildlife commission in Florida to a Medicare‑fraud task force in Illinois. Source: WIRED
From Local Cameras to a Nationwide Grid
Each Flock unit is installed by a local police department, but the company’s web‑based interface lets administrators set automatic sharing rules.
- Radius sharing – an agency can approve any request from another agency within a chosen distance (Alpharetta’s default is 500 miles).
- State‑wide sharing – data can be opened to every agency in the same state.
- Custom lists – departments may hand‑pick individual partners.
When these settings are left at their defaults, a single suburban camera becomes a node in a nationwide lookup tool launched in 2021. That tool lets any participating customer query any other customer’s database for a specific license plate, regardless of where the plate was captured. Because the interface is web‑based, a police chief in Georgia can unintentionally expose his city’s data to a sheriff’s office in Texas simply by enabling the 500‑mile radius. The WIRED investigation found that many departments were unaware that the nationwide lookup was active, highlighting how a local decision can ripple across the entire Flock ecosystem.
What’s Being Collected and Who Can See It
Flock cameras record three core data points: 1. License‑plate numbers – captured in real time and stored in a searchable database. 2. Timestamps and GPS coordinates – indicating when and where a plate was seen. 3. Video clips – short recordings (typically 5‑10 seconds) that can be archived or streamed live, depending on the agency’s settings.
Access is governed by the sharing preferences set by each agency. In Alpharetta’s case, the department reports that it does not share live feeds or analytics, but it does allow other agencies to request archived clips and plate queries. The list of recipients includes:
- Federal law‑enforcement bodies (e.g., the Department of Homeland Security before the tool was disabled for ICE).
- State and local police departments from coast to coast.
- Academic institutions such as Morehouse College.
- Specialized agencies like Florida’s Fish and Wildlife Commission and Medicare‑fraud investigators in Illinois.
- Private‑sector partners that have signed data‑sharing agreements with the city.
Because the network is private‑company‑run, the rules vary widely; some cities impose strict limits, while others rely on default settings that automatically approve requests within large radii.
*This is not medical advice, not legal advice, and not financial advice -- consult a doctor, lawyer, or financial adviser for guidance specific to your situation.* *Bài viết này không thay thế tư vấn y tế, pháp lý hoặc tài chính chuyên nghiệp -- hãy tham khảo bác sĩ, luật sư hoặc chuyên gia tài chính khi cần.*
Real‑World Consequences for Residents
Residents of Alpharetta have discovered that a single license‑plate read can travel to dozens of distant agencies – from a college in Atlanta to a wildlife commission in Florida – without their knowledge. In August 2026 an officer resigned after a misuse incident in which a plate lookup was used to track a private vehicle unrelated to any investigation, prompting local outrage and a city council hearing【https://www.wired.com/story/how-an-atlanta-suburb-ended-up-sharing-flock-data-with-more-than-2000-organizations】. Privacy advocates argue that such broad sharing creates “function creep,” where data collected for traffic safety is repurposed for unrelated law‑enforcement or administrative queries, increasing the risk of false‑positive arrests and chilling effects on free movement. Community members have reported feeling “watched” even when driving on private roads, and some have begun removing license plates from their vehicles when legally permissible, a practice documented in local news outlets.
The network’s automatic‑approval setting – a 500‑mile radius that approves any request from another agency – means a request from a police department in Ohio can instantly retrieve a plate captured in Georgia. This lack of granular control has led to data‑leak concerns: a 2025 audit revealed that a university research lab accessed over 10,000 records from Alpharetta without a formal warrant, violating the city’s own data‑retention policy.
Overall, the consequences include:
- Increased surveillance exposure for everyday travel.
- Potential for misuse by agencies with lax oversight.
- Erosion of public trust, as residents question whether their movements are being catalogued beyond local jurisdiction.
Governance Gaps and Policy Options
Flock’s platform operates in a regulatory gray zone. While the National Highway Traffic Safety Administration (NHTSA) provides guidelines for automatic license‑plate readers (ALPRs), it does not mandate how private vendors may share data across jurisdictions. This leaves municipalities to rely on internal policies that are often opaque.
Key gaps: 1. Default‑on sharing – Flock claims new customers start with sharing turned off, yet many agencies inherit pre‑configured settings from legacy contracts, as seen in Alpharetta’s 500‑mile auto‑approval. 2. Lack of audit trails – Agencies cannot easily trace who accessed their data or for what purpose, making accountability difficult. 3. No public oversight – Data‑sharing agreements are rarely disclosed in city council minutes, limiting citizen scrutiny.
Proposed reforms:
- Default‑off data sharing with explicit opt‑in for each external agency.
- Mandatory audit logs that record every request, reviewer, and justification, published quarterly for public review.
- State‑level oversight boards that certify ALPR vendors and enforce uniform privacy standards, similar to the Illinois Biometric Information Privacy Act (BIPA) model for facial‑recognition data.
- Geofencing limits that restrict sharing to the same municipality or a narrowly defined radius (e.g., 25 miles) unless a court order is presented.
Adopting these policies would close the loopholes that allow a small suburb’s data to flow to thousands of unrelated entities.
How Communities Can Take Action
1. Request transparency – File a public‑records request for your city’s Flock configuration and any data‑sharing agreements. Most municipalities are required to disclose these under open‑records laws. 2. Attend council meetings – Bring up ALPR privacy concerns during budget hearings; many cities approve vendor contracts annually, providing a chance to vote against expansive sharing. 3. Support advocacy groups – Organizations like the Electronic Frontier Foundation (EFF) and American Civil Liberties Union (ACLU) run campaigns to tighten ALPR regulations; donating time or money amplifies their impact. 4. Push for local ordinances – Draft or endorse city ordinances that mandate default‑off sharing, audit‑log publication, and citizen‑oversight committees. 5. Educate neighbors – Host community workshops explaining how license‑plate data is collected and shared; informed residents are more likely to demand accountability.
By taking these steps, ordinary citizens can reshape the balance between public‑safety technology and personal privacy, ensuring that surveillance tools serve the community rather than become a hidden, nationwide data‑pipeline.
Use the tool
Open the tool →
This article was edited with AI assistance based on publicly available sources and reviewed before publishing.
