Mass surveillance networks don't build themselves. They expand quietly, one license plate reader at a time, until an entire country is wired into a searchable grid. Flock Safety built a sprawling web of automated license plate reader (ALPR) cameras across thousands of American communities, logging billions of data points every month. But raw data collection is only part of the story. The real issue is who gets to look at that data and why.
For years, privacy advocates warned that putting searchable location histories into the hands of local police officers without strict warrant requirements was asking for trouble. They were right. Across the country, police officers, dispatchers, and task force agents have been caught using the Flock system to stalk ex-partners, spy on acquaintances, and run personal queries completely unrelated to law enforcement.
Garrett Langley, the founder and CEO of Flock Safety, finally owned up to part of the problem. After mounting public pressure and a wave of arrests involving officers misusing the platform, Langley admitted that the company and law enforcement agencies took too long to act against systemic abuse.
The Reality of Police Misuse
When thousands of local law enforcement agencies have instant access to a vast repository of vehicle movements, abuse isn't a hypothetical risk. It is a statistical certainty.
Consider what has happened recently in states like Georgia, where local investigations and internal audits exposed multiple law enforcement employees weaponizing the database. Dispatchers, sheriffs' deputies, and investigators were arrested and charged after internal tracking tools flagged dozens of unauthorized searches. Some used the system to track romantic interests. Others ran checks on people they knew personally.
These weren't sophisticated cyberattacks. They were routine logins by people who simply had too much access and too little supervision.
For a long time, tech companies selling tools to the government hid behind a convenient shield. They claimed their software was just a neutral utility, and that policing the users was up to the departments themselves. But when private companies build infrastructure that tracks the daily commutes of ordinary citizens, hands-off governance stops working.
Too Little, Too Late on Accountability
Flock's recent policy overhauls include making their "Audit Assistance" tool mandatory for all customers, requiring case codes to justify searches, and shortening default data retention periods in many areas. These changes are designed to flag abnormal search patterns and lock out suspicious users before things spiral out of control.
These safeguards are welcome, but they arrive years too late.
For years, the system lacked basic account security features like mandatory multi-factor authentication across the board, making unauthorized access far easier than it should have been. When software companies prioritize rapid municipal adoption and frictionless sales over strict privacy defaults, accountability becomes an afterthought.
Critics point out that mandatory search justification fields can still be bypassed if users enter generic or untruthful reasons. Without independent oversight or strict warrant requirements enforced by courts rather than private software algorithms, internal auditing tools can only catch the most blatant abusers.
The Core Problem with Automated Dragnet Surveillance
The debate over Flock Safety goes beyond rogue cops breaking department rules. The fundamental architecture of modern automated surveillance creates a massive imbalance of power.
When a single private company maintains a database tracking millions of everyday journeys, the expectation of privacy while driving vanishes. Citizens shouldn't have to rely on a tech CEO's belated realization that abuse is unacceptable to feel secure from unwarranted tracking.
Law enforcement officials often defend these networks by pointing to solved cases and recovered stolen vehicles. That utility is precisely why the technology spreads so fast. Yet convenience cannot override basic civil liberties. If a tool is powerful enough to track anyone's movements across an entire state, it requires ironclad legal guardrails from day one, not after the scandals break and the headlines force a corporate response.
Fixing a surveillance state requires more than software updates and mandatory audit logs. It demands a hard look at whether we want our daily travels permanently logged in private databases accessible by thousands of local officials with minimal judicial oversight.
