Flock Cameras in Reno: a Growing Crisis of Public Trust

With increasing awareness of Flock’s failures and threat to privacy people in Reno are protesting and want the cameras to be gone. Here’s a look at why.

Michael Leonard

A Surveillance System Becomes a Political Flashpoint

Reno’s adoption of Flock automated license‑plate readers (ALPRs) was quiet at first — a line item in a public‑safety budget, a promise of “modern tools” to help solve crimes, and a technology already spreading across thousands of U.S. cities.

In 2026, national reporting on Flock’s failures collided with Reno’s political climate, turning the cameras from a technical procurement into a full‑blown civic controversy.

Residents now raise the issue at council meetings. Neighborhood groups debate it. The mayoral candidates were forced to address it on stage. Public mood has shifted from curiosity to alarm.

Reno’s situation is volatile because people’s skepticism of opaque spending, sensitivity to civil‑liberties issues, and growing distrust of policing make Flock’s problems a civic crisis.

Flock cameras are everywhere in Reno. The police are watching where you go.

How Flock Cameras Work

Flock’s ALPR system captures passing vehicles, reads license plates using AI‑learning models, and logs metadata such as:

  • make and model

  • color

  • distinguishing features

  • timestamps and location

When a plate matches a “Hot List” entry — stolen vehicle, felony suspect, Amber Alert — the system sends an alert to police.

In theory, this is a neutral investigative tool. In practice, the system’s accuracy and the way police use it have produced serious failures nationwide.

The National Evidence: A Pattern of Misreads and Misuse

The Business Insider investigation revealed a staggering statistic from Roseville, California:

“71% of all Flock alerts flagging a vehicle as stolen or connected to a felony contained a misread license plate.”

That’s not a rounding error — it’s a systemic failure. And it’s not isolated.

Documented national cases include:

  • Toledo, Ohio: A misread “7” as a “2” led to a violent felony stop, a K‑9 attack, hospitalization, jail time, and dismissed charges.

  • Suwanee, Georgia: A disabled Army veteran was arrested on a cruise ship after Flock mislabeled his beige Audi as white, triggering a wrongful felony warrant.

  • Florida: A woman jailed for two weeks after Flock misidentified her vehicle in a fatal hit‑and‑run; her car had no damage.

The cases have a common pattern: Flock makes an error → police don’t check the data → innocent people are arrested.

Reno’s Adoption of Flock: What We Know

Reno installed Flock cameras as part of a broader effort to modernize policing and reduce auto theft. The city has not publicly released detailed accuracy data, nor has it published a verification policy outlining how officers must confirm alerts before initiating stops. This lack of transparency is now a central point of public frustration.

Key questions Reno residents are asking:

  • What is the misread rate for Reno’s cameras?

  • How often do Flock alerts lead to stops?

  • Does Reno PD require visual verification before acting?

  • How long is vehicle data stored?

  • Who has access to the data — local police, regional agencies, federal partners, private companies?

  • What oversight exists?

These questions remain unanswered.

People in Reno have been de-Flocking the poles in protest, as with this one by the Eddy.

Public Backlash: Why Reno Residents Are Angry

The backlash in Reno mirrors the national pattern but is amplified by local dynamics.

1. Fear of wrongful stops

Residents have seen the national cases and worry: Could this happen here? Reno’s diverse neighborhoods — from Midtown to North Valleys — include many people who already feel over‑policed.

2. Distrust of automated policing

Reno has a long memory of controversial policing incidents. Flock feels like a step toward “policing by machine,” which many residents reject.

3. Civil‑liberties concerns

The Fourth Amendment argument is gaining traction: Should the government track every vehicle, everywhere, without a warrant?

4. Political frustration

Residents feel blindsided — the cameras appeared without robust public debate. Now that the public is aware, they want the contract reconsidered.

5. Retail involvement

National reporting shows Lowe’s and Home Depot using Flock cameras. Reno residents are now asking whether local retailers are participating in surveillance without public oversight.

Link: Backlash grows in Reno area as AI license plate reader and surveillance camera numbers increase

The Mayoral Debate: Flock Becomes a Symbol

In Reno’s mayoral debate, Flock cameras became a proxy for larger issues:

  • trust in police

  • transparency in city contracts

  • civil liberties

  • responsible use of technology

  • oversight of private vendors in public safety

Candidates were pressed to explain whether they support continuing the contract, modifying it, or ending it. The fact that ALPRs reached this level of political prominence shows how deeply the issue resonates with voters.

The Accountability Gap: Who Is Responsible When Flock Gets It Wrong?

One of the most troubling aspects of Flock’s business model is its liability structure.

Flock’s stance: Alerts are “investigative leads,” not proof. Police must verify.

Police departments’ stance: The system is accurate and helpful; errors are rare.

Victims’ reality: When mistakes happen, they suffer, and taxpayers pay the settlements.

This accountability vacuum is driving much of the public anger in Reno.

Residents want to know:

  • If a misread leads to a wrongful stop, who pays?

  • If a warrant is issued based on bad data, who is disciplined?

  • If the system misidentifies a vehicle, who fixes the underlying model?

Right now, the answers are unclear.

Link: Reno police chief addresses Flock camera concerns

The Policy Options Facing Reno

Reno City Council now faces three paths — each with consequences.

Option 1: Keep the Flock contract

This requires:

  • publishing accuracy data

  • enforcing strict verification policies

  • creating oversight mechanisms

  • addressing civil‑liberties concerns

Option 2: End the contract

This requires:

  • explaining the initial adoption

  • addressing public‑safety concerns

  • identifying alternative tools

  • managing political fallout

Option 3: Replace Flock with another vendor

This is the hidden danger. Many ALPR vendors (Axon, Motorola, Rekor) offer facial recognition, which would dramatically escalate the controversy.

Residents are already warning: “Dropping Flock means dropping all ALPRs.”

What Reno Should Do Next

Based on national evidence and local sentiment, Reno needs:

1. Full transparency

Publish:

  • misread rates

  • number of alerts

  • number of stops

  • verification policies

  • data‑sharing agreements

2. Independent auditing

Reno should not rely on Flock’s internal accuracy claims.

3. Civil‑liberties review

The city must evaluate:

  • warrant requirements

  • retention periods

  • access controls

  • use by private retailers

4. Public engagement

Residents deserve a say in whether mass vehicle surveillance is acceptable in their city.

5. Clear accountability

If a misread leads to harm, responsibility must be defined — not deflected.

Conclusion: Reno at a Crossroads

Flock cameras were sold as a simple safety upgrade. But the national reporting, the local backlash, and the political debate show that Reno is confronting something much larger:

What kind of city do we want to be? One that embraces automated surveillance, or one that demands accountability, accuracy, and civil liberties?

Do you have a story to tell? Write to me at: mike@mikesrenoreport.com

Support Reno independent journalism. Click to donate: Mike’s Reno Report.

Next
Next

Schieve Says That Reno Is Booming. So Why Doesn’t It Feel Like It?