Flock Safety reads plates in 5,000 U.S. towns. ICE can query the database. Here is the contract.
In Belleville, Illinois, a town of roughly 41,000 people, a Flock Safety camera mounted on a utility pole reads the license plate of every car that passes [3]. The plate, the timestamp, the location, and a partial image of the vehicle are sent to Flock’s cloud servers. The data is retained for 30 days by default. The Belleville Police Department can search the database. So can every other police department that contracts with Flock, in any of the more than 5,000 communities the company has signed contracts with [1][3]. A query for a specific license plate returns every Flock camera in the country that has seen that plate in the retention window, with timestamps and locations. The database is the product. The cameras are the data-collection infrastructure [3][5].
Flock Safety, founded in 2017, has grown faster than any prior automated-license-plate-reader vendor [2]. The company has raised more than $700 million in venture capital and reached a private valuation reported around $7.5 billion as of 2024 [2]. The growth has been driven by a marketing model that sells the cameras directly to neighborhood homeowners associations and small-town police departments, then connects all of those installations into a single shared database queryable by any participating agency [2][3]. The Electronic Frontier Foundation’s Atlas of Surveillance has documented the deployment town by town since 2020 [1].
The Official Story
Flock Safety’s stated purpose is solving small-town and suburban crime, particularly auto theft, by giving police departments fast access to plate data that can identify a stolen vehicle within minutes of its passing a camera. The company describes itself as a public safety platform. Police departments that contract with Flock often cite specific high-profile cases where camera data helped identify a suspect vehicle. Homeowners associations that contract with Flock cite reduced burglary and vehicle theft.
The documented use cases assembled by 404 Media, The Markup, and the EFF tell a more complicated story [1][3][5]. Flock’s database is used for the vehicle-theft cases the company features in its marketing. It is also used to track the movements of individuals who have not been accused of any crime, to identify vehicles seen at protests, to track the movement of people across state lines for the purpose of accessing legal services that are restricted in some states but not others, and, in documented cases since 2022 [6], to provide data to U.S. Immigration and Customs Enforcement for civil-immigration enforcement [6]. The Belleville camera and the cameras in the other 5,000 communities do not distinguish among the use cases. They read every plate that passes [3][5].
Follow the Money
The financial mechanics work in three layers.
Flock sells cameras to the local agency or HOA on a subscription model. The typical small-town police-department contract has been reported in the $2,500 to $3,000 per camera per year range, with most departments installing between 5 and 30 cameras [2][3]. The customer pays the subscription. The hardware remains Flock’s property. The data the hardware collects flows to Flock’s cloud servers and into the cross-customer queryable database [3].
The database is the asset that gives the per-camera subscription its value. A police department that installs ten cameras gets ten cameras’ worth of local data, plus query access to every other Flock camera in the country, plus the ability to share queries with neighboring departments. The marginal value of joining the network grows as the network grows [3]. Flock’s marketing emphasizes that value directly, and the company’s growth has accelerated as the per-customer return on subscription has increased [2].
The data also has value to Flock independent of the customer. The Markup’s 2024 investigation, using public-records requests, documented patterns of internal Flock data use that the company’s contracts with police departments did not clearly authorize [5]. The customer agencies have, in many cases, not been informed of those uses or of the specific data-sharing pathways Flock operates with federal agencies [5][6].
The Network
Flock Safety is privately held. Its largest investors include Andreessen Horowitz, Bedrock, Tiger Global, and Meritech Capital [2]. The company’s board includes individuals from those firms plus several former senior law enforcement officials [2]. The customer base spans police departments in nearly every U.S. state, with the densest deployments in Georgia (where the company is headquartered), Illinois, Texas, North Carolina, and Tennessee [1][3].
The company has also signed contracts with school districts, retail chains, and large homeowners associations [3]. The school-district and HOA cameras feed the same shared database as the police-department cameras. A query in any participating agency returns hits from every type of installation. The network’s coverage is therefore broader than the count of police-contracting jurisdictions suggests, because the cameras also operate at schools and private communities that the police database otherwise would not see [3][5].
What Was Buried
404 Media and Reason’s July 2024 joint investigation documented that Flock Safety’s database has been queried by U.S. Immigration and Customs Enforcement and other federal agencies for purposes that go beyond the local-crime-fighting use case the company describes in its marketing [6]. The data-sharing pathway operates through partnerships between Flock and federal agencies that have been documented in some cases through public records and in other cases only through internal communications obtained through litigation [6]. Customer police departments have often not been notified that their cameras’ data is being used for federal civil-immigration enforcement against people the local departments themselves have no investigative interest in [6].
The Markup’s 2024 investigation, working from public-records requests in multiple states, documented additional patterns of database query that suggest some agencies have used Flock for purposes outside the company’s stated use cases, including tracking individuals based on partial physical descriptions of vehicles they are believed to drive [5]. The query logs are available through public records in jurisdictions with sunshine laws. The pattern is visible only when the work of compiling the logs across jurisdictions is done [5].
The Stakes Now
Flock Safety’s deployment continues to expand. The company’s contract list has grown by hundreds of new communities per year since 2022 [1][2]. Several states, including Virginia and California, have passed bills restricting some forms of ALPR data sharing, but the laws have generally been narrower than the practices the EFF and 404 Media have documented [1][6]. State-by-state reform has not kept pace with deployment [1].
The federal regulatory framework for ALPR deployment is absent. There is no federal statute that limits how long Flock or any other vendor can retain the data, who can query it, or under what circumstances the data can be shared with federal agencies [4]. The 2024 federal Privacy Act amendments under consideration do not specifically address private ALPR vendors [4]. The structural condition that has produced the current deployment is therefore likely to persist absent significant new legislation [4][6].
The One Thing That Matters
The Flock network’s value is not in any individual camera. It is in the joining of all the cameras into a single queryable database that lets any participating agency see the movements of any vehicle that has passed any camera in the past 30 days. The cameras are infrastructure. The database is the product. The customer cities and HOAs are the data-collection workforce, paying Flock for the privilege of contributing data to a centralized surveillance system that they themselves cannot fully access or audit [3][5].
The same pattern visible in the consumer-data-broker industry, where the data collected at the edge is monetized in a layer the data subject does not control, operates here at the level of local government infrastructure. The cities and the HOAs paying Flock subscriptions are not the only customers of the system. The other customers are the federal agencies and the cross-jurisdictional queries the local cities did not sign up for. The data flows where the contracts permit, which in the absence of federal legislation, is almost everywhere.
How we know
Every factual claim above traces to one of the entries below. Paywalled sources are marked. Where a source might disappear, the archive link points to a snapshot.
- 01
- 02
- 03
- 04
- 05
- 06
This piece traces the architecture and customer base of the Flock Safety automatic license plate reader network using the Electronic Frontier Foundation's Atlas of Surveillance, the ACLU's investigative reporting on ALPR deployments, contemporaneous reporting by Forbes, 404 Media, and The Markup, and Flock Safety's own public disclosures and reseller documentation. State-level reporting on ALPR data sharing practices draws on public records requests filed by EFF and journalists. No anonymous sources; every named jurisdiction or data-sharing arrangement traces to a public record or contemporaneous report.