Milford to change Flock camera usage policies following community pushback

Our Take

Credit where it's due: WFSB 3's report shows what happens when residents refuse to let a city council or police chief quietly roll out a surveillance network without a fight. Milford's pushback forced a conversation about policy, and that conversation is forcing changes. That's the whole game with Flock Safety deployments — these systems get installed fast, often with little public input, and they only get reined in when enough people show up and ask hard questions about retention windows, audit logs, who gets access, and what "public safety" actually means in practice.

Policy tweaks are a start, not a finish line. A camera that stores less data or shares with fewer agencies is still a camera logging every car that passes, building a location history on every driver whether or not they're suspected of anything. Milford's win should be read as a floor, not a ceiling — the same questions apply to every town sitting on a Flock contract renewal. Check our camera map to see what's already watching your routes, because most residents have no idea how dense these networks have gotten until they look.

If your town hasn't had its Milford moment yet, it's worth forcing one before the contract gets signed rather than after. Our take-action resources walk through how to get on a council agenda, what questions actually matter, and how to organize neighbors who care about not living under a permanent vehicle-tracking grid.