{"resourceId":"marshall-flock-alpr-backlash-20261003","versions":[{"version":"external-659e5eaf9d5d199a2600984022ee287ee92229222d33f763e3fadef811e07c3f","resource":{"id":"marshall-flock-alpr-backlash-20261003","title":"Marshall Project: ALPR backlash brings Missouri purpose/audit/30-day rules, Florida state-road ban, and Flock claim walk-back","organization":"The Marshall Project","sector":"Policing / ALPR surveillance","geography":"United States — Missouri, Florida, multi-state (Flock ALPR networks)","publishedAt":"3 October 2026","publicationDate":"2026-10-03","eventDate":"2026-10-01","sourceName":"The Marshall Project","sourceLabel":"Independent criminal-justice journalism synthesizing state ALPR rules and outcome claims","sourceUrl":"https://www.themarshallproject.org/2026/10/03/police-camera-traffic-flock-protest","evidenceClass":"independent-reporting","outcomeClass":"mixed","topics":["governance-procurement","data-security","operating-model","infrastructure"],"finding":"On 3 October 2026 Jamiles Lartey reported that Missouri agencies got new ALPR rules requiring a stated legitimate search purpose, monthly audits, and deletion of non-investigative records within 30 days (tied to Gov. Kehoe’s EO framework), while Florida’s state-road ALPR installation ban took effect the same week. The piece documents audit workarounds (e.g., Maricopa deputies entering junk case-number strings), vendor retention cut from 30 to 7 days, 247 IJ-tallied full ALPR cancellations, and—after CBS scrutiny—Flock revising a “solve more than one million crimes” claim to “supported approximately one million investigations and incidents.” Auto-theft outcome studies are described as mixed once pre-trends are considered.","sledRelevance":"Same-week U.S. signal that AI-enabled ALPR networks are entering a governance reset: purpose binding, audits, retention, and claim discipline now matter as much as camera counts for SLED buyers.","evidence":"Opened Marshall Project HTTPS article via WebFetch after curl received Cloudflare 403; recorded retrieval 2026-10-04T02:51:01Z; verified Missouri rules, Florida ban, 247 cancellations, and Flock wording revision against page text.","architectureImplications":"Treat ALPR as a searchable movement graph with purpose-coded queries, immutable audit logs, and retention timers—not a passive plate camera overlay.","governanceImplications":"Codify legitimate-purpose entry, monthly audit sampling, and junk-string detection before expanding sharing; convert EO/guidance into enforceable policy with discipline paths.","securityPrivacyImplications":"Short retention and bans on FR integration reduce stalking and secondary-use risk but shrink cold-case windows; document tradeoffs explicitly.","caveats":"National synthesis citing secondary reporting and vendor statements; does not publish a new RCT; Missouri DPS guidance details come via the article’s Wednesday-rules framing rather than a separate opened DPS PDF.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: agencies buying or renewing AI-enabled ALPR are under bipartisan political heat, so lead with enforceable purpose, audit, and retention controls—not coverage maps. Missouri’s legitimate-purpose plus monthly-audit plus 30-day deletion package and Florida’s state-road ban show procurement risk is now legislative and gubernatorial, not only activist. Use the Flock “one million crimes” walk-back after CBS scrutiny to reset ROI conversations toward investigatory-support metrics. Offer a bounded policy-and-controls readiness engagement before camera expansion. Do not promise theft-rate drops the mixed auto-theft literature cannot support.","engineering":"Engineering framing: ALPR value hinges on query governance plumbing—required purpose codes, case-number validation that rejects junk strings like those found in Maricopa, monthly audit exports, and retention jobs that purge non-case data. Integrate FR-off flags if policy bans AI face overlays on plate systems. Proof points should include audit completeness rates and false-lead rates, not vendor solve-count marketing after the million-crimes revision. Hybrid on-prem/cloud designs must still produce jurisdiction-owned logs when vendors shorten retention to seven days.","delivery":"Delivery framing: stand up purpose taxonomy, auditor workflows, and exception handling for seven- versus thirty-day retention before go-live expansion. Ownership sits with records/compliance plus investigations command; train supervisors to sample searches monthly and escalate misuse. Acceptance criteria: ≥95% searches with non-junk purpose/case fields; documented purge of non-investigative records inside policy windows; no FR feature flags enabled where banned. Risks include officers bypassing fields, vendor national-share surprises, and investigative pushback when retention shrinks."},"roleDetails":{"sales":{"customerProblem":"ALPR deployments face rapid state/federal rule churn and public backlash while crime-outcome claims are contested.","stakeholders":["police executives","city/county counsel","state DPS/POST","elected executives","civil liberties monitors"],"discoveryQuestions":["What purpose codes and audit cadence are written into policy today?","How do you measure investigatory support versus solved crimes?","What happens if state roads or state funds ban or condition ALPR?"],"valueHypothesis":"A controls-first ALPR operating model can preserve legitimate investigative use while cutting unauthorized-search and political-cancellation risk.","potentialEngagement":"2–4 week ALPR governance readiness review mapping purpose, audit, retention, and FR-ban controls to current vendor configs.","unsupportedClaims":["Guaranteed vehicle-theft reductions from ALPR","Vendor solve-count marketing as causal crime clearance","That monthly audits alone stop determined misuse"]},"engineering":{"fit":"Fits agencies already on Flock/Axon/Motorola ALPR that must add purpose binding and auditability under new state rules.","architectureIntegration":"Insert mandatory purpose/case metadata at query time; stream immutable audit events to agency SIEM; configure retention timers and FR-off.","prerequisites":["written ALPR policy","identity-bound officer accounts","exportable audit API or reports","records retention schedule"],"constraints":["vendor national network sharing may exceed local policy","seven-day vendor retention vs local investigative timelines","junk free-text purpose fields without validation"],"security":"Encrypt queries/results in transit; least-privilege roles; alert on anomalous search volume or romantic/personal contact patterns.","proofOfValue":["percent searches with validated purpose/case fields","monthly audit completion with sampled anomalies","unauthorized-access incidents detected via logs","no enabled FR on ALPR feeds where prohibited"]},"delivery":{"work":"Configure purpose taxonomy and validation, stand up monthly audit SOP, test retention purge, document FR-ban compliance.","dependencies":["vendor admin access","legal sign-off on purpose list","internal affairs/compliance auditor assignment"],"ownership":"Investigations commander owns use policy; records/compliance owns audits and retention evidence.","skillsAdoption":"Train supervisors on junk-string detection and misuse escalation; brief line officers on legitimate-purpose examples.","governanceCheckpoints":["pre-expansion policy attestation","first monthly audit readout","post-retention-change investigative impact review"],"acceptanceCriteria":["non-junk purpose/case on ≥95% sampled searches","documented 30-day (or stricter) purge for non-case data","FR integration disabled and verified"],"risks":["audit theater with weak sampling","vendor claim inflation","public cancellation despite controls","investigators losing cold leads under short retention"]}},"retrievedAt":"2026-10-04T02:51:01Z","enrichedAt":"2026-10-04T02:51:01Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Supervisors need plain-language purpose guidance so audits are usable by non-technical command staff and civilian oversight boards.","procurementImplications":"Write purpose/audit/retention/FR-ban and claim-definition (investigations supported vs crimes solved) into renewals before adding cameras.","operatingModelImplications":"Shift from coverage growth to governed query operations with monthly compliance reporting to executives.","sourceVerification":{"openedUrl":"https://www.themarshallproject.org/2026/10/03/police-camera-traffic-flock-protest","referenceExcerpt":"Officers must state a “legitimate purpose” for searching databases, agencies are required to audit searches monthly","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}