The Erosion of Trust: How Flock Safety’s Misleading Claims Are Undermining Public Confidence

The promise of smart city technology once felt like a leap into a safer, more efficient future. Cameras that could read license plates in real time, sensors that tracked traffic flow, and systems designed to help law enforcement respond faster — all of it sounded like progress. At the center of this vision was Flock Safety, a company that positioned itself as a trusted partner for municipalities looking to modernize public safety. But over the past year, that trust has eroded. Repeated instances of misleading statements, omitted details, and outright inaccuracies shared with city councils, police departments, and the public have left many questioning not just the technology, but the integrity behind it.

What began as enthusiasm for automated license plate readers (ALPRs) has turned into skepticism. In city after city, officials who once welcomed Flock’s presentations now describe feeling misled. The pattern is consistent: Flock representatives emphasize crime reduction and community safety, often citing statistics or case studies that later prove difficult to verify. When pressed for data sources or methodology, responses are vague or delayed. In some cases, claims made during public meetings have been contradicted by internal documents or independent audits.

One recurring issue involves the presentation of crime statistics. Flock frequently highlights drops in certain offenses after installing its cameras, suggesting a direct causal link. Yet in several jurisdictions, independent reviews have found no significant change in crime rates — or worse, that the data used to support Flock’s narrative was selectively chosen or misrepresented. For example, in a midwestern city council meeting last fall, a Flock executive claimed a 40% reduction in vehicle thefts over six months. Six months later, a freedom of information request revealed that the baseline period used for comparison included an unusually high spike in thefts due to a temporary police staffing shortage. When that anomaly was accounted for, the actual change was negligible. The company did not correct the record publicly.

Transparency about data use is another point of contention. Flock partners with agencies across state lines to expand its surveillance network, often without clear public disclosure. In one case, a city discovered that license plate data was being used to identify vehicles involved in unrelated investigations, raising concerns about mission creep. In another, data collected by Flock was found in a federal database with no clear link to an active investigation, prompting questions about retention policies and oversight.

Equally troubling is how Flock handles discussions around privacy and surveillance. While the company publicly states that data is retained for only 30 days and is accessible only to law enforcement with proper authorization, internal training materials and contractor agreements obtained through public records requests suggest a more complex reality. In some cases, data retention periods appear to be extended under vague "investigative hold" provisions, and access logs show queries from personnel not officially affiliated with active investigations. When city attorneys have asked for clarification, Flock has sometimes responded with technical jargon or redirected the conversation toward general statements about public safety — avoiding direct answers.

There’s also the matter of partnerships. Flock often frames its collaborations with police departments as cooperative efforts to solve crimes. But in several instances, departments have reported feeling pressured to renew contracts or expand deployments based on promises that weren’t fulfilled. One police chief in the Southwest described being told that integrating Flock’s system with their existing dispatch software would be "seamless and immediate." Six months later, after significant staff time and budget were spent on the effort, the integration remained incomplete. When questioned, Flock cited "unforeseen technical complexities" — a explanation that rang hollow given how often similar promises had been made elsewhere.

These patterns aren’t just about missed deadlines or overstated benefits. They point to a broader issue: a reluctance to be honest about limitations, risks, and uncertainties. Technology companies selling tools to public institutions have a responsibility to be clear about what their products can and cannot do. When that responsibility is ignored, it’s not just budgets that suffer — it’s public trust.

The consequences extend beyond individual cities. As more municipalities reconsider or slow down their adoption of automated surveillance tools, the ripple effects are felt across the industry. Vendors that rely on transparency and accountability may find themselves unfairly tarnished by association. Meanwhile, communities already wary of surveillance technologies see their concerns validated, making future conversations about public safety innovation even harder to navigate.

There’s still time for Flock to change course. Admitting past missteps, providing verifiable data, and engaging in open dialogue with the communities they serve could help rebuild credibility. But that requires more than updated marketing materials. It demands a shift in how the company communicates — one rooted in honesty, not persuasion.

For now, the lesson is clear: when a company repeatedly tells city councils, police, and the public things that aren’t true, the damage isn’t just to its reputation. It’s to the very idea that technology can be a force for good in public safety. And that’s a loss no algorithm can fix.