Boston Dumps Flock Safety After Firm Shared Licence Plate Data Nationwide Without Consent

The City of Boston has terminated its contract with Flock Safety, the surveillance camera and licence plate reader company, after discovering that Flock had enabled a "nationwide lookup" feature that allowed Boston's data to be searched by law enforcement agencies across the entire United States. The problem? Boston's contract specifically required that feature to be disabled.

This is not a minor administrative disagreement. Boston signed up with Flock on the understanding that licence plate data collected within the city would remain local. The idea was that the cameras would help Boston's own police solve crimes in Boston. Instead, the data was apparently accessible to any of the thousands of law enforcement agencies in the Flock network, creating a de facto national surveillance database without any of the oversight, legal review, or public consent that would normally be required.

What Flock Safety Actually Is

Flock has become one of the most widely deployed surveillance systems in the United States in a remarkably short time. The company sells solar-powered cameras that capture licence plates and other vehicle data, cross-referenced with law enforcement databases. As of late 2025, Flock reported operating in over 5,000 communities across the US, with tens of thousands of cameras deployed.

The appeal to local governments is obvious. The cameras are relatively cheap, easy to install, and have been credited with solving car thefts and other vehicle-related crimes. But the flip side is that every community that installs Flock cameras is contributing to a shared data pool, and the terms of what gets shared with whom have apparently not always been what municipalities were told they were.

Boston is not the first city to raise concerns about Flock. Privacy advocates have been warning for years that Flock's network architecture creates risks precisely because it is so interconnected. A camera in Boston capturing the movements of a Boston resident could, under the nationwide lookup setup, be queried by a sheriff's department in Texas with no connection to that resident whatsoever.

The Consent and Oversight Problem

American cities purchasing Flock cameras are not typically putting the matter to a public vote. These are often administrative decisions made by police departments or city managers. Residents rarely know the cameras are there, let alone that their vehicle's movements are being logged and potentially shared across state lines.

Boston's action is notable because it represents a city actually enforcing its contract and pulling out when the terms were not met. That is genuinely unusual. Most of the time, data sharing violations of this kind are discovered by journalists or advocacy groups long after the fact, and the vendor faces little practical consequence.

Flock has not publicly commented in detail on Boston's specific claims. The company has previously argued that its network sharing features help solve serious crimes that would otherwise go unsolved, pointing to cases where out-of-state lookups identified suspects in murders and kidnappings.

What Comes Next

Boston's decision to terminate the contract rather than seek a technical fix suggests the city has lost confidence in Flock's ability or willingness to comply with agreed limitations. That is a significant statement.

For other cities currently operating Flock cameras, the question now is whether their own contracts have similar restrictions and whether those restrictions are actually being honoured. Given how opaque these agreements tend to be, that is not a question most residents can easily answer for themselves.

The broader issue is that the US does not have a comprehensive federal framework governing how local surveillance data can be shared across jurisdictions. Until that changes, the gap between what a city thinks it has agreed to and what actually happens with the data will remain uncomfortably wide. Boston finding out by accident is not a reassuring sign.