The useful safeguard with mass license plate surveillance isn’t a glossy policy promise; it’s a verifiable trail of who looked up what, when, and why—and Have I Been Flocked turns those internal audit trails into something the public can actually see.
At a Glance
- Have I Been Flocked aggregates Flock Safety “audit logs” released under open-records laws so drivers can check if their plate was actively searched—this is about investigator lookups, not mere camera sightings.
- The database reflects only agencies that released logs; coverage is broadening but inherently partial by design and by law.
- Audit logs are a cornerstone accountability control that major civil-liberties groups and policy shops endorse, even as states diverge on disclosure rules.
- Public release battles are intensifying; some jurisdictions now narrow or exclude ALPR records and even certain audit details from disclosure.
What the site actually reveals: “searches,” not camera scans
Have I Been Flocked is a public-records project focused on one precise artifact inside Flock Safety’s automated license plate reader (ALPR) ecosystem: audit logs. In technical terms, an audit log records user-initiated activity within a system—who queried, what they looked for, and when. The site collects those logs, when governments release them under transparency laws, into a searchable interface where any driver can input a plate and see if that tag appeared in an agency’s search history. That is a crucial distinction. Audit logs are not the raw stream of camera detections; they’re the record of humans (or agency-side automated workflows) looking up plates inside Flock’s software.
The project’s own materials are blunt on this point: it aggregates audit logs released through FOIA or equivalent state laws, sometimes via vendor-managed “transparency portals,” and sometimes via direct public-records responses. The result is a growing, but necessarily incomplete, public window onto a historically opaque layer of surveillance practice—how often officers run specific plates, across which agencies, and over what periods.
How it works under the hood: records law, redaction, and scope limits
There is no national FOIA for cities and counties, and ALPR oversight statutes vary widely. In practice, that means Have I Been Flocked’s coverage footprint is determined by which agencies retain audit logs, how they log queries, and whether local counsel agrees the records are disclosable with appropriate redactions. The site leans into that reality: it instructs residents on how to file requests, what to ask for, and how to submit releases back for inclusion, creating a network effect that expands access plate by plate and agency by agency.
Two further constraints matter. First, audit logs often arrive redacted—names, case numbers, or sensitive fields may be masked—so the granularity of what the public can learn is uneven. Second, Flock customers differ in configuration and policy; some agencies publish recurring logs, while others resist, delay, or provide minimal fields. The site is transparent about this: the logs you can search are those an agency has actually released, so a “no result” can reflect non-disclosure as much as non-search.
Why auditability is the safeguard that scales
In any large data system that touches civil liberties, an audit trail is not a luxury—it’s the control that makes all the other rules enforceable. The Brennan Center’s ALPR policy recommendations put it plainly: access and use should be logged in a format that permits meaningful auditing, including reasons for alerts and details on inter-agency sharing. That guidance is not abstract; it’s the blueprint that lets internal affairs units, inspectors general, courts, and, where law allows, the public, verify whether surveillance tools are used for legitimate aims and according to policy.
Have I Been Flocked operationalizes that principle for the end user. It is not adjudicating probable cause, and it cannot answer why a specific officer ran a plate. It does something narrower but vital: it surfaces whether an identifier became the subject of active search activity inside a powerful police technology platform. In a space where misuse cases typically come to light only after harm, audit visibility can be the tripwire that deters or documents abuse.
The scale of searching—and why it matters
Flock’s networked model has changed ALPR from a collection of local sensors into a queryable, multi-jurisdictional platform. Reporting has tallied millions of plates appearing across hundreds of millions of searches, a scale that helps explain why audit transparency carries such weight: a single user’s query footprint, replicated across thousands of users and agencies, constitutes a map of investigative attention that never existed in analog policing. When the baseline capability is “type a tag, get location trails from far beyond your city,” the risks shift from a single-camera misuse to systemic overreach.
This is precisely why audit logs—and the public’s ability to inspect them where law permits—are the policy fulcrum. Without logs, debate about retention windows or data sharing devolves into promises; with logs, oversight bodies can verify how features are actually used, how often, and by whom. As more agencies connect to shared ALPR networks, the value of standardized, disclosable audit data only increases.
What the site can and cannot tell you
Two clarifications prevent misinterpretation. First, appearing in the audit database does not prove your car was photographed on a given date; it shows your plate was searched inside Flock by an agency that released its logs, which often—and appropriately—occur after an alert or detection elsewhere. Second, the database is not comprehensive. If your local department withholds logs or your state has carved out ALPR exemptions, you may see nothing even if your plate is routinely checked. The site calls this out; its scope tracks public disclosure, not total activity.
Conversely, when a match does appear, it is authoritative within its limits: it ties a plate to a timestamped search in a specific agency’s tenant. For drivers contesting a pattern of attention, journalists reconstructing timelines, or councils weighing contract renewals, that is actionable, documentary evidence—not opinion or extrapolation from raw camera hits.
The legal landscape: one technology, three recurring fights
Arguments over ALPRs recur on three axes that often get conflated. The first is public-records law: are ALPR-derived records, including audit logs, disclosable with redactions, or categorically investigatory and exempt? Courts and legislatures split; California litigation has moved in both directions over the last decade, and more recent state-level exemptions have narrowed access to ALPR data and even certain audit artifacts.
The second axis is constitutional: when does aggregated, long-duration vehicle tracking become a “search” requiring a warrant? Courts have increasingly recognized the sensitivity of persistent, networked location monitoring—even when each discrete observation occurs in public—and have encouraged or required heightened safeguards or judicial process in some contexts. That tension will not abate as networks grow denser.
The third is policy design: retention limits, inter-agency sharing rules, and mandatory auditability. Here, cross-ideological consensus is stronger than the headlines suggest. Auditable access, reason codes, periodic external review, and calibrated retention are endorsed by civil-liberties organizations and by auditors seeking basic accountability hygiene in digital policing systems.
Transparency is expanding—and contracting—at once
Public-facing audit transparency is not a one-way ratchet. Some jurisdictions have used open-records laws to publish recurring ALPR audit logs or to release them upon request, which is exactly the material Have I Been Flocked relies on. Other jurisdictions have moved to limit what can be disclosed about ALPR systems, including excluding the data from public-records statutes or carving out “audit trail” fields from release. Washington State’s recent guidance illustrates how states can reshape the boundary conditions around what the public can see, regardless of a vendor’s capabilities.
Expect this push-pull to intensify. As more misuse cases are substantiated through audits and more agencies lean on ALPR networks for day-to-day policing, legislators will continue to refine disclosure rules—some toward greater transparency with protected redaction regimes, others toward categorical exemptions that shift oversight behind closed doors. Have I Been Flocked’s footprint will expand in places that choose the former and contract where the latter prevails.
How communities, agencies, and drivers can use the tool
For community members, the site is a practical way to ground abstract privacy concerns in specific, checkable facts: was my plate searched; by whom; when? For city councils and police managers, it is an external reference point to test whether internal auditing practices are producing the right fields and whether usage patterns align with policy goals. And for journalists and researchers, the normalized interface reduces friction in tracing spikes in search activity to events, initiatives, or individual users without reinventing the records-collection wheel each time.
The project’s design choice—to publish only what governments release and to document provenance—keeps it on firm footing. It is not a data broker and not a shadow ALPR network; it is an index of official audit trails convened for public inspection, with submission pathways that preserve links to original requests and responses.
A new website called Have I Been Flocked lets anyone enter a license plate number to check whether it appears in publicly obtained audit logs from Flock Safety’s network of automated license-plate reader cameras.
Flock operates tens of thousands of AI cameras across the U.S.… pic.twitter.com/CGUPi3u23s
— Bella (@stockbella) August 17, 2026
The bottom line
ALPRs are here, networked, and increasingly woven into routine policing. In that environment, arguments about efficacy or privacy are secondary until you can establish a baseline of use. Have I Been Flocked supplies that baseline where law allows, converting internal audit trails into public accountability. It will never be comprehensive, because public-records law is fragmented and evolving. But where it exists, it changes the conversation from assertions to artifacts: this plate, this agency, this timestamp. That is how democratic oversight of powerful technologies begins—one verified log entry at a time.
Sources:
feedpress.me, haveibeenflocked.com, nypost.com, deflockapex.org, yahoo.com, san.com, aclu.org, information.auditor.ca.gov
