Boston ditched Flock cameras, but your city might not.
The short version: Boston walked away from Flock after a configuration error exposed its cameras to outside law enforcement searches — proof that 'local control' promises often don't hold up.
Our Take
Credit to CacheLine for digging into Boston's reversal, because this is exactly the kind of story that gets buried in a press release and forgotten. A city that bought into the Flock Safety pitch — "it's just for us, it's just for this" — found out the hard way that network configurations can quietly open the door to other agencies pulling local plate data for purposes nobody approved. That's not a hypothetical slippery slope. That's the actual mechanics of how these systems fail.
Flock's whole sales pitch rests on trust: trust the access controls, trust the audit logs, trust that your police department's cameras won't become someone else's dragnet. Boston's experience shows how thin that trust actually is, and how a single misconfiguration can turn a "community safety tool" into a surveillance pipeline nobody consented to. Most cities don't have the staff, the technical scrutiny, or frankly the political will to catch these problems before they happen — they just hope it works out. Boston got lucky enough to catch it and hold its ground. Plenty of cities won't.
If you want to know whether your own city is running this experiment on you right now, check our camera map to see what's been deployed near you, and if you don't like what you find, our take-action page has concrete steps for pushing back before your city becomes the next cautionary tale instead of the exception.
This is DeFlock The USA’s original commentary. The video above is the work of CacheLine, published on YouTube — full credit to the creator.