Audits Find Flock Safety Camera Network Allowed Federal Access to Local Driver Data

Thousands of quiet roadside cameras built to fight crime have instead been silently feeding your driving history into federal databases you never agreed to join.

Story Snapshot

Flock Safety’s default “nationwide” and “statewide” lookup tools let federal and out‑of‑state agencies search local license plate scans without clear local consent.
City audits from California to Washington uncovered hundreds of thousands of unauthorized searches and “vendor-based” reactivation of sharing that departments had switched off.
Flock says it does not “partner with ICE,” but records show immigration and border agencies have still accessed data through its national network.
A growing backlash from both conservatives and liberals frames the system as proof that powerful tech vendors and agencies ignore local laws and public consent.

How a “crime-fighting” camera network turned into a quiet federal data pipeline

Flock Safety sells automated license plate reader cameras to neighborhoods, police, and homeowner groups on a simple promise: catch car thieves and dangerous criminals by logging every plate that drives by and checking it against hot lists. Each scan records a vehicle’s plate, make, model, color, and location, and the data is stored for about 30 days by default. In theory, local customers choose who can search those scans. In practice, internal toggles called “national lookup” and “statewide lookup” often opened the doors much wider.

City contracts and audits show that when those lookup settings are on, any law enforcement agency on the Flock network can query another agency’s camera data, even across the country. That means a small town paying for cameras to stop porch pirates might unknowingly feed a national search system that federal agencies can tap. Reports describe this not as a one-off glitch but as a design choice: a network where broad sharing is easy, and tight local control is hard.

Mountain View, Oxnard, and Ventura: cities learn their “local” data went nationwide

Mountain View, California, offers one of the clearest examples. A malware and privacy report explains that a “national lookup” setting was switched on for at least one city camera without notice; a separate “statewide lookup” toggle was active on 29 of 30 cameras for 17 months. During just one year, more than 250 outside agencies that had never signed a sharing deal with Mountain View ran an estimated 600,000 searches of the city’s plate data.

A detailed news investigation notes that among the agencies querying Mountain View’s data were the Bureau of Alcohol, Tobacco, Firearms and Explosives, the United States Air Force, and the General Services Administration inspector general. Local officials said they had not granted those agencies access. An ACLU-backed review found that the statewide lookup setting had been on since installation, and a national lookup setting on one camera had also been toggled on without the city’s knowledge. Mountain View’s city council later voted to terminate the contract.

“Vendor-based issues”: when disabled sharing quietly turns itself back on

Other California cities discovered similar surprises. Oxnard’s police department configured its Flock system to allow only “California only” access, believing this complied with state law that forbids sharing license plate data with federal agencies. A later audit, however, found that a “vendor-based issue” had re-enabled a nationwide query feature, allowing outside and federal agencies to search Oxnard’s data despite local settings meant to block them.

Ventura County’s sheriff reported the same pattern, according to local disclosures. The office’s audit showed 364,000 unauthorized queries between February and March 2025, even though the National Lookup feature had been disabled in June 2023 to follow California rules. Officials said “no one from our agency activated the national lookup feature,” pointing instead to configuration changes on Flock’s side. For many residents on both left and right, this looked less like an accident and more like proof that vendors and distant agencies override local limits when it suits them.

Border Patrol and immigration enforcement gain access through the back door

In Washington state, the University of Washington Center for Human Rights found that at least eight law enforcement agencies shared Flock data directly with United States Border Patrol in 2025, while ten more gave Border Patrol apparent “back door” access without explicitly authorizing it. The investigation concluded that local agencies often did not fully understand how their settings allowed federal access, or how broad that access could become once enabled. That finding matched a broader pattern seen in other states.

Advocacy groups report that Flock’s default contract language gives the company a “worldwide” license to use customer license plate data and to disclose it to law enforcement nationwide and federal agencies for “investigative purposes,” even when a local department tries to restrict access in the app interface. One civil liberties analysis says this model has already helped federal immigration and border officials use local license plate readers to assist with deportation efforts, despite public claims that Flock does not “partner” with Immigration and Customs Enforcement. For communities that fought sanctuary battles on both sides, this feels like the rules were quietly rewritten in the cloud.

Company denials, federal pilots, and a growing public backlash

Flock publicly insists that it does not have a contract with Immigration and Customs Enforcement and that sharing with federal agencies is “disabled by default.” The company acknowledges, however, that it ran “limited pilots” with United States Customs and Border Protection and Homeland Security Investigations, and that local agencies can choose to share data with federal partners through the network. After an Illinois audit found unlawful data sharing with Customs and Border Protection, Flock paused all federal pilot projects and promised to add clearer, distinct search permissions.

Garrett Langley, CEO of Flock Safety, called privacy activists "activist terrorists" in a closed meeting with law enforcement. Then got caught. Then sent an internal email: "My statement was inappropriate and I sincerely apologize."

The apology is fine, as apologies go. What it…

— The Dissent SF (@TheDissentSF) July 21, 2026

Despite those promises, civil liberties groups, city auditors, and now class action lawyers argue that the basic problem remains: the system is built to centralize and share data first, and to ask local permission second. A class action complaint in California accuses Flock of helping track millions of residents’ daily movements and illegally sharing that information with out-of-state and federal agencies in violation of state privacy laws. For many Americans worried about crime, illegal immigration, or government overreach, the message is the same: a billion-dollar surveillance machine grew faster than the safeguards around it, and both parties in Washington let it happen.