Flock Safety’s CEO, Garrett Langley, has publicly conceded that his surveillance company failed to act swiftly enough when alerted to law enforcement officers misusing its license plate recognition technology. The admission marks a significant shift for the Atlanta-based firm, which has long positioned itself as a privacy-conscious alternative to traditional government-run camera networks. In a candid interview, Langley acknowledged that internal protocols designed to catch rogue officers were too slow, allowing a handful of bad actors to exploit the system for personal gain before the company intervened.
The controversy centers on a series of incidents where police officers used Flock’s vast network of automated license plate readers (ALPRs) to stalk romantic partners, harass journalists, or conduct unauthorized background checks on civilians. While Flock Safety has always maintained that its technology is a neutral tool for solving crime, the company’s own internal audits revealed a pattern of abuse that went unnoticed for weeks. Langley admitted that the company’s “trust but verify” approach was fundamentally flawed, stating, “We built a system that assumed the best in people, but we didn’t build a fast enough mechanism to catch the worst.”
Why Flock Boss Admits Surveillance Firm Acted Too Late on Police Abuse
The timing of this admission is critical. Flock Safety has aggressively expanded across the United States, installing its solar-powered cameras in thousands of neighborhoods, HOAs, and small municipalities. The company’s sales pitch has always emphasized its “privacy-first” design, which includes blurring faces and storing data for only 30 days. However, the recent revelations have cast a harsh light on the gap between marketing rhetoric and operational reality. Langley’s confession that the surveillance firm acted too late on police abuse is not just a PR crisis; it is a legal and ethical reckoning for an industry that operates largely without federal oversight.
Internal documents obtained by investigative journalists show that Flock received multiple complaints from citizens who suspected they were being tracked. In one alarming case, a deputy sheriff used the ALPR system to follow his ex-girlfriend’s vehicle for over a month. The deputy’s queries were flagged by Flock’s automated anomaly detection system, but the alert sat in a queue for nearly two weeks before a human reviewer investigated. By that time, the deputy had already used the data to show up at the victim’s workplace. Langley admitted that this delay was “unacceptable” and that the company has since overhauled its response team to prioritize real-time intervention.
The Structural Problem with Private Surveillance
Critics argue that Langley’s apology, while necessary, does not address the root cause of the problem. Flock Safety sells its cameras directly to police departments, but it also sells to private citizens and businesses. This creates a confusing web of data access where officers can query the network from their personal phones or patrol car laptops without a warrant. The company’s own terms of service prohibit using the data for “personal reasons,” but enforcement has historically been reactive rather than proactive.
Langley’s admission that the surveillance firm acted too late on police abuse highlights a broader industry-wide issue: the lack of independent auditing. Flock Safety has hired a former federal prosecutor to oversee compliance, but the company still conducts its own internal reviews. Privacy advocates argue that self-regulation is insufficient. They point to the fact that Flock’s cameras are often placed in low-income and minority neighborhoods, where residents have little say in the deployment of the technology. The company’s promise to “reduce crime” is often used to justify the erosion of Fourth Amendment protections, yet there is little peer-reviewed evidence that ALPR networks actually deter crime.
What Changes Are Coming?
In response to the backlash, Langley outlined a series of immediate reforms. First, Flock Safety will now require mandatory two-factor authentication for all law enforcement queries, making it harder for officers to use shared credentials. Second, the company is implementing a “zero-tolerance” policy for misuse, meaning that any officer found to be using the system for non-law-enforcement purposes will be permanently banned from the network, and their department will be notified. Third, Flock is rolling out a real-time alert system that notifies a supervisor within minutes of a flagged query, rather than days.
However, Langley stopped short of supporting federal legislation that would mandate nationwide standards for ALPR usage. He argued that state-by-state regulations are more adaptable, but critics note that this position conveniently allows Flock to continue operating in jurisdictions with lax privacy laws. The CEO’s admission that the surveillance firm acted too late on police abuse is a step toward accountability, but it remains to be seen whether these voluntary reforms will be enough to restore public trust.
Ultimately, the Flock Safety scandal serves as a cautionary tale for the entire surveillance industry. Technology is not neutral; it reflects the values of the people who build it and the policies of the people who deploy it. By admitting fault, Langley has opened the door for a more honest conversation about the limits of private policing. But without external oversight, the next scandal is not a question of “if” but “when.” For now, the company’s promise to do better is a welcome change, but it is only a first step in a long journey toward ethical accountability.
