{"resourceId":"missouri-eo-26-18-alpr-safeguards-20260916","versions":[{"version":"external-a0dfc7cb8c3893f4cdd19beb93d3fe9ffa3899c004e4da38afe78060ecd90a2b","resource":{"id":"missouri-eo-26-18-alpr-safeguards-20260916","title":"Missouri EO 26-18 sets statewide ALPR retention, audit logging, FR ban, and misuse penalties","organization":"Office of the Governor of Missouri / Missouri Secretary of State","sector":"State government / executive order","geography":"Missouri (state agencies and state-funded local law enforcement)","publishedAt":"September 16, 2026","publicationDate":"2026-09-16","eventDate":"2026-09-16","sourceName":"Missouri Secretary of State — Governor's Executive Orders","sourceLabel":"Executive Order 26-18 primary text","sourceUrl":"https://www.sos.mo.gov/library/reference/orders/2026/eo18","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["governance-procurement","data-security","operating-model","infrastructure"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"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.","caveats":"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.","streamIds":["public-safety"],"roles":{"sales":"Sales framing: Missouri EO 26-18 is a statewide procurement-and-compliance signal for ALPR, not a vendor feature pitch. Position advisory work around 30-day retention, case-linked search logging, FR-integration bans, vendor non-commercialization clauses, and misuse-to-license pathways before camera expansion. Stakeholders are DPS, chiefs/sheriffs, city attorneys, councils, and FOP/prosecuting associations named in the order. Bound value to auditable compliance readiness; do not claim crime-clearance gains from the EO text itself.","engineering":"Engineering framing: treat ALPR SaaS as a regulated control plane. Enforce 30-day deletion except investigation-tagged retention, mandatory user+case/justification fields, exportable audit logs, and contractual blocks on vendor secondary use or FR face-screen add-ons. Prerequisites include written policy mapping to §43.500 RSMo criminal-justice purposes and hot-list governance. Proof of value is purge compliance and 100% logged justifications under DPS sampling—not faster plate lookups alone.","delivery":"Delivery framing: stand up DPS-aligned SOP, vendor contract amendments, monthly justification audits, discipline/criminal-referral workflows, and officer training within the interim EO window. Dependencies include DPS 10-day guidance, vendor certification letters, RMS/CAD case IDs, and clarity on which agencies receive state funding (EO scope). Ownership should sit with agency heads with DPS reporting for license actions. Risks include uneven municipal coverage for non–state-funded systems and checkbox logging that fails to stop misuse."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Bounded value is demonstrable compliance architecture and misuse-risk reduction—not proven investigative yield from the EO.","potentialEngagement":"3–5 week EO 26-18 readiness assessment: map funding scope, retention/logging gaps, FR integrations, and contract amendments.","unsupportedClaims":["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"]},"engineering":{"fit":"State-funded Missouri ALPR programs needing enforceable retention, purpose logging, and FR separation.","architectureIntegration":"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.","proofOfValue":["Sampled queries 100% have user+case/justification","Non-investigation imagery deleted by day 30","No active FR auto-screen integration on ALPR"]},"delivery":{"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.","skillsAdoption":"Train officers on authorized criminal-justice/lifesaving purposes, case-linked logging, and personal-use prohibition with scenarios.","governanceCheckpoints":["Contract certification on file","First monthly justification audit","Hot-list addition review sample","DPS guidance incorporation checklist"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-09-23T03:16:40Z","enrichedAt":"2026-09-23T03:16:40Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"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.","procurementImplications":"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.","operatingModelImplications":"ALPR shifts from optional local policy to interim statewide operating floors with DPS guidance and planned grant-withholding leverage for noncompliance.","sourceVerification":{"openedUrl":"https://www.sos.mo.gov/library/reference/orders/2026/eo18","referenceExcerpt":"ensure the permanent deletion of all captured license plate and vehicle images within 30 days of collection.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}