Across the United States, a growing movement is opposing Flock surveillance cameras, with reports of individuals dismantling and vandalizing them. Flock, a surveillance startup valued at $7.5 billion, has faced backlash due to its collaboration with federal authorities, particularly in relation to immigration enforcement. Critics argue that the extensive network of license plate readers enables U.S. Immigration and Customs Enforcement to target communities, raising significant privacy concerns among residents. In cities like La Mesa, California, where local councils have opted to continue using Flock cameras despite public opposition, acts of vandalism have surged. Reports indicate that cameras have been destroyed in various states, including Oregon and Connecticut, with some individuals leaving messages expressing their disdain for surveillance practices. According to DeFlock, a project mapping license plate readers, there are nearly 80,000 of these cameras nationwide, and numerous municipalities have rejected their use as public sentiment shifts against invasive monitoring technologies.
Ring has canceled its partnership with Flock Safety following backlash over surveillance concerns. The partnership was initially aimed at enhancing community safety through shared video footage.
Why do we care?
The data collection industry spent two decades operating on one assumption: collected data is an asset. Store everything, figure out the value later.
Flock didn’t hide its federal data-sharing terms — they were in the contract language municipalities signed. Political context made those terms visible and radioactive.
The buyer-user separation that protected surveillance vendors — the city council signs, the residents are watched — collapsed the moment organized opposition built tools to map the infrastructure and mobilize against it.
The broader implication runs directly into MSP operations. Every tool you deploy on client behalf collects data. Your RMM. Your monitoring platform. Your security stack. Most of it sits under terms clients haven’t reviewed and retention policies you haven’t audited. That was a manageable background risk when collected data was passive. It is an active liability now that AI makes that data actionable and political context can make any data-sharing arrangement a front-page problem overnight.
The MSP who deployed surveillance tools without surfacing federal data-sharing clauses isn’t managing technology — they’re managing undisclosed political liability. The MSP who inventories vendor data-sharing terms today avoids explaining them under public pressure tomorrow.