Flock Logs Blow Open Driver Tracking

Police car blocks residential street at night behind caution tape
Photo: Thomas Egan Photography / Shutterstock

A free website now lets you see if police ran your license plate inside Flock Safety’s search system, using public audit logs.

Story Snapshot

  • The site aggregates public Flock Safety audit logs obtained through records requests.
  • Search results show if, when, and which agency queried a plate in the system, not just camera sightings.
  • Coverage is limited to agencies that release audit logs; gaps remain where records are withheld or redacted.
  • The rollout lands amid wider fights over access, privacy, and oversight of license plate reader data.

What The New Site Actually Shows

Have I Been Flocked aggregates “audit logs,” which are records of searches performed inside Flock Safety’s platform, and makes them searchable for the public. The site says a match means someone looked up a plate in the system, which goes beyond a camera simply snapping a photo. The tool displays details like the date, time, and the agency that ran the query, based on what the government released. This gives drivers a window into how plate data is accessed.

Flock Safety’s cameras are used by police and other agencies to scan plates and to share data across jurisdictions. The audit logs captured by the site come from open records laws. Volunteers and requesters submit official responses and documents to the project, which then standardizes and posts them for search. This model turns scattered disclosures into a single view that regular people can use without filing their own requests first.

Limits And Redactions In The Data

The site warns that searches only appear for agencies that released their audit logs, so the database is partial by design. Some agencies post heavily redacted logs, which can mask user names, search reasons, or other fields, limiting context. Because public records laws differ by state, and because some agencies resist disclosure, coverage will vary. Users should treat a “no results” outcome as a lack of available records, not proof that no one searched their plate.

Media reports highlight the scale and public interest: millions of plates have appeared across hundreds of millions of Flock searches, and the site lets drivers check for their own numbers. News coverage also explains that a hit indicates an operator looked up a plate, not just that a camera saw it, which is a key distinction for accountability. That difference matters for both proper use and potential misuse, since audit trails can deter or identify abuse.

Why This Matters Across The Political Spectrum

Transparency groups have long pushed for strong logging and public oversight of automated license plate reader systems. The Brennan Center urges that use be logged in ways that allow audits, reinforcing that access records are vital safeguards. Civil liberties groups won rulings that reject blanket secrecy for mass plate data, arguing it is not always an “investigative record” that can be hidden from the public. These steps seek balance between safety tools and civil rights.

At the same time, some courts and state laws limit what must be released, and agencies warn that broad disclosure could expose tactics or sensitive data. That tension drives uneven access and fuels public distrust. A practical takeaway remains clear: audit logs, when released, show who searches what and when. This site lowers the barrier for people to see those controls in action, test policy claims against records, and press local leaders for stronger rules when gaps appear.

Sources:

feedpress.me, haveibeenflocked.com, deflockapex.org, san.com, aclu.org