A billion‑dollar camera network quietly let federal agents search local drivers’ movements, even when cities thought they had locked the door.
Story Snapshot
- Flock Safety’s license plate cameras sent local driver data into nationwide lookup tools that federal agencies could search, often without city consent.
- Audits in California and Washington found “nationwide” and “statewide” sharing features turned on or re‑enabled without local departments realizing it.
- Federal agencies including immigration enforcers accessed location data from communities that had banned such sharing under state sanctuary and privacy laws.
- Contract language and default settings gave Flock broad rights to share data, exposing a deeper problem in how modern surveillance systems treat public privacy.
How Local Camera Data Ended Up in Federal Hands
Flock Safety sells automated license plate reader cameras that many cities use to track cars entering neighborhoods and business districts. Each time a vehicle passes one of these cameras, the system logs the license plate, vehicle details, time, and location into a cloud database for about 30 days by default. That database connects to “national lookup” and “statewide lookup” tools. When those tools are on, any police agency in the network can search another city’s camera data.
Multiple investigations found that these lookup tools were active in places where city leaders believed they had blocked outside access. In Mountain View, California, a “national lookup” setting was turned on for one camera without the city’s knowledge, while a “statewide lookup” feature ran on 29 of 30 cameras for 17 months. More than 250 agencies that never signed a sharing agreement ran about 600,000 searches of Mountain View’s drivers in one year, including federal agencies such as the Bureau of Alcohol, Tobacco, Firearms and Explosives.
State Laws, Sanctuary Rules, and Silent Workarounds
California law bars public agencies from sharing license plate reader data with out‑of‑state or federal agencies, and sanctuary state rules specifically forbid sharing with Immigration and Customs Enforcement and Customs and Border Protection. Yet audits and lawsuits say that Flock’s systems still exposed Californians’ data to federal and out‑of‑state police. In Oxnard and Ventura County, officials set their systems to “California only,” but later found that a “nationwide query” feature had been silently re‑enabled, allowing agencies around the country to query their data.
A class‑action lawsuit in California argues that Flock tracked millions of people’s movements and illegally shared that data beyond state borders. Civil rights groups in Massachusetts and elsewhere warn that Flock’s standard contract gives the company a “worldwide” license to use customer data and allows disclosure to federal agencies for “investigative purposes,” even when a local department believes it has locked data access to its own officers. This means a city can follow its own rules on paper while the underlying contract and software still push data into a national pool.
Border Patrol, Immigration Enforcement, and Backdoor Access
Research by the University of Washington Center for Human Rights showed how these systems affect immigration enforcement. Records from 31 agencies in Washington state revealed that at least eight had enabled direct data sharing with Border Patrol in 2025, and at least ten more gave Border Patrol apparent “back door” access to their networks without formally approving it. In practice, that meant federal agents could track vehicles tied to immigration cases using local cameras, even where communities opposed such use.
So,
Flock is a system of Automated License Plate Readers (ALPRs) that are now in over 5,000 communities with 80k–100k+ cameras across 49 states. Every month, Flock cameras generate over 20 billion vehicle scans (roughly 650–700 million scans per day).
Each scan logs your… pic.twitter.com/7D2ofaRxAC
— TheLastPatriot (@lastpatriotFR) July 21, 2026
National civil liberties advocates say this pattern—local data feeding federal searches through vendor tools—matches earlier problems with other license plate systems. They note that most plates scanned belong to drivers not suspected of any crime, yet the data is stored and shared widely. Critics across the political spectrum worry that this creates a quiet surveillance web that can be used for immigration raids, asset seizures, or political targeting, with little local control and almost no public transparency.
Why This Surveillance Fight Resonates Across Party Lines
For conservatives, these stories feed anger at a distant federal bureaucracy and powerful tech companies that ignore local rules and property rights. Many see Flock’s network as one more tool for unelected officials and “deep state” agencies to track citizens, vehicles, and businesses far beyond what most people would call reasonable policing. They also worry this data could be misused for taxes, gun regulation, or financial probes that hit working Americans hardest.
For liberals, the same facts highlight fears about discrimination, immigration crackdowns, and widening gaps between those with power and those without. They point to evidence that license plate data has helped immigration agents find and detain people in sanctuary cities, and that the burden of constant tracking falls more on minority neighborhoods and low‑income drivers. Many on both sides agree on one core point: local voters never clearly consented to a coast‑to‑coast tracking grid where a mistake in a vendor’s settings can expose entire communities to federal surveillance.
Contracts, Defaults, and the Bigger Question of Consent
Flock says on its website that communities control whether their data is shared and that sharing with federal agencies is turned off by default. Yet city audits, lawsuits, and state reports now show repeated cases where “national” or “statewide” sharing was enabled, re‑enabled, or used in ways local officials did not expect. Some cities have responded by canceling contracts, passing new rules, or demanding clearer language that blocks vendor‑controlled data sharing beyond local borders.
Policy experts argue that the deeper problem goes beyond one company. Modern surveillance systems are built for maximum connectivity, not careful consent. When data from thousands of cameras flows into one corporate cloud, a single toggle or clause can shift control from local residents to a national network overnight. Whether you lean right or left, that raises a basic question about American self‑government: if people cannot see or limit how their daily movements are tracked and shared, who is really in charge—voters, or the surveillance machines they pay for?
Sources:
thegatewaypundit.com, flocksafety.com, paloalto.gov, acluohio.org, aipolicydesk.com, placa.ai, losaltosca.gov, haveibeenflocked.com, techdirt.com, aclu.org, austintexas.gov, facebook.com, aclu-ia.org, platesmart.com, assets.aclu.org, information.auditor.ca.gov, brennancenter.org
