# CPD Policy 800-32 — License Plate Reader Vehicle Operations The **governing internal policy** for Conway Police Department's use of license-plate reader (LPR) systems. Effective Aug 30, 2013. Most recent surfaced revision: R3, 1/18/2023, approved as "Chief of Police" by **William Tapley**. Four pages, embedded as an attachment in the 2025-01-23 Flock onboarding email chain. The policy sets the local rules every Conway-side data point in the investigation operates inside. ## Definition Per the policy itself, four operational concepts: - **LPR** — "Automated license plate reader with fixed cameras." - **LPR System** — "The LPR and all associated equipment and databases." - **Hot List** — "Any database that contains lists of license plate numbers that are of interest to police personnel, such as those associated with vehicles and/or license plates that have been stolen, wanted for specific crimes, or those that are associated with, or may assist with the identification of, suspects involved in criminal activity. This will also include data held by the Office of Motor Vehicles, the Arkansas Crime Information Center including without limitation the Arkansas Crime Information Center's Missing Persons database, the National Crime Information Center, and the Federal Bureau of Investigation Kidnapping and Missing Persons database." - **LPR Data** — "Data obtained by an LPR from license plates that were read by the device, including potential images of the plate and the vehicle on which it is displayed, the date and time, and information regarding the location of the police vehicle in which the LPR is installed, and any other data captured by or derived from any automatic license plate reader system, and, which may be stored on the department's computer servers." - **Hit** — "LPR read matched to a license plate that has previously been uploaded on a departmental 'Hot List'." ## Key operational rules **Section A — General:** - Only authorized LPR systems owned or provided by the department. - LPR used only by trained members. **Section B — Equipment:** - Qualified personnel install/remove. - Malfunctions reported to LPR supervisor + IT. - Permanently mounted cameras inspected monthly by LPR supervisor. **Section C — Operation:** - Used during patrol / special operations / investigations as approved by Chief. - Officer must visually verify a hit before action. - For permanent (fixed) camera hits, dispatch relays to on-duty officers. - LPR supervisor notified by email when enforcement action results from an LPR hit (statistical purposes). **Section D — Data:** - **Retention: 150 days max on fixed LPRs or server, "in accordance with State Law," then automatically purged.** - Hit data used in case files retained until "no longer needed." - **Semi-annual statistical report** by LPR supervisor to Patrol Administration Office, kept 18 months, **public on request.** Required fields: plates scanned, hot list names, per-list confirmed matches, non-correlations, arrests-and-prosecutions. - **Access restricted** to Chief-authorized, username/password-issued members; for criminal justice reasons only. - **Data sharing** with other LE agencies "if evidence of an offense is indicated." ## How it appears in the corpus - Attached to the 2025-01-23 Melissa Lee onboarding request (see [[AR - Conway PD - Welcome to Flock!]]). Burningham sends it on her request as the agency's LPR policy. - The semi-annual reporting requirement (Section D.2) is the predicate for [[LPR Report First Half 2025]] — the only such report surfaced in the production. - The 150-day retention is the **policy ceiling**; the Flock platform's product-default retention of 30 days ([[Flock Safety Order Form and Contract]]) is well below. - The "evidence of an offense is indicated" sharing standard (Section D.4) is **narrower** than the actual sharing pattern the corpus documents (default-on national network, federal-LE access without per-query predicate). This is an open research question: how does the contract-default 1,384-network sharing topology reconcile with a policy that limits sharing to "evidence of an offense"? ## Stakeholders - **Conway PD personnel** — bound by the policy. - **LPR supervisor** — operational owner of monthly camera inspections and the semi-annual public report. Identity not confirmed in the corpus; likely [[Lt. Andrew Burningham]] given his role as Flock administrator and as author of the H1 2025 LPR Report. - **Chief of Police** — authorizes user access; signs policy revisions. ## Timeline - 2013-08-30 — Effective date of the policy. - 2023-01-18 — R3 revision signed by William Tapley. - Future R4 — Pending update? Whether the policy has been further revised in light of Flock platform deployment, network-sharing capability, federal-LE access, and Home Depot camera-sharing is the open question. ## Notes - **The policy predates Flock's cloud architecture.** Drafted around physical cameras storing data on department servers (the policy text says "stored on the department's computer servers"). Flock's cloud-only retention model is a different architecture; whether the policy applies cleanly to cloud-hosted LPR data is an open legal question. - **The policy is silent on cross-jurisdictional sharing topology.** Section D.4 limits sharing to "evidence of an offense is indicated" but does not address pre-configured platform sharing relationships that enable thousands of one-off queries by counterparty officers. The policy contemplates a per-event sharing decision; Flock's product enables a per-relationship sharing configuration. - For deliverables that need a clean policy ↔ practice gap citation, this concept page is the cite for "policy ceiling: 150-day retention; sharing only with offense predicate; semi-annual public reporting" — and the corpus is the cite for the practice variance.