# Flock Audit Logs and Retention The Flock platform's **search-event recording and data-retention** layer. Audit logs record every plate lookup performed by every authorized user (including federal-LE counterparties) against the Conway PD dataset, with metadata fields including searching officer, agency, search-reason free text, search time, license plate queried, filters used, networks/devices searched. The retention layer separately governs how long raw plate-read data remains queryable. ## How it appears in the corpus **Internal-officer audit logs** ([[Conway PD Audit Logs Series]]): 13 monthly CSVs across April 2025 – April 2026, totaling ~10,391 Conway-officer search events. Pre-cutover schema 14 cols (`Text Prompt, Moderation` included); post-cutover schema (effective 2025-12-17) drops one column. **Federal-officer audit logs** ([[Federal Searches CSV]]): A single export covering March 1 2026 – April 21 2026, 5,929 federal-officer searches that touched Conway data. **Retention rules:** - **Flock platform default (per [[Flock Safety Order Form and Contract]]):** 30-day retention for raw plate reads. - **CPD Policy 800-32:** 150-day retention ceiling, "in accordance with State Law," then automatic purge. Hit data used in investigations may be retained until "no longer needed." - **Audit log retention:** Not specified in the corpus. The 13 monthly files extending back to April 2025 suggest at least 13-month retention, but the corpus does not surface Flock's official audit-log retention policy. ## Stakeholders - **Flock** — platform operator; sets the retention defaults and generates the audit-log exports. - **Agency administrators** — configure retention within the platform-supported range; per CPD Policy 800-32 are responsible for "automatic purge" verification. - **Auditing/oversight bodies** — Conway PD's "LPR supervisor" (per Policy 800-32) reviews semi-annual statistical reports; the public has access on request. - **FOIA requesters** — depend on audit-log retention to surface evidence of historical activity. ## Key takeaways - **Schema cutover at 2025-12-17.** The Conway audit log series shifts from 14 to 13 columns on this date. The `Important Update to Flock Audit Logs to Protect Officer Safety Active Investigations.msg` (in `raw/`, not yet documented as a source page) is the platform-change announcement; reviewing it will confirm which column was dropped and the stated rationale. - **Officer-name redaction is inconsistent.** Some pre-cutover files marked "Redacted" still contain visible officer names (e.g., "Phillip Boyd" in 8/2025 file). Plates are never redacted. The post-cutover files (March 2026, April 2026 partial) carry no "- Redacted" suffix but still contain identical PII patterns. The wiki's privacy standard bars republication of either category. - **The Reason field is officer-supplied free text.** It is the primary check on policy-compliant use (per CPD Policy 800-32's "evidence of an offense is indicated" sharing standard), but it is not validated at search time. An open analytic question is the distribution of Reason values across all 10,391 internal searches. - **Audit-log generation is platform-mediated.** Conway PD does not own the audit logs in any controllable sense; Flock owns the generation pipeline. The exports are deliverables the agency requests of Flock, then forwards to FOIA requesters. The agency could in principle ask Flock for an unredacted, fuller export — and Flock could in principle modify what fields are included. (Cf. the schema cutover.) - **Retention vs. evidentiary preservation tension.** A 30-day default platform retention puts most plate reads beyond retrospective FOIA reach within a month. The 150-day policy ceiling and the "until no longer needed" hit-retention rule mitigate but do not eliminate this. Public-records investigations of LPR systems must be tightly time-coupled to recent activity. ### In PDFOI-2026-1874 (LRPD Flock emails) The Little Rock PD production surfaces several 2026 audit and compliance developments visible in the agency's mailbox, documented in [[Flock Audit and Compliance Controls and Gaps]]: - **Mandatory NIBRS Offense Type per search.** Flock made selection of a NIBRS-based "Offense Type" from a dropdown a required field before any LPR search runs, while the older free-text "Search Reason" became optional ([[Flock Audit and Compliance Controls and Gaps]], Emails 1-24.pdf pp. 564, 645). Axon Fusus made a parallel change in its own RTCC stack, requiring an "Offense category" / "Search purpose" before an ALPR search and defaulting a "Case number" field to Required (min 3 chars) in release 2026.14 ([[Flock Audit and Compliance Controls and Gaps]], Emails 1-24.pdf p. 476). - **The "\*\*\*" masking disclaimer.** Flock added audit-record disclaimer text explaining that records shown as "\*\*\*" do exist but are "intentionally only visible to the searching agency" ([[Flock Audit and Compliance Controls and Gaps]], Emails 1-24.pdf p. 564; reprinted in Emails 25-35.pdf p. 275). This describes a vendor visibility rule; it does not establish that LRPD generated or retained a particular export. - **Out-of-state "Network Audit filter."** Flock's April 2026 newsletter announced a new "Network Audit filter" surfacing only out-of-state searches for any date range across the full audit history, pitched to "confirm there's no out-of-state activity, or review the searches that did happen" ([[Flock Audit and Compliance Controls and Gaps]], Emails 1-24.pdf p. 1330). - **A documented audit-log gap.** Axon Fusus release 2026.4 added adjustable confidence levels for ALPR vehicle-attribute searches with a stated caveat that "Adjusting confidence levels does not create audit log entries" ([[Flock Audit and Compliance Controls and Gaps]], Emails 1-24.pdf p. 556) — a parameter that materially shapes search results yet leaves no entry in the trail. These vendor-announced features bear on [[T004 - Ambiguous Audit-Log-Review Response vs Unresolved Item 3]], but they do not prove LRPD's configuration, permissions, retention, or possession of the named exports. The separate Deconfliction Advisories establish particular overlap-triggering events, not a complete officer-level audit log. ## Independently archived vendor policy and audit context (2026-07-20) Flock's current evidence policy states a **30-day default** from capture, subject to customer agreements and law; says data are hard-deleted after the applicable period; and offers extended LPR retention up to one year when not otherwise required by law only after approval from an elected official or governing body (vendor primary/self-description, [Flock Evidence Policy](../../web%20archive/2026-07-20/flocksafety.com/flock-evidence-policy.md)). This is evidence of Flock's published policy, not proof that a tenant's setting or deletion process conformed. Flock's LPR policy says all queries are stored for auditing and describes customer administrators, privileged vendor access, customer-controlled sharing, legal/security disclosure exceptions, and use of less than one percent of LPR images—described by Flock as stripped of metadata and identifying information—for machine-learning improvement (vendor primary/self-description, [Flock LPR policy](../../web%20archive/2026-07-20/flocksafety.com/lpr-policy.md)). Those are vendor representations. They do not independently establish technical enforcement, completeness of logs, de-identification sufficiency, or the setting used by an Arkansas tenant. The May 26, 2026 price list separately contains extended-retention SKUs, including jurisdiction-specific one-, three-, and five-year entries. Catalog availability is not a tenant setting (official procurement attachment / vendor catalog, [Flock price list](../../web%20archive/2026-07-20/omniapartners.com/r250203-flock-pricing-2026-05-26.md)). The LAPD Inspector General found a special five-year Flock retention term in that mixed-vendor program and documented uncertainty over vendor access and written security agreements (primary public record, [LAPD OIG ALPR audit](../../web%20archive/2026-07-20/lapdpolicecom.lacity.org/lapd-oig-alpr-audit-2026-07.md)). That California configuration cannot be imputed to Arkansas. ## Arkansas compliance tests after Act 668 [[Arkansas Automatic License Plate Reader System Act|Act 668 of 2025]] makes the relevant record set broader than a contract's headline retention number. Compliance testing requires the tenant configuration and change history; preservation linked to each ongoing investigation; destruction at investigation/criminal-action conclusion; 24-hour data-update records when updates are available; public policies; six-month statistics; and dissemination/sharing logs. Vendor policy and a transparency page cannot substitute for those agency records.