{"resourceId":"mill-valley-suspends-flock-alpr-over-changed-terms-of-use-20261021","versions":[{"version":"external-38ae6ef545ea9c39acda6965bd19bbf3bfcd3f4c67aa824efb1481f75d0b44cf","resource":{"id":"mill-valley-suspends-flock-alpr-over-changed-terms-of-use-20261021","title":"Mill Valley, Calif., suspends Flock plate readers and live-feed cameras after the vendor changed its terms of use mid-contract","organization":"City of Mill Valley","sector":"Policing / ALPR vendor governance","geography":"Mill Valley, California, United States","publishedAt":"City statement posted Oct. 21, 2026","publicationDate":"2026-10-21","eventDate":"2026-09-09","sourceName":"City of Mill Valley","sourceLabel":"Statement on Automated License Plate Recognition (ALPR) Technology","sourceUrl":"https://www.cityofmillvalley.gov/m/NewsFlash/Home/Detail/1639","evidenceClass":"government-evaluation","outcomeClass":"cautionary","topics":["governance-procurement","data-security"],"finding":"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.","sledRelevance":"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":"Opened the City of Mill Valley news item and read the statement in full.","architectureImplications":"Settings such as statewide lookup sit in the vendor platform; the city wants verifiable technical safeguards over configuration and sharing.","governanceImplications":"Five evaluation priorities: access and sharing, retention, auditing, transparency and vendor accountability; any restart goes to council with public comment.","securityPrivacyImplications":"Emphasises preventing sharing prohibited by California law, including with out-of-state and federal agencies.","caveats":"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.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: the buying problem here is control, not features. Mill Valley had tight local settings and still suspended its system when vendor terms changed. Agencies renewing ALPR or camera contracts may want help writing enforceable data-control terms. A bounded engagement could be a contract and configuration review against a city’s privacy requirements. The evidence cannot support claims about ALPR effectiveness, and it reflects one small city’s position.","engineering":"Engineering framing: key settings such as statewide lookup and sharing lists live in the vendor platform, so policy depends on vendor configuration. Pre-sales should check whether an agency can verify settings independently, export audit logs and enforce retention technically. A proof of value could compare configured settings and sharing lists with the city’s written policy and test whether changes by the vendor would be detected.","delivery":"Delivery framing: work would include a regional requirements set (access, retention, audits, transparency, vendor accountability), vendor evaluation and contract terms, then a council and public review before any restart. Dependencies include county and neighbouring city coordination. The operational owner is the police department with the city attorney. Acceptance should be measured by contract clauses secured and audit evidence, and risks include delay and coverage gaps while cameras stay off."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Enforceable contract terms and independent verification could let a city keep ALPR under its own rules or exit cleanly.","potentialEngagement":"Contract and configuration review for one ALPR or camera program, ending in required clauses and an audit checklist.","unsupportedClaims":["ALPR effectiveness","That other vendors offer better terms","That Flock’s changes apply to all contracts"]},"engineering":{"fit":"Cities and counties renewing or re-procuring ALPR and live-feed cameras.","architectureIntegration":"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.","proofOfValue":["Proposed: reconcile platform sharing lists with signed MOUs","Proposed: test whether a vendor-side setting change triggers an alert to the city"]},"delivery":{"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","skillsAdoption":"Train staff on audit procedures and configuration checks.","governanceCheckpoints":["Council review in February 2027","Public comment on any restart","Recurring access audits"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-25T02:58:06Z","enrichedAt":"2026-10-25T03:02:27Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Limited relevance.","procurementImplications":"Contract terms must give the city control over data, settings and sharing permissions; vendor-side term changes are treated as a material risk.","operatingModelImplications":"Moves from a single-city program to a coordinated county approach.","sourceVerification":{"openedUrl":"https://www.cityofmillvalley.gov/m/NewsFlash/Home/Detail/1639","referenceExcerpt":"Because the revised terms did not provide the enforceable protections the City requires, we suspended use of the Flock system.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}