What Your City Council Isn't Being Told About LPR Privacy

What Your City Council Isn't Being Told About LPR Privacy

If license plate reader (LPR) technology comes before your council this year, you may hear a familiar debate.

Most people hear about public safety technology and think of crime reduction, stolen-vehicle recoveries, and investigative leads. Some will also raise fair concerns about surveillance, privacy, and data sharing.

Both sides are valid, and where they can meet in the middle is in considering the question:

What privacy protections actually exist inside the system your agency is considering?

The answer is critical because there is often a significant gap between what is said in a council meeting or on social media and what the technology itself actually allows.

For elected officials and city managers, privacy concerns deserve careful consideration. The key question is whether those concerns accurately reflect how modern LPR systems are designed, governed, and used in practice.

The Privacy Debate Often Starts With The Wrong Assumption

Many public discussions begin with an assumption that all LPR systems work the same way: cameras collect data, agencies share it broadly, and officers can search whatever they want.

That may make for a compelling public meeting narrative or news story, but it is not an accurate description of how today's leading systems operate.

The questions local governments should be asking are much more specific:

• Who controls data sharing?
• What searches are allowed?
• What searches are prohibited?
• Who can see audit records?
• How is public accountability maintained?
  ‍

The answers to those questions determine whether an LPR deployment is privacy-forward or privacy-risky.

Data Sharing Is Not Automatic

One of the most common misconceptions is that every participating agency automatically gains access to every piece of data collected across a network.

In reality, responsible LPR networks, like the Flock system, are built around agency control.

Each agency determines what information it shares and with whom. Participation in a larger network does not require unrestricted access to local data.

That distinction is important for policymakers because it means local governments retain authority over how their community's information is handled. Sharing is not something that happens to an agency. It is a decision made by the agency.

When evaluating any technology proposal, councils should understand whether data sharing is automatic, mandatory, or controlled by the agency itself.

Those differences have significant privacy implications.

Privacy Is About What Users Cannot Do

Many technology presentations focus on capabilities.

The more important question for public trust is limitations:

• What actions are blocked?
• What safeguards are enforced?
• What behavior is prohibited by design?
  
  

A privacy-forward LPR platform, like Flock, should not simply tell users to follow policy. It should help enforce policy.

That includes preventing searches that fall outside approved investigative purposes and creating accountability when searches occur.

The strongest privacy protections are often the ones the public never sees because they operate in the background, restricting inappropriate use before it happens.

For local governments, this is a critical distinction. Effective privacy protection starts with the architecture itself.

Transparency Must Be Paramount

Every council member knows that public trust can disappear quickly.

That's why transparency is no longer optional.

Residents rightfully expect to know how technology is being used, who has access, and what safeguards exist to prevent misuse.

The most effective approach is not asking the public to simply trust the technology. It provides visibility into how the technology operates.

Transparency tools allow communities to see policies, understand governance practices, and evaluate oversight measures for themselves.

That changes the conversation from speculation to evidence.

Instead of debating hypothetical misuse, councils can point to documented safeguards, published policies, and clear accountability mechanisms.

What are the questions every council should ask?

When evaluating any public safety technology, councils should ask a simple question:

If a resident raises a privacy concern six months from now, what evidence will we be able to show them?

Can you demonstrate who searched the system?

Can you explain what searches are allowed?

Can you show how inappropriate use is prevented?

Can you point to public-facing transparency resources?

Can you prove that local agencies retain control over sharing decisions?

If the answer is yes, you are relying on governance that ultimately protects both communities and elected officials.

The Decision Is Bigger Than Technology

For city councils, this is a decision about outcomes and trust.

Communities expect public safety programs to be effective, transparent, and accountable. That confidence comes from clear policies, strong oversight, and privacy protections built directly into the system, creating a foundation that can withstand public scrutiny over time.

As LPR discussions continue in council chambers across the country, officials should look beyond the claims made during a meeting and ask a more important question:

What does the system actually allow, prevent, and document?

When privacy safeguards are built into the architecture itself, public safety and public trust do not have to compete.

They reinforce each other.

‍

Photo credit:

1. The Climate Reality Project

2. Christina @ WOCinTech