Flock Safety: Privacy Faces a Public Safety Test

Flock Safety is dealing with a problem that goes beyond an ordinary product complaint. The company has built a business around cameras, drones, and automated license-plate recognition, selling those tools largely to law-enforcement agencies. Its pitch is familiar: help investigators locate vehicles, connect incidents, and respond to public-safety threats more efficiently. The controversy is about what happens when that infrastructure becomes available for purposes it was never meant to serve.

CEO Garrett Langley has responded with a media campaign that frames the debate as a search for balance. In an interview with Fox News, he argued that the country should not choose privacy or security as an absolute priority, but should look for a compromise that protects both. That position sounds reasonable in the abstract. The hard part is defining who sets the limits, who checks compliance, and what happens when an officer or agency crosses the line.

“When people only talk about privacy or only talk about safety, they have the priorities wrong,” Langley said, arguing that the goal should be security balanced with privacy.

Why Flock’s surveillance model is under scrutiny

The technology itself is straightforward to describe, even if its consequences are not. Cameras positioned around neighborhoods, roads, and commercial areas can capture vehicle information. Automated license-plate recognition helps organize those records, while drones can add another layer of observation. For police departments, the combination can create a searchable network that reaches far beyond a single crime scene.

That network is also what makes governance so important. A person may never know that their vehicle was recorded, how long the record is retained, which agencies can access it, or whether a search was connected to a legitimate investigation. A system designed for public safety can become a privacy problem when access is broad, logging is weak, or oversight is treated as an afterthought.

An investigation by The Washington Post reported 46 cases in which law-enforcement personnel were accused of using Flock technology without authorization. The reported examples included officers allegedly tracking wives, girlfriends, or former partners. These allegations are especially damaging because they turn an abstract debate about surveillance into a very ordinary abuse-of-power scenario: someone with privileged access using a public system to monitor a private relationship.

• Camera networks, drones, and license-plate recognition can create a persistent record of movement.
• Residents may have limited visibility into who searched the data or why.
• Personal misuse by authorized users can undermine trust in the entire program.

Langley has not denied that misuse is a serious concern. During an interview with CBS News, he apologized to a person affected by the reported behavior and said the situation was painful to hear about. At the same time, he defended Flock’s role, saying he did not believe the company created police abuse and arguing that Flock was among the first companies to expose the problem and build tools intended to detect it.

A rare surveillance issue with cross-party appeal

Flock’s political troubles are notable because the criticism is not confined to one side of the American political spectrum. Privacy advocates on the left have long challenged mass surveillance and the expansion of automated monitoring. More recently, conservative concerns about government reach, data collection, and institutional accountability have pushed similar technology into a wider political conversation.

Michigan Democratic Senate candidate Abdul El-Sayed criticized his opponent Mike Rogers over support for what he described as the unchecked spread of Flock cameras. Senator Bernie Sanders also posted a direct condemnation online: “STOP AI MASS SURVEILLANCE. STOP FLOCK.” Whatever their broader policy differences, those statements point to a shared concern: surveillance tools can grow faster than the rules governing them.

The backlash resembles the political reaction to large data centers, another technology issue that has attracted opposition from both progressives and conservatives for different reasons. With Flock, the common ground is easier to identify. People may disagree about crime policy, but many are uncomfortable with the idea that government agencies can quietly build detailed records of movement without clear limits or meaningful public consent.

That does not make every criticism equally specific or every proposed restriction automatically effective. Cameras and license-plate systems can assist investigations, and agencies may have legitimate reasons to use them. But a public-safety benefit should not be treated as a blanket justification. The relevant questions are practical: What incidents justify a search? How long can data be stored? Can an officer look up a person for personal reasons? Are searches logged and independently reviewed?

What agencies and residents should watch next

For residents, the central issue is not simply whether surveillance should exist. It is whether surveillance operates within boundaries that ordinary people can understand and challenge. License-plate recognition data can reveal patterns of travel, even when a person has done nothing wrong. If an officer can access that information after hours, or if records are shared without clear authorization, the privacy risk becomes much larger than the original camera installation might suggest.

Law-enforcement agencies considering these systems should treat internal controls as part of the deployment, not as a feature to add later. A responsible procurement process should require written search policies, role-based access, audit logs, regular reviews, and consequences for misuse. Agencies should also explain retention periods and data-sharing arrangements in plain language. These steps will not eliminate every risk, but they make abuse easier to detect and harder to dismiss.

• Ask whether every search is automatically logged and reviewed by someone outside the immediate investigation.
• Check how long records are retained and which other agencies can access them.
• Look for a clear complaint process, public reporting, and documented penalties for unauthorized use.

Flock, meanwhile, faces a credibility test. Its executives can argue that the company helps reveal misuse, but that claim will carry more weight if customers and the public can see evidence of stronger access controls and transparent enforcement. The most important response may not be another interview. It may be a measurable change in how permissions, audits, alerts, and disclosures work in everyday deployments.

State lawmakers are another part of the story. Rules for police access to surveillance data remain uneven, and new legislation could determine how agencies use automated vehicle records, how long they keep them, and whether residents can learn when their information has been collected. Watch for policy changes, public-contract requirements, and independent audits rather than treating corporate promises as the final word.

Langley’s call for compromise is a useful starting point, but compromise cannot mean that privacy concerns are acknowledged while the underlying system remains opaque. Privacy and public safety need enforceable boundaries, public input, and accountability that reaches beyond the vendor. Until those pieces are in place, Flock Safety’s controversy will remain a warning about how quickly a helpful investigative tool can become a contested surveillance network.