# Van Buren License Plate Reader Policy Policy 2.36 was implemented and revised 2023-07-01 and reviewed 2025-06-16. It names Chief [[Jonathan Wear]] as authority and governs fixed, mobile, or portable LPR systems and their data. ## Search and alert controls The policy limits LPR systems and associated databases to official public-safety purposes (`Policy 2.36 License Plate Readers.pdf`, p. 1). For historical searches: > `"All searched must include a case number or reason for the search."` It then requires: > `"A log of searched data shall be retained"` and includes all searches in the report described later in the policy (`Policy 2.36 License Plate Readers.pdf`, p. 4). The policy also says an alert alone is not sufficient probable cause for arrest, directs users to record alert/hit dispositions, and requires a documented reason for a manually entered plate (`Policy 2.36 License Plate Readers.pdf`, p. 4). ## Sharing and secondary dissemination When LPR data is sent outside the department or cooperating agencies sharing under an existing MOU, the policy requires a Secondary Dissemination Log showing: > `"what was shared, why it was shared, and when and who authorized the sharing"` (`Policy 2.36 License Plate Readers.pdf`, p. 4). The policy identifies an MOU-based sharing category but does not supply Van Buren's actual MOUs, organization list, sharing topology, or dissemination log. ## Six-month public report The System Administrator must compile statistical data every six months, present the report to the chief, preserve it for eighteen months, and format it for public review. Required fields are: - Number of plates scanned. - Names of lists checked. - Confirmed matches. - Matches that did not correlate to an alert after investigation. - Matches resulting in arrest and prosecution. (`Policy 2.36 License Plate Readers.pdf`, p. 5.) No such report appears in this rolling production. ## Retention The policy concludes: > `"Absent a specific schedule, LPR system data, related records, and logs shall be purged after 30 days."` (`Policy 2.36 License Plate Readers.pdf`, p. 5.) The phrase `"Absent a specific schedule"` leaves open whether any Van Buren data class has a different configured period. No Flock retention screenshot or administrator export appears in this package. ## Open questions - The current administrator designation, approved users, deployments, training, and use protocols. - Native search and audit logs, alert dispositions, hot-list entries, and manual-plate reasons. - Six-month reports and the records used to compile them. - MOUs, SharedNetworks exports, direct-access users, sharing directions, and Secondary Dissemination Logs. - Actual configured retention and purge records for reads, images, searches, alerts, logs, and preserved evidence.