Product1 publisher3 min readPublished Updated
HaveIBeenFlocked turns Flock's own audit logs into a plate lookup anyone can run
The site says it assembled Flock audit logs from records requests to 6,586 agencies. That moves plate-reader oversight from a FOIA queue to a search box, incompleteness included.
The Product Desk · Product desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- HaveIBeenFlocked.com allows users to type in a license plate number and returns search results, including whether a Flock system operator has searched the database for that plate.
- Flock cameras are a brand of Automated License Plate Readers made by Flock Safety, a private for-profit technology company.
- Unlike regular security cameras that must be manually reviewed, Flock cameras use AI to capture photos of passing cars and log data such as license plate, make, model and color into a searchable database.
- The cameras have been branded "big brother" and "mass surveillance" and are unpopular because they track and log a person's movements regardless of whether they are a criminal suspect.
- HaveIBeenFlocked.com compiles Flock audit logs as the basis for its lookup.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
A site called HaveIBeenFlocked.com now lets a driver enter a license plate and see whether an operator has searched for it in Flock Safety's database [1][5]. The lookup is assembled from Flock's own audit logs, which the site says it obtained through public record requests covering 6,586 agencies across the United States [5][8].
The underlying product is worth restating plainly. Flock cameras are automated license plate readers built by Flock Safety, a private for-profit company [2]. Unlike a security camera that someone has to sit down and review, they use AI to photograph passing vehicles and write plate, make, model and color into a searchable database [3]. Every car gets logged, suspect or not, which is the reason the cameras have drawn labels like "big brother" and "mass surveillance" [4].
What HaveIBeenFlocked does is not a new dataset. It is a new index over an old one. The audit log exists because searching a surveillance database is supposed to leave a trace, including the reason the searcher gave for the lookup [6]. That reason field was designed as an internal compliance artifact, read by supervisors and auditors. Now it is a string a member of the public can read about themselves, one plate at a time [1][6]. Reason-field discipline stops being a policy question inside an agency and becomes a disclosure exposure: whatever an operator typed is what the subject of the search eventually sees.
The tool is also narrower than the panic will suggest, and the site says so. The logs record searches, not sightings: they do not show whether or when a vehicle passed a camera [6]. The site also notes that whoever ran a search may not have been a law enforcement officer, and that appearing in the results is not evidence anyone was ever under investigation [7]. So the product answers "who went looking for me, and what did they write down" rather than "where have I been."
The bigger operator lesson is about corpus quality, and it is the failure mode most consumer lookup tools share. The site warns that the dataset is incomplete, saying that "Few governments provide easy access to these logs, and the records we obtain are often redacted" [9]. A search box invites a binary reading, but an empty result here cannot mean no search occurred; it can equally mean no log was released, or that the log arrived with the relevant field blacked out [1]. That asymmetry, confident-looking hits and meaningless misses, is the thing a well-built version of this would surface per agency rather than per plate.
What to watch: whether agencies respond by tightening or slow-walking audit log releases, since coverage here is entirely downstream of FOIA compliance [8][9]; whether reason fields start arriving templated and uninformative, which would preserve the log while gutting its value; and whether Flock changes what its audit exports contain or how they are formatted, which would break the pipeline without any policy change at all. The account of the launch includes no response from Flock Safety [10].