- HaveIBeenFlocked.com allows users to search their license plate to see if it has been queried by law enforcement, but the reason field in the audit logs has evolved into vague abbreviations or blank entries, limiting public accountability.
Your plate shows up on HaveIBeenFlocked.com. In many records: the agency name, the operator, the timestamp. And where the reason should be — the field that’s supposed to tell you why someone pulled your location history — there’s a vague abbreviation, a blank, or, in some cases, a numeric placeholder. No codebook attached. No explanation offered. That’s not an oversight. It’s a pattern.
HaveIBeenFlocked.com aggregates Flock Safety audit logs obtained via public records requests, letting anyone search their own plate to see if an operator actively queried the database. Not just whether a camera photographed your car — whether someone chose to look you up. The “reason” field was supposed to tell you why. Increasingly, it tells you nothing.
From “Fishing Violation” to Sanitized Codes
Reason fields have quietly evolved from readable free text into something far more useful to police — and far less useful to you.
Before January 2026, free-text reason fields produced entries that were absurd but at least readable: “fishing violation,” “stranger danger,” “Suspicious Auto (bullet holes).” Chaotic, yes — but you could see the shape of what was happening. Then Flock introduced dropdown menus. Reasons collapsed into sanitized phrases like “Traffic Infraction – Criminal Justice Purpose,” per Texas Department of Public Safety logs. San Jose’s Flock problem illustrates how vague abbreviations and internal codes are the logical extension of that trend: internal tracking preserved, public accountability diminished…