Criticism of automated license plate reader networks has reached a point that advocacy groups rarely achieve: it has produced formal government action in a small but notable set of U.S. jurisdictions. Two populous states and two large cities are among the places where elected or appointed officials have taken direct steps in response to concerns about how these systems operate. The details of each measure have not been uniformly disclosed, but the pattern is real and worth tracking closely.

What happened

The pushback on Flock Safety license plate reader accountability has moved out of conference rooms and op-ed pages and into the machinery of government. That shift is significant on its own. Most surveillance technology never faces this kind of scrutiny from elected bodies.

The actions taken vary by jurisdiction. Some appear to involve contract reviews. Others involve formal inquiries or policy directives. What they share is that they were initiated by officials with the authority to impose requirements, not just express concern.

The full scope of what each jurisdiction has decided has not been publicly confirmed in uniform detail. That opacity is itself part of the story.

Who is affected

The people most directly affected are residents of the jurisdictions that have acted. Any restriction or requirement imposed there would govern how plate-reading technology is used in their communities — which roads are monitored, how long data is kept, and who can access it.

Law enforcement agencies that use automated plate readers for routine work would also need to adjust. These systems are used to flag stolen vehicles, locate people with outstanding warrants, and build movement histories. Changing the rules mid-operation is not a simple administrative task.

There is a structural tension worth naming here. The jurisdictions most likely to impose accountability conditions tend to be large, populous places — exactly the markets where a plate-reader network becomes most valuable. That creates a situation where the places with the most political pressure are also the places with the most operational significance.

Privacy advocates and civil liberties organizations now have a small set of real cases to point to. That matters. It is easier to argue that formal action is possible when you can point to somewhere it has already happened.

What the real risk is

The risk is not that one company’s product gets restricted in a few cities. The deeper structural risk is what happens if these early actions stall before they produce enforceable rules.

A non-binding inquiry is not the same as a hard requirement. If the measures taken so far remain at the level of guidance or review without resulting in written, enforceable policy, the practical effect on how data is collected and retained may be limited — even where political will genuinely exists.

There is also a geography problem. Jurisdictions acting independently of one another risk creating a patchwork. If oversight is tight in one city but absent in the next county over, the technology does not disappear — it migrates toward the places with the least scrutiny. The floor does not rise; it just becomes uneven.

A third risk is subtler. Visible action in a few high-profile places can reduce pressure elsewhere. If the story becomes “several cities are handling it,” jurisdictions that have not yet moved may feel less urgency to do so. The broader network of plate readers continues to expand in those places with less examination.

What to do today

These steps are achievable this week, regardless of whether you have a technical background.

• Find out where your jurisdiction stands. Search your city council’s or state legislature’s website for any resolutions, ordinances, or committee reports mentioning automated license plate readers or ALPRs. Council meeting minutes are usually posted publicly. Look for any vote or formal directive from the past two years.
• Ask your representative directly. Email or call your city council member or state legislator and ask one specific question: has your office reviewed any contracts or policies related to automated license plate reader networks operating in this jurisdiction? A direct question is harder to deflect than a general inquiry about privacy.
• Submit a public records request. If you are a journalist, researcher, or simply a motivated resident, you can file a public records request — often called a FOIA request at the federal level, or an equivalent open-records request at the state or local level — asking your local law enforcement agency for documentation of any data-sharing agreements tied to plate reader systems. Most jurisdictions have an online portal or a designated records officer. The request does not need to be complicated. Ask for contracts, data retention policies, and any agreements to share data with third parties.
• Follow the proceedings in the jurisdictions that have acted. The initial announcement of a review or inquiry tells you almost nothing about what will actually change. The details — what data must be deleted and when, who can request access, whether residents can find out if they were tracked — will emerge later, in implementation documents and amended contracts. Set a reminder to check back.
• Check whether your state has a privacy or surveillance oversight body. Some states have established offices or legislative committees specifically tasked with reviewing surveillance technology contracts. If yours does, their published reports are a faster path to answers than starting from scratch.

Why this keeps happening

Surveillance technology typically enters public infrastructure through procurement decisions made at the agency level — a police department signs a contract, equipment gets installed, and operations begin. That process happens well below the threshold of legislative review. By the time elected officials become aware of what is running in their jurisdiction, the technology is already embedded in daily operations.

At that point, unwinding it carries real costs: retraining, gaps in investigative capacity, contractual obligations. Those costs create institutional resistance that has nothing to do with whether the original decision was sound. The question shifts from “should we have this?” to “can we afford to remove it?”

The companies that build these systems have strong incentives to move quickly into new markets. Speed matters more than waiting for governance frameworks to catch up. That is not an accusation — it is a description of how competitive markets work. But the result is that accountability questions arrive after the fact, if they arrive at all.

There is a deeper problem that applies to this kind of technology specifically. Automated plate reader networks operate across jurisdictional lines. Data collected in one city may be accessible to agencies in another. When oversight is fragmented by jurisdiction, there is no single point where accountability can take hold. Each locality can only govern its own piece of a system that functions as a whole. That structural gap means even well-intentioned oversight struggles to find a target that matches the actual scale of the network.

Accountability in this space tends to depend on a small number of motivated people in each jurisdiction — a council member, an advocate, a journalist — rather than on any standing mechanism. When those people move on or shift focus, the pressure dissipates. That is a design flaw in how oversight is structured, not a failure of individual effort.

Frequently asked questions

Which specific states and cities have taken action against automated license plate readers?

Two populous states and two large cities are among the jurisdictions where officials have taken direct steps, according to available reporting. The full list and the specific nature of each action have not been uniformly disclosed. Searching your state legislature’s or city council’s public records is the most reliable way to find out whether your jurisdiction is among them.

Does pushback in a few jurisdictions actually change how a national network of plate readers operates?

Not automatically. A plate reader network that spans many jurisdictions is not governed by any single authority. Action in one city restricts how the system operates there, but data sharing with agencies elsewhere may continue under separate agreements. Meaningful change at the network level would require either federal action or coordinated requirements across many jurisdictions simultaneously.

What kind of action counts as meaningful accountability for a technology like this?

Meaningful accountability generally requires written, enforceable rules — not just statements of concern or voluntary guidelines. That means defined limits on how long data is retained, clear rules on who can access it and under what conditions, and a mechanism for residents to find out whether they were subject to tracking. Inquiries and reviews are a starting point, but they only produce accountability if they result in binding requirements with consequences for non-compliance.

Related reading

• Berlin’s Repeat Data Leaks: A Governance Failure
• Russia’s Data Centers: Security by Decree, Not Design

Originally reported by therecord.media. This article summarises that reporting and adds practical guidance.

Scams, fraud, bots, and manufactured noise keep spreading because the internet was built with no reliable way to know who anyone actually is. Everyone deserves authenticity and accountability online, and that is the mission we are working on. Subscribe to follow our coverage as these cases develop.