Public Safety Tech Walks a Tightrope as Flock Safety Navigates Bipartisan Scrutiny
The automated surveillance provider is defending its business model while confronting documented misuse by law enforcement and regulatory proposals from both sides of the aisle.
A Compromise That Satisfies No One
Garrett Langley has spent the past several weeks making the rounds on cable news and broadcast networks, attempting to reframe the conversation around his company's automated surveillance products. According to Flock Safety, the nation needs to strike a balance between two competing priorities: individual privacy and public safety. In Langley's telling, anyone emphasizing just one side of that equation is missing the point.
The CEO's media tour comes as Flock confronts pressure from an unusual coalition. Automated license plate recognition systems, aerial drone monitoring, and camera networks have become a flashpoint for politicians who rarely agree on technology policy. At DailyTechWire, we've tracked how data center expansion and AI infrastructure debates have created strange-bedfellow alliances across the political spectrum; now surveillance technology is following a similar trajectory.
Three Republican members of the House recently introduced legislation that would bar federal agencies from purchasing automated surveillance systems employing facial recognition, biometric identification, or license plate scanning. The bill specifically names Flock Safety products. Meanwhile, Michigan's Democratic Senate candidate Abdul El-Sayed has criticized his opponent for supporting what he characterized as mass deployment of Flock cameras tracking citizens without their knowledge. Vermont Senator Bernie Sanders posted a blunt directive on social media: stop AI mass surveillance, stop Flock.
When the Product Becomes the Evidence
The intensity of the backlash is rooted in documented incidents rather than hypothetical risks. Investigative reporting identified 46 separate cases in which police officers stand accused of accessing Flock systems for purposes outside their official duties. The alleged misuse includes officers surveilling romantic partners, former spouses, and other individuals with whom they had personal relationships.
Langley acknowledged the harm caused by these incidents and expressed regret after listening to an interview with one person affected. Yet he also argued that Flock did not create the underlying problem of law enforcement abuse. Instead, he positioned the company as the first to build technological safeguards that can surface such misconduct.
That framing has done little to satisfy civil liberties organizations. The tension lies in a fundamental question about surveillance infrastructure: does building audit trails into a pervasive monitoring system mitigate harm, or does it simply make an invasive technology slightly more accountable while expanding its reach?
Policy Adjustments Under Pressure
Flock has announced changes to its platform in response to the criticism. The company reduced its default data retention window from 30 days to seven days, a significant contraction in how long location and vehicle movement records remain accessible. The platform now requires officers to enter a case code before querying the database, creating a paper trail for each search.
Both modifications, however, include override mechanisms. Law enforcement agencies can preserve data beyond the seven-day window by activating what Flock calls Evidence Mode. The American Civil Liberties Union issued a measured response to the announced changes, noting that while the shift away from 30-day retention might represent progress, the organization had recommended a 48-hour default. Whether the adjustments constitute meaningful reform or public relations maneuvering, the ACLU suggested, will depend on how Evidence Mode operates in practice and how frequently agencies invoke it.
Langley has called for state-level legislation that would criminalize unauthorized access to Flock data. During one television appearance, he pointed to the absence of regulation and accountability mechanisms for his company's technology and others like it, describing that gap as a problem.
The Regulatory Void
The current landscape for automated surveillance in the United States is a patchwork. Some municipalities have enacted strict limits on law enforcement use of facial recognition and related technologies. Others have adopted these systems with minimal oversight or public input. Federal frameworks remain largely absent, leaving technology providers, police departments, and civil liberties advocates to negotiate terms city by city and county by county.
That fragmentation creates asymmetries. A surveillance company can scale its business model nationally while opponents must fight the same battles repeatedly at the local level. Flock has sold its products to thousands of law enforcement agencies across the country, each operating under different legal and policy constraints.
The bipartisan nature of the current backlash may signal a shift. Data center opposition has shown that infrastructure projects can unite rural communities concerned about water and energy consumption with progressive activists focused on environmental impact. Surveillance technology is now generating a similar cross-ideological response, with privacy hawks on the right joining forces with civil liberties organizations on the left.
What Compromise Looks Like in Practice
Langley's call for compromise assumes that privacy and safety sit on opposite ends of a spectrum, and that moving toward one necessarily means retreating from the other. That framing is contested. Critics argue that pervasive surveillance does not reliably produce safer communities, and that the data collected can be misused in ways that actively harm public safety for vulnerable populations.
The documented cases of officer misconduct involving Flock systems illustrate the risk. When a law enforcement officer uses surveillance infrastructure to stalk a former partner, the technology has not balanced privacy against safety; it has enabled harm under the institutional authority of a police department.
Flock's adjustments to retention periods and access logging represent one approach to mitigating misuse. Whether those changes prove sufficient will depend on factors the company does not fully control, including how rigorously agencies audit their officers' queries and how states choose to regulate the technology.
Forward Pressure
The legislative proposals currently circulating in Congress and state houses suggest that the regulatory void Langley referenced may not persist. If federal procurement restrictions pass, they would not ban Flock products outright but would prevent national security and law enforcement agencies from purchasing them unless the company restructures its offerings to remove the targeted capabilities.
State-level criminal penalties for unauthorized access, which Langley supports, would create a deterrent but would also require prosecutors to bring charges and courts to convict. The track record for holding law enforcement officers accountable for abuses of surveillance technology is mixed at best.
At DailyTechWire, we've followed how export controls, procurement restrictions, and compliance requirements shape technology markets in ways that pure market forces do not. The pressure Flock now faces from both ends of the political spectrum may force a reckoning that neither voluntary policy changes nor incremental adjustments can resolve. The question is whether the compromise Langley envisions is one that lawmakers, civil liberties organizations, or the public will accept.
