Flock Cameras Are Here: What you should know

Our Take

Credit to WDIO for a segment that captures the whole Flock playbook in miniature: a police department signs a contract promising faster answers on stolen cars and missing kids, the cameras go up on public roads, and only afterward do residents start asking who else gets access to that data, how long it's kept, and whether "public safety" is doing the heavy lifting it's supposed to. The fact that Duluth PD ended its contract after this story aired is the real headline here, and it's a pattern we've seen play out in city council chambers across the country once people realize these aren't passive traffic cameras but a networked system logging every plate that passes, searchable well beyond the town that paid for it.

Flock's own language, "connect communities, businesses, and public safety," is doing a lot of work to make a blanket surveillance dragnet sound like a neighborhood watch app. What that framing leaves out is the audit trail problem: once a city is plugged into Flock's national network, local officials lose a lot of control over who queries their data and why, and "solving crimes more efficiently" quickly becomes indistinguishable from tracking anyone's movements, for any reason, with almost no public accounting. Duluth pulling out isn't an isolated local story, it's a template other communities can use.

If you want to know whether these cameras are already watching your commute, check our camera map, and if your city is currently debating a Flock contract, our take-action page has the tools to get organized before the vote, not after the cameras are bolted to the pole.