Flock is trying to answer a growing concern around police access to automatic license plate readers: how to stop officers from using the technology for illegal or illegitimate purposes. But the sharper question is not only whether misuse can be caught after the fact. It is whether the system has been built too broadly for the safeguards now being added to carry enough weight.
New safeguards target a real misuse problem
Flock, a police-tech company known for a network of some 120,000 automatic license plate readers around the US, announced changes to its platform last Thursday. The stated aim is to prevent officers from using the system without a legitimate law-enforcement reason.
The immediate context is serious. The Washington Post recently identified 50 cases in which officers misused systems from Flock and its competitors, often to stalk and harass women. In Wisconsin, one woman alleged that her officer ex-boyfriend searched for her car 179 times. Another woman was being stalked by the chief of police, leaving her with nobody to report him to.
Flock’s response includes practices meant to make every search more accountable. The company has pointed to software that can flag abnormal searches and a requirement that officers enter a criminal case number before running a search.
Those measures address part of the problem. They recognize that access to location-related vehicle data can be abused by people who already have police credentials. They also suggest that Flock sees a need for more friction around searches that may otherwise be too easy to run.
The case-number rule has an obvious weakness
The new case-number requirement sounds like a straightforward control: if every search must be tied to a case, then every search has a stated purpose. But Flock confirmed to MIT Technology Review that it does not verify those case numbers.
That leaves room for officers to enter bogus case numbers. The source article also notes that officers have lied to get around other Flock safeguards, which means the company is not dealing with only accidental misuse or minor procedural mistakes. It is dealing with the possibility that someone with access may intentionally evade the rules.
A stronger version of the same idea would connect the search to police department records, so a case number would have to match an actual file. That kind of design could create a clearer audit trail. It could also be more intrusive, which is part of the broader trade-off: stronger safeguards may require deeper integration with police systems.
The point is not that a case-number field is useless. It is that a field officers can fill with false information cannot, on its own, resolve the concern raised by stalking and harassment cases.
The deeper question is how broad the network should be
Much of the defense of Flock starts from a simple premise: if the cameras help solve crimes, then the loss of privacy may seem acceptable. The source article challenges that framing by asking what kind of crime-fighting system Flock has chosen to build.
That question matters because the current system reflects choices. Flock’s platform is shaped by decisions about what information is collected, who can search it, how long the data is kept and how widely it can be shared. Those choices define the bargain between public safety and civil liberties.
Flock often points to cases involving kidnapped or missing people. In that situation, access to a nationwide network of cameras could be valuable. But the same use case also shows how a narrower design might work.
For example, searches connected to an active Amber Alert, or a similar emergency, could be given wider access to data from surrounding cities. That would preserve the value of the network in urgent situations without requiring the same scope of access for every kind of search.
This is the central issue: accepting technology as one tool for solving crime does not require accepting every design choice a vendor has made. A system can be useful and still collect too much, retain too much or share too widely.
Retention and sharing are part of the bargain
Flock mostly operates as a national network. Police in one city or state can search data collected in another, and agencies can retain that data for months or years.
Yet Flock itself says 90% of searches happen within a week of an incident. That fact supports a different possible model: keep and share data only for as long, and as widely, as it is actually useful for solving crimes.
The company recently changed its recommended retention time to seven days. But agencies can still hold onto data for as long as they like. A recommendation is not the same as a binding limit, and that distinction matters when the concern is mass surveillance.
Privacy and civil liberties groups are not only worried about individual bad searches. They are worried that a tool sold as a way to stop crime is becoming a broad surveillance network. Those concerns have already led to backlash, including cities canceling contracts and some states trying to pass laws to limit or ban license plate readers entirely.
Communities may decide the limits next
Flock could design its surveillance system more narrowly. That would not satisfy every critic. Chad Marlow, a senior policy counsel at the ACLU, half-joked that the most acceptable Flock contract by his standards is
one that is never signed
He also emphasized that limits on surveillance should come from new laws, not only from new Flock guidelines. Flock CEO Garrett Langley said he will
probably always have a different view than the ACLU.
The disagreement is also tied to Flock’s business model. License plate readers have been around since the 1990s and have been used for tolls and ticketing. Flock’s pitch is different: it builds a massive network that collects rich amounts of data and helps police departments make sense of information from their own cameras and from others.
That approach is central to the company’s recent $8 billion evaluation. Narrowing the system could therefore affect more than product policy. It could challenge the very thing Flock sells to police departments.
The next phase may be decided outside the company. Some cities have canceled contracts. Some have moved to competitors. Others are pausing while residents consider how the technology should be used and what rules police should follow.
That local debate may produce different answers in different places. But it puts the core question where it belongs: not whether crime-solving matters, but how much surveillance people should be asked to accept in its name.