Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Police Technology topic
No spam. Unsubscribe anytime.
Meridian police outline Axon ALPR deployment, retention, and audit controls
Summary
Police Chief Chatham presented Meridian PD’s Axon automatic license plate reader (ALPR) deployment, saying data are owned by the city, retention was reduced from 60 to 30 days, opt-in training is off by default, and the department is building auditing and access‑control guardrails; council pressed on false positives, public dashboards, and third‑party review.
Get email alerts on the Police Technology topic
No spam. Unsubscribe anytime.
Meridian Police Chief Chatham told the city council on July 21 that the department controls and owns the data collected by its Axon automatic license plate readers (ALPRs), that data are retained per department policy (recently moved from a 60-day retention to 30 days), and that third-party access is limited and logged. The chief said Axon holds FedRAMP High authorization for the federal cloud environment used for evidence storage and that audit logs are immutable: “We own the data,” he said. “No 3rd party controls our data.”
Chief Chatham and staff described the system’s features: fixed Outpost cameras in public locations and mobile Fleet 3 cameras in patrol vehicles; a hot-list mechanism to alert officers to vehicles of interest; and manual confirmation requirements so officers must visually verify a plate and vehicle before making contact. He said opt-in data sharing for vendor training is off by default and — even if enabled — provides only partial plate reads for model training, not full plate data.
Council members asked how misuse would be detected and what auditing functions exist. Councilwoman Streator and others asked about random auditing and independent review; chief and support staff said Meridian runs more frequent audits than the state’s semiannual minimum, records case/incident numbers on searches, maintains reviewer gatekeepers and weekly reviews, and is exploring MOUs and public dashboards. “If we see searches without case numbers or excessive repeated searches of a single plate, those are red flags,” the chief said. Lieutenant Frazier and other staff explained audit tools and internal controls.
Councilmembers also raised operational questions: false positives and traffic stops, how citizens obtain redress, and how many plates are active on the hot list. The chief said there have been many false positives but no known incorrect arrests tied to ALPR hits; he described typical stop procedures and backup verification through dispatch and the real-time support center. The department said roughly 50 plates are active on its hot list at any one time and that supervisors and RTSC staff control who may add plates.
The presentation ended with council praise for the department’s safeguards and an invitation to return with follow-up on drones and audit enhancements in the fall. Council did not take formal regulatory action at the meeting; staff said they plan an early-fall follow-up.

