From the Public Safety edition of November 6, 2026
Fresno will not renew Flock Safety ALPR contract after misuse and sharing concerns; city will seek another vendor and a citywide ordinance
City of Fresno / Fresno Police Department · Policing / automated license plate readers and vendor oversight · Fresno, California, United States
- Publisher
- Fresno Bee
- Original publication
- Fresno Bee, Nov. 6, 2026; also covered by KMPH FOX26 same day
- Source retrieved
- 2026-11-07
- Event date
- 2026-11-06
What happened
On Nov. 6, 2026 Fresno Mayor Jerry Dyer announced the city will not renew its Flock Safety ALPR service contract when it expires in February, citing ineffective safeguards despite vendor modifications, while keeping city-owned cameras and seeking another vendor with stronger safeguards for likely December council approval. Police Chief Mindy Casto said more than 70 fixed readers helped solve 42 shootings and 16 murders from January–October 2026 (agency-claimed, uncontrolled). A review found out-of-state agencies had accessed Fresno Flock data despite sharing settings, including “immigration” as a search reason, though officials said they found no ICE searches and could not determine whether access came from a department setting or a Flock change. An officer is under investigation for alleged non-investigative abuse. Councilmember Nick Richardson plans a citywide ordinance with search-record, 30-day retention and oversight rules. The three-year Flock contract cost about $1.5 million via a state Organized Retail Theft Prevention Grant. Flock said audit assistance, case-code requirements by end-2026, and proactive lockouts are coming.
Why it matters
A major California city is ending a Flock service relationship over misuse and cross-agency access doubts while still buying ALPR capability—useful for SLED buyers comparing vendor lock-in, audit controls and ordinance design.
Evidence and measured results
Opened the Fresno Bee article via WebFetch after curl to the origin failed/timed out; saved full article text. Corroborated with the same-day KMPH FOX26 local report opened via HTTPS curl (User-Agent SLED-research-bot/1.0) and converted to text. Key figures and quotes matched across both accounts.
Limitations and uncertainty
Crime-reduction attribution is agency-claimed and uncontrolled; Fresno Bee page blocked direct curl so text came via WebFetch; replacement vendor unnamed; officer investigation details withheld.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- City must keep ALPR value while ending a vendor relationship after misuse and sharing failures.
- Stakeholders
- Mayor
- Police chief
- City council
- City attorney
- Discovery questions
- What sharing settings are actually enforced?
- Can we audit out-of-state access?
- What ordinance survives the next chief?
- Value hypothesis
- A recompete tied to ordinance controls can reduce misuse risk without abandoning plates.
- Potential engagement
- ALPR vendor safeguard comparison and ordinance checklist.
- Unsupported claims
- That cameras caused the crime drop
- That Flock alone is unsafe
- That ICE never accessed data
Pre-sales engineering
Role takeaway
- Fit
- Relevant to agencies running fixed ALPRs with multi-agency sharing.
- Architecture and integration
- Case-code gate, audit export, sharing ACL, retention delete jobs.
- Prerequisites
- Asset inventory
- Policy
- IA access to logs
- Constraints
- Grant funding
- Vendor lock-in
- California sharing law
- Security
- Block unauthorized sharing; lock abnormal searches; investigate insider abuse.
- Proof of value
- Audit sample of searches
- Unauthorized search blocked
- Retention purge verified
Delivery
Role takeaway
- Work
- Non-renew Flock service; RFP successor; pass citywide ordinance; finish officer probe.
- Dependencies
- Council
- Counsel
- Grant admin
- Successor vendor
- Ownership
- Mayor and police chief with council ordinance lead.
- Skills and adoption
- Officers need case-number discipline on the new console.
- Governance checkpoints
- Ordinance introduced
- RFP scored on audits
- First post-cutover audit
- Acceptance criteria
- Flock not renewed
- Successor under ordinance
- Misuse case closed or charged
- Risks
- Service gap
- Weaker next vendor
- Political reversal
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
ALPR networks need enforceable sharing defaults, case-code gates and exportable audit trails that survive vendor swaps.
Governance
Who approves, reviews and stays accountable for outcomes?
Cities can separate camera hardware ownership from vendor software and require council-approved ordinances before the next contract.
Security and privacy
What data, permissions and controls need testing?
Out-of-state “immigration” labeled searches and an officer-misuse probe show sharing and insider-abuse risks even with policy bans on ICE sharing.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Chiefs still frame ALPRs as a staffing/crime-reduction tool; outcome claims need independent verification.
Procurement
What should contracts, pricing and exit terms secure?
Non-renewal mid-grant cycle forces a recompete on safeguards, not only price; demand lockout and audit features in writing.
Operating model
Which teams own the service once it runs?
Keep investigative use while changing the console operator; publish how hits map to case numbers.
Publication history
- 2026-11-06Public Safety · Issue 615 resources
Stable resource ID: fresno-nonrenew-flock-alpr-seek-new-vendor-misuse-safeguards-20261106