# Jacksonville LPR Policy and Retention Settings Jacksonville Police Department Policy 10-28 became effective and was reviewed on 2024-11-11. It expressly covers "Motorola LPRs and AVA Quad Cameras with LPR detection" and governs fixed, mobile, and portable LPR systems (`JPD Policy 10-28 License Plate Readers.pdf`, p. 1). ## Administration and retained operational records The policy assigns an administrator responsibility for: > "Maintaining records identifying approved LPR deployments and and documenting their results, including appropriate documentation of significant incidents and arrests that are related to LPR usage." (p. 2) It also requires protocols to preserve alerts or hits acted on in the field or tied to investigations or prosecutions (p. 2). These requirements identify existing record categories; the production did not include deployment/result records or alert-disposition records. ## Alert verification and hot-list documentation Before an alert-based stop, the policy directs the officer to: > "Visually verify that the vehicle plate number matches the plate number run by the LPR system, including both alphanumeric characters of the license plate and the state of issuance." (p. 2) and: > "Verify the current status of the plate through dispatch or MDT query when circumstances allow." (p. 2) The policy further says users should record each alert/hit disposition and document the reason whenever a plate is manually entered into the LPR system (p. 2). ## Sharing and dissemination LPR data are treated as for official use only. When disseminated outside the agency, the policy says the disclosure "should be documented in a secondary dissemination log" (p. 2). The production did not include that log. ## Retention Policy 10-28 sets an outer limit: > "All LPR system data will be stored on the designated LPR system server for a period not to exceed 150 days" (p. 3). It permits investigative preservation and requires destruction at the conclusion of an investigation without charges or the resulting criminal action (p. 3). The produced platform settings are shorter: - `FLOCK Retention Information.png` says Flock's standard retention is **30 days**, with extended retention only when mandated by an elected official or legislative body. - `VM DATA STORAGE .pdf`, p. 1, displays deletion of both detection and hit data after **30 days**, plus 30-day hot-plate expiry/inactivity settings. - `PO- Flock Safety - Documents (003).pdf`, p. 2, states `Retention Period: 30 Days`. The policy's 150-day language is a ceiling, so the 30-day platform settings are not a contradiction. The screenshots establish configured values shown, not execution of each deletion. ## Open questions / follow-ups - Current and superseded policies for Flock/Wing, VehicleManager, integrated video, Jacksonville Safe, private-camera registration, auditing, misuse, and account termination. - Deployment/result records, alert/hit dispositions, manual hot-list reasons, secondary-dissemination logs, and retained audit reports required or contemplated by Policy 10-28. - Six-month ALPR reports prepared under Ark. Code Ann. § 12-12-1805. - Native retention configuration and deletion/audit exports for each platform.