Flock Safety operates a network of roughly 120,000 automatic license plate readers across the United States, and the company recently announced changes meant to stop officers from misusing the platform. Those changes sound reassuring on the surface. Dig a little deeper, and the loopholes become impossible to ignore.
Documented cases of abuse have surfaced across multiple states, with at least 50 confirmed incidents of officers using Flock and similar systems to stalk or harass individuals, many of them women. One alarming case involved a woman whose car was searched 179 times by an ex-boyfriend who happened to carry a badge. These are not edge cases. They are predictable outcomes of a system built with weak guardrails and broad access.
The Safeguards That Are Not Really Safeguards
Flock’s newest policy requires officers to enter a criminal case number before running a search. The intent is reasonable. The execution falls apart immediately because Flock does not verify those case numbers against any police department’s actual records. An officer can type in anything and proceed. That is not accountability. That is the appearance of accountability.
A genuinely robust alternative would integrate directly with department case management systems so that every search ties to a verifiable, active investigation. It would create an audit trail that supervisors and oversight bodies could actually use. Technology capable of doing exactly that already exists in enterprise software across other industries. The choice not to build it is a design decision, not a technical limitation.
A Network Designed Wider Than It Needs to Be
Flock’s own data reveals that 90 percent of searches occur within one week of an incident. That single statistic carries enormous implications. If almost all legitimate investigative use happens in the first seven days, there is no compelling public safety reason to retain location data for months or even years, which many agencies currently do. The company recently updated its recommended retention period to seven days, but agencies are free to ignore that guidance entirely.
The nationwide scope creates similar concerns. Officers in one state can query data collected in another, building a detailed picture of a person’s movements across jurisdictions without a warrant. Several cities have already canceled Flock contracts in response to community pressure, and some state legislatures are actively drafting bills to cap retention periods and restrict cross-jurisdictional sharing. Civil liberties groups argue persuasively that binding law, not voluntary guidelines, is the only meaningful constraint.
Why the Design Choices Matter for Everyone Buying Into Smart Security
For consumers and municipalities evaluating smart security technology right now, the Flock debate is a timely warning. The question is never simply whether a technology works. The question is what tradeoffs the vendor has already made on your behalf before you signed anything. Buyers entering the public safety tech market in 2024 and beyond should demand granular data retention controls, verified audit trails, and clearly defined access tiers as baseline requirements, not premium add-ons. The vendors willing to compete on those terms are the ones worth trusting with infrastructure that touches civil liberties directly.
