Flock Safety mandates audit logs, case-linked searches, and seven-day retention for license plate readers

Flock Safety is converting optional guardrails into mandatory rules for every law enforcement customer. The changes take effect on a fixed deadline, removing local discretion over whether to enable auditing, case-number linking, or retention limits. This shift creates a uniform compliance surface for engineers who maintain the platform or build integrations with police records systems.

The new audit tool is designed to detect and block abnormal search patterns. When triggered, it locks the user account until an internal review is completed. This introduces a runtime dependency on the agency’s own review process, which may vary in speed and rigor. Engineers should note that the tool does not replace judicial oversight; it merely flags behavior after the fact.

Data retention is now seven days by default, down from 30. Longer retention is permitted only when data is tied to an active case number. This change reduces storage costs but increases the operational burden of managing case-linked retention rules. Engineers must ensure that retention overrides are logged and auditable, adding complexity to data lifecycle management.

Customers can now restrict outside-agency searches to specific offense types, such as homicide or arson. This feature allows agencies to block searches related to immigration enforcement or other sensitive categories. The change shifts policy decisions from Flock to individual departments, requiring engineers to implement fine-grained access controls that reflect local priorities and legal constraints.