How police accidentally published who they were tracking
The short version: Unredacted Flock audit logs leaked plate numbers from millions of police lookups, and Flock's fix was to threaten the host and shrink transparency — not fix accountability.
Our Take
Credit to Brink for surfacing this one: police agencies running Flock license plate readers turned over audit logs through public records requests without stripping out the plate numbers being searched. That's not a hypothetical privacy risk — that's actual surveillance targets, including people caught up in active investigations, exposed in bulk and downloadable by anyone. Nobody searched was notified. This is what happens when a surveillance dragnet gets built faster than the policies meant to govern it.
What really tells you everything about this industry's priorities is the response. Flock didn't rush to help the people whose data got dumped online, or push departments toward real redaction standards. It sent legal threats at the site hosting the records and then quietly reduced what its own "transparency" audit logs reveal going forward. That's the pattern we track constantly at DeFlock: when the system embarrasses the vendor, the vendor's instinct is to shrink visibility, not expand accountability. The audit trail that's supposed to reassure the public that these searches are lawful just became one more thing the company controls access to.
This is exactly why independent tracking of this infrastructure matters — the companies and agencies deploying it won't police themselves. Check our camera map to see what's watching in your area, and hit up take action if you want to push back on ALPR expansion where you live.
This is DeFlock The USA’s original commentary. The video above is the work of Brink, published on YouTube — full credit to the creator.