Documented Incident

Police MisuseAuditsPrivacyCompany NewsIndiana

EFF finds officers typed jokes and gibberish into Flock ALPR 'reason for search' fields

The Electronic Frontier Foundation reported that police officers across the US entered flippant or nonsensical text into the mandatory 'reason for search' field of Flock Safety's license plate reader network. Examples cited include a Lake County, Indiana sheriff's deputy who searched more than 19,000 cameras across 1,558 communities in July 2025 with the reason 'LMAO,' and a Goshen Police Department officer who searched 6,474 networks covering 82,413 cameras on May 7, 2025 with the reason 'idk.' The EFF said 'TBD' appeared in over 6,300 searches across more than 30 agencies, alongside profanity and keyboard mashing. Flock has since replaced the free-text field with pre-set offense categories, a change the EFF argues does not verify that the stated reason matches the actual purpose.

Why this matters

Search-reason logs are one of the few audit trails available for a network that lets one officer query vehicle location data across thousands of jurisdictions, and the EFF's findings go to whether that documentation can support meaningful oversight. How agencies and Flock respond sets expectations for audit and accountability standards in other communities using ALPR systems.

Key facts

Timeline

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

More from Indiana

Everything we have documented in Indiana, or search every Indiana article in the archive.

About this record

BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.

Updated September 20, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.