The debate over Flock cameras is not about whether police should have effective tools—they should. The real question is whether the public should accept a growing surveillance network when departments have failed to prove its worth, establish clear rules, or ensure accountability for misuse.
Research shows these automated license plate readers can help officers identify stolen vehicles and support arrests, but their value depends heavily on how they are managed. A randomized study found that patrols using the technology scanned nearly eight times more vehicles than manual checks and generated more hits and arrests, yet manual checks by a specialized auto-theft unit were actually linked to lower auto theft two weeks later.
Another large study tied a network of cameras to improved outcomes in some auto-theft and robbery cases, especially where cameras were dense. But researchers could not isolate the cameras' effect because police also used real-time crime centers, hundreds of other surveillance cameras, and detectives. A 2025 evaluation linked expanded camera use to reductions in shootings, motor-vehicle theft, and property crime, but found no reduction in violent crime overall.
The evidence does not show that Flock cameras fail to help police. It shows that departments should not promise broad crime reductions the data does not support. Results depend on placement, frequency of use, investigator training, and who can access the system. The burden is on police departments, not residents, to demonstrate these systems are worth the public's trust.
If Flock cameras are genuinely improving public safety, departments should show the public how. How many stolen vehicles have been recovered? How many missing people have been found? In how many serious cases did a camera alert provide a useful lead? How many leads resulted in arrests, and how many arrests helped close a case?
A camera alert is not an arrest. An arrest is not a solved case. A large database is not, by itself, a public-safety strategy. Public reporting should help communities distinguish real results from broad claims that cannot be independently verified.
Departments must also be transparent about their rules. They should publish policies detailing which agencies can search Flock data, how long information is stored, when it can be shared, and what conduct is prohibited. Every search should be tied to a legitimate police purpose, a case number, and a named employee. Supervisors should regularly review searches, and outside reviewers should be able to investigate violations.
Recent allegations of improper Flock data access, including questions raised by Senator Josh Hawley, highlight what can happen when powerful surveillance tools are used without strong protections. Departments should not dismiss these as isolated mistakes. Leaders should explain how access was gained, why safeguards failed, who was responsible for oversight, and what will change to prevent abuse.
For communities with a long history of over-policing, the concern is not just that a camera captures a license plate. It is that the government can build a searchable record of where people work, worship, receive health care, and visit family—turning ordinary movement into police data. This deepens existing imbalances of power, and strong safeguards alone do not answer the larger question: Why should expanding surveillance be the default response to public-safety concerns when investments in housing, health care, youth opportunity, and community-based safety could prevent harm without expanding the state's power to monitor people?
Some cities are already pushing back. Tempe, Arizona, recently canceled its Flock contract as the mayor warned of privacy risks. That decision underscores a growing recognition that public trust cannot be assumed simply because a department says a technology is useful. The question is not whether police should have effective tools, but at what cost to civil liberties and community trust.
