Inside a Flock LPR Search: How Investigators Actually Use the Tool

Our Take

Credit where it's due: Flock's product team, in this walkthrough, is more transparent than most vendors about how a search actually gets typed into the box — a case number, an offense code, a time window. That's useful context, and it's worth watching precisely because it's Flock explaining its own system in its own words. But remember who's narrating. This is a company demo, not an audit. The "guardrails" described — mandatory reason fields, role-based access, logged justifications — are policies Flock built and that individual police departments configure for themselves. There's no independent regulator checking that a detective's typed-in reason is true, that the audit log is ever reviewed, or that a search outside the stated case doesn't happen quietly in a system with millions of plate reads behind it.

The video leans hard on the sympathetic use cases — missing persons, violent crime, victim justice — because that's the framing that sells cameras to city councils and keeps civil liberties pushback at bay. What it doesn't dwell on is the much larger pattern DeFlock tracks: departments sharing access across state lines, informal lookups that stretch past the original offense, and networks that quietly expand with little public debate. A search screen with a dropdown menu for "reason" is not the same thing as real accountability. It's a UI feature, not a constitutional safeguard.

If you want to see how far this network actually reaches in your own town, check our camera map and start asking your local council the questions Flock's demo conveniently skips. And if you think your community deserves a real debate before more of these readers go up, our take-action page has the tools to make that happen.