From the Public Safety edition of October 3, 2026
Marshall Project: ALPR backlash brings Missouri purpose/audit/30-day rules, Florida state-road ban, and Flock claim walk-back
The Marshall Project · Policing / ALPR surveillance · United States — Missouri, Florida, multi-state (Flock ALPR networks)
- Publisher
- The Marshall Project
- Original publication
- 3 October 2026
- Source retrieved
- 2026-10-04
- Event date
- 2026-10-01
What happened
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.
Why it matters
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 and measured results
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.
Limitations and uncertainty
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.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- A controls-first ALPR operating model can preserve legitimate investigative use while cutting unauthorized-search and political-cancellation risk.
- Potential engagement
- 2–4 week ALPR governance readiness review mapping purpose, audit, retention, and FR-ban controls to current vendor configs.
- Unsupported claims
- Guaranteed vehicle-theft reductions from ALPR
- Vendor solve-count marketing as causal crime clearance
- That monthly audits alone stop determined misuse
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies already on Flock/Axon/Motorola ALPR that must add purpose binding and auditability under new state rules.
- Architecture and integration
- 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.
- Proof of value
- 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
Role takeaway
- 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.
- Skills and adoption
- Train supervisors on junk-string detection and misuse escalation; brief line officers on legitimate-purpose examples.
- Governance checkpoints
- pre-expansion policy attestation
- first monthly audit readout
- post-retention-change investigative impact review
- Acceptance criteria
- 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
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?
Treat ALPR as a searchable movement graph with purpose-coded queries, immutable audit logs, and retention timers—not a passive plate camera overlay.
Governance
Who approves, reviews and stays accountable for outcomes?
Codify legitimate-purpose entry, monthly audit sampling, and junk-string detection before expanding sharing; convert EO/guidance into enforceable policy with discipline paths.
Security and privacy
What data, permissions and controls need testing?
Short retention and bans on FR integration reduce stalking and secondary-use risk but shrink cold-case windows; document tradeoffs explicitly.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Supervisors need plain-language purpose guidance so audits are usable by non-technical command staff and civilian oversight boards.
Procurement
What should contracts, pricing and exit terms secure?
Write purpose/audit/retention/FR-ban and claim-definition (investigations supported vs crimes solved) into renewals before adding cameras.
Operating model
Which teams own the service once it runs?
Shift from coverage growth to governed query operations with monthly compliance reporting to executives.
Publication history
- 2026-10-03Public Safety · Issue 264 resources
Stable resource ID: marshall-flock-alpr-backlash-20261003