From the Public Safety edition of October 24, 2026
Mill Valley, Calif., suspends Flock plate readers and live-feed cameras after the vendor changed its terms of use mid-contract
City of Mill Valley · Policing / ALPR vendor governance · Mill Valley, California, United States
- Publisher
- City of Mill Valley
- Original publication
- City statement posted Oct. 21, 2026
- Source retrieved
- 2026-10-25
- Event date
- 2026-09-09
What happened
In an Oct. 21 statement, Mill Valley said it suspended its Flock ALPR and live-feed cameras, disabled since Sept. 9, 2026, because Flock changed its terms of use midway through the contract and the revised terms did not give the city enforceable protections over data control and privacy. The city had already limited the program: no facial recognition, 72-hour retention for live-feed cameras and seven days for ALPR, regular access audits, statewide lookup disabled and sharing limited to a few California agencies under an MOU. It is working with Marin County and neighbouring cities on a coordinated approach that will consider other vendors, with priorities on access, retention, auditing, transparency and vendor accountability, and plans to return to council in February 2027. Regional coverage of the statement appeared Oct. 24.
Why it matters
Shows that strict local policy settings were not enough once vendor terms changed; the city now wants contract terms that give it, not the vendor, control of data, settings and sharing.
Evidence and measured results
Opened the City of Mill Valley news item and read the statement in full.
Limitations and uncertainty
City statement without crime or usage data; Flock’s position (an Aug. 21 blog post saying changes do not affect customers with a standalone signed agreement) appears only in secondary coverage, not the opened statement.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-25; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Cities with strict ALPR policies find vendor-controlled terms and settings can undermine those policies mid-contract.
- Stakeholders
- City managers and attorneys
- Police chiefs
- City councils
- County partners
- Privacy advocates
- Discovery questions
- Can the vendor change terms that affect your data without a signed amendment?
- Can you verify sharing and lookup settings yourself?
- What would a regional ALPR approach require of vendors?
- Value hypothesis
- Enforceable contract terms and independent verification could let a city keep ALPR under its own rules or exit cleanly.
- Potential engagement
- Contract and configuration review for one ALPR or camera program, ending in required clauses and an audit checklist.
- Unsupported claims
- ALPR effectiveness
- That other vendors offer better terms
- That Flock’s changes apply to all contracts
Pre-sales engineering
Role takeaway
- Fit
- Cities and counties renewing or re-procuring ALPR and live-feed cameras.
- Architecture and integration
- Vendor-hosted platforms hold sharing lists, lookup features and retention settings; agencies need audit log export and configuration visibility.
- Prerequisites
- Signed agreement terms
- Audit log access
- Data-sharing MOUs
- Constraints
- California law limits on sharing
- Vendor platform controls settings
- Regional coordination timelines
- Security
- Disable broad lookup features; restrict sharing to agencies under MOU; verify deletion at stated retention periods.
- Proof of value
- Proposed: reconcile platform sharing lists with signed MOUs
- Proposed: test whether a vendor-side setting change triggers an alert to the city
Delivery
Role takeaway
- Work
- Define regional requirements, evaluate vendors and negotiate contract terms before any restart.
- Dependencies
- County and neighbouring city coordination
- City attorney review
- Vendor responses
- Ownership
- Police department with the city attorney
- Skills and adoption
- Train staff on audit procedures and configuration checks.
- Governance checkpoints
- Council review in February 2027
- Public comment on any restart
- Recurring access audits
- Acceptance criteria
- Proposed: contract grants city control over data, settings and sharing
- Proposed: quarterly audit reports published
- Risks
- Extended camera outage
- Vendor refusal of terms
- Regional policy divergence
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?
Settings such as statewide lookup sit in the vendor platform; the city wants verifiable technical safeguards over configuration and sharing.
Governance
Who approves, reviews and stays accountable for outcomes?
Five evaluation priorities: access and sharing, retention, auditing, transparency and vendor accountability; any restart goes to council with public comment.
Security and privacy
What data, permissions and controls need testing?
Emphasises preventing sharing prohibited by California law, including with out-of-state and federal agencies.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Limited relevance.
Procurement
What should contracts, pricing and exit terms secure?
Contract terms must give the city control over data, settings and sharing permissions; vendor-side term changes are treated as a material risk.
Operating model
Which teams own the service once it runs?
Moves from a single-city program to a coordinated county approach.
Publication history
- 2026-10-24Public Safety · Issue 467 resources
Stable resource ID: mill-valley-suspends-flock-alpr-over-changed-terms-of-use-20261021