Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Public Safety edition of September 22, 2026

Standards or public-body guidanceEmergingNew this fortnight

Missouri EO 26-18 sets statewide ALPR retention, audit logging, FR ban, and misuse penalties

Office of the Governor of Missouri / Missouri Secretary of State · State government / executive order · Missouri (state agencies and state-funded local law enforcement)

Publisher
Missouri Secretary of State — Governor's Executive Orders
Original publication
September 16, 2026
Source retrieved
2026-09-23
Event date
2026-09-16
Read original source

What happened

Governor Mike Kehoe’s Executive Order 26-18 (Sept. 16, 2026) directs Missouri state agencies and state-funded local law-enforcement entities using ALPR to meet interim minimum standards until permanent legislation: permanently delete captured plate/vehicle imagery within 30 days unless linked to an active criminal investigation, life-safety emergency, or court order; keep Missouri-generated ALPR data as exclusive government property and bar vendors from selling/sharing/commercializing it for non–law-enforcement purposes; require vendor written certification of the 30-day purge; limit access to criminal-justice and bona fide lifesaving purposes; prohibit integrating AI facial-recognition with ALPR to auto-screen faces; mandate every query log user identity plus a valid active case number or specific law-enforcement justification; and treat personal use, stalking, unauthorized sharing, or non–criminal-justice hot-list additions as grounds for discipline, criminal referral under §576.050 RSMo, and DPS officer-license action. DPS must issue best-practice guidance within 10 days and develop a legislative package covering guardrails, audits, a standalone misuse crime, and grant withholding for noncompliance.

Why it matters

Direct public-safety (policing) governance of ALPR networks used for stolen-vehicle recovery, missing persons, and investigative leads—not fire/EMS. Transferable model for other U.S. states wrestling with Flock-style multi-agency location databases, retention, FR add-ons, and misuse sanctions.

Evidence and measured results

Primary executive-order text hosted by the Missouri Secretary of State, effective immediately on Sept. 16, 2026. Corroborated by the Governor’s press release same day. No measured clearance-rate outcomes; this is a control framework, not an effectiveness study.

Limitations and uncertainty

Applies to state entities and state-funded locals “to the greatest extent permissible”; purely self-funded municipal systems may be outside direct EO reach. Permanent legislation and DPS guidance outcomes after the 10-day window are not yet observed here. No empirical evaluation of crime outcomes.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Missouri agencies using ALPR face statewide interim floors on retention, logging, FR integration, and misuse penalties without a finished statute yet.
Stakeholders
  • Missouri DPS Director
  • Police chiefs / sheriffs
  • City/county attorneys
  • City councils / privacy advocates
  • ALPR vendor contract managers
Discovery questions
  • Does the agency receive state funding that brings it under EO 26-18?
  • Can the vendor certify and enforce a 30-day purge today?
  • Are queries blocked without user ID + case number/justification?
  • Is any facial-recognition product integrated with ALPR feeds?
Value hypothesis
Bounded value is demonstrable compliance architecture and misuse-risk reduction—not proven investigative yield from the EO.
Potential engagement
3–5 week EO 26-18 readiness assessment: map funding scope, retention/logging gaps, FR integrations, and contract amendments.
Unsupported claims
  • Guaranteed crime reduction from ALPR under the EO
  • That the EO binds every purely locally funded camera
  • That written certifications alone stop vendor secondary use

Pre-sales engineering

Role takeaway
Fit
State-funded Missouri ALPR programs needing enforceable retention, purpose logging, and FR separation.
Architecture and integration
ALPR capture → 30-day TTL store → investigation-tag retain exception → query gate (user+case/justification) → immutable audit export; no FR face-screen pipeline on ALPR imagery.
Prerequisites
  • Inventory of ALPR systems and funding sources
  • CAD/RMS case-ID validation
  • Vendor contract amendment path
  • Hot-list change-control process
Constraints
  • EO coverage limited where no state funding
  • Vendor multi-tenant cloud UX
  • Active-investigation retention exceptions need careful tagging
Security
Least-privilege query roles; prohibit personal/stalking use; log and alert anomalous high-volume or out-of-policy searches; bar vendor commercialization of Missouri data.
Proof of value
  • Sampled queries 100% have user+case/justification
  • Non-investigation imagery deleted by day 30
  • No active FR auto-screen integration on ALPR

Delivery

Role takeaway
Work
Policy rewrite to EO floors, vendor negotiations, purge configuration, audit sampling, training, and DPS reporting hooks.
Dependencies
  • DPS best-practice guidance (10-day clock)
  • Vendor purge certification
  • Labor/discipline procedures
  • Prosecutors for §576.050 referrals
Ownership
Agency executive with professional standards co-owning misuse investigations; DPS for license actions.
Skills and adoption
Train officers on authorized criminal-justice/lifesaving purposes, case-linked logging, and personal-use prohibition with scenarios.
Governance checkpoints
  • Contract certification on file
  • First monthly justification audit
  • Hot-list addition review sample
  • DPS guidance incorporation checklist
Acceptance criteria
  • Configured 30-day purge with documented exceptions
  • Query UI enforces identity+justification
  • Written FR-integration prohibition
  • Misuse pathway documented to DPS
Risks
  • Municipal systems outside EO scope continue weak controls
  • Investigation tags used to evade purge
  • Logging theater without real sanctions

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 deployments serving Missouri state-funded agencies need configurable 30-day purge, case-linked query gates, immutable user+justification logs, contractual vendor non-commercialization clauses, and hard separation from facial-recognition face-screening pipelines.

Governance

Who approves, reviews and stays accountable for outcomes?

Moves ALPR from honor-system local policy to statewide interim floors with DPS guidance, planned statute, grant leverage, and license-revocation pathways—while acknowledging authority gaps for purely locally funded systems.

Security and privacy

What data, permissions and controls need testing?

Caps bulk location retention, asserts agency ownership against vendor secondary use, and elevates personal/stalking queries to criminal-referral territory—addressing continuous tracking of non-suspect drivers.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Officers need clear purpose categories and case-ID entry that work in mobile field conditions; professional standards need capacity to sample logs and pursue license referrals.

Procurement

What should contracts, pricing and exit terms secure?

New and renewed ALPR contracts must require 30-day deletion certification, government data ownership, ban on non–LE commercialization, and no FR face-screen integration—evaluate vendors on these clauses, not only camera density.

Operating model

Which teams own the service once it runs?

ALPR shifts from optional local policy to interim statewide operating floors with DPS guidance and planned grant-withholding leverage for noncompliance.

Publication history

  1. 2026-09-22Public Safety · Issue 164 resources
Read preserved resource versions (JSON)

Stable resource ID: missouri-eo-26-18-alpr-safeguards-20260916