Flock Safety Mandates Audit Assistance and Case Codes for All Clients After 50+ Officer Misuse Cases

The policy shift follows documented officer abuses including a New Bedford officer charged with stalking an ex-girlfriend via plate queries and three Georgia deputies arrested for personal tracking. A Washington Post review identified at least 50 law enforcement personnel charged with misusing Flock data. The company previously treated the case-code requirement as optional since its July 2025 rollout, allowing easy circumvention through emergency bypasses.

Procurement records and contract data show Flock expanded rapidly into liberal jurisdictions before cancellations in Los Angeles, Cambridge, and Eugene. The ACLU noted that identical purpose-input rules failed earlier because users simply lied about investigative intent. Data retention cuts to seven days appear substantive on paper, yet cross-agency sharing controls remain unenforceable without technical verification of stated reasons.

Flock's network creates persistent location histories that survive local policy changes through neighboring agency access. Official statements emphasize privacy commitments while the underlying architecture still permits one officer's query to pull from unrelated jurisdictions without automated purpose validation.

Next phase will test whether mandatory audits produce measurable drops in misuse reports or merely shift abuse patterns to emergency-flagged queries that evade review thresholds.