Cities Can't Turn Off Flock Cameras, So They're Covering Them With Trash Bags

When the Only Way to Stop a Surveillance Camera Is a Trash Bag

In what might be the most striking image of the tension between local governance and federal immigration enforcement in recent memory, city workers in Dayton, Ohio found themselves standing in the street holding trash bags — not to collect refuse, but to cover license plate reader cameras they could not figure out how to turn off. The cameras in question belong to Flock Safety, a private surveillance technology company whose automated license plate recognition (ALPR) systems have been quietly installed in hundreds of cities across the United States. When Dayton learned that data collected by those cameras was being shared with federal immigration enforcement agencies, local officials wanted to act fast. The problem? They couldn't simply flip a switch.

What Are Flock Safety Cameras and How Do They Work?

Flock Safety is an Atlanta-based company that provides automated license plate reader technology to law enforcement agencies, municipalities, and even private homeowners associations. The cameras capture images of passing vehicles and extract data points including license plate numbers, vehicle make, color, and distinguishing features. That data is then uploaded to Flock's cloud-based platform, where it can be searched and cross-referenced against law enforcement watchlists in real time.

The pitch to cities has always been straightforward: reduce crime, solve cases faster, and do it all without requiring a massive investment in officers or infrastructure. Hundreds of police departments have signed contracts with Flock, making it one of the fastest-growing surveillance vendors in the country. The cameras are physically unassuming — small, solar-powered devices mounted on poles — but they generate an enormous volume of data on the movements of ordinary people every single day.

The Immigration Enforcement Connection

The controversy in Dayton began when city officials discovered that data gathered by their locally installed Flock cameras was accessible to federal agencies involved in immigration enforcement. This raised immediate alarm bells for a city that, like many others across the country, has expressed concerns about the role local infrastructure should play in federal deportation efforts.

The data-sharing arrangements that make this possible are often buried in the fine print of Flock's contracts and terms of service. Flock operates a shared network called the Flock Network, which allows law enforcement agencies at different levels — local, state, and federal — to query license plate data across jurisdictions. That means a camera installed by a city government to catch car thieves could simultaneously be feeding data to agencies operating immigration enforcement operations.

For cities that have passed sanctuary city policies or have otherwise sought to limit their cooperation with federal immigration authorities, this revelation represented a significant and unexpected problem.

Why Couldn't Dayton Just Turn the Cameras Off?

This is the question at the heart of the story, and the answer is both technically and contractually complicated. Flock Safety cameras are managed through the company's proprietary cloud platform. Cities do not operate the backend infrastructure themselves — they are, in effect, customers of a software-as-a-service surveillance product. That means control over how data is stored, who can access it, and what integrations are active does not always rest entirely with the municipality.

Contracts between Flock and local governments have reportedly made it difficult for cities to unilaterally modify data-sharing settings or disable network-level access without involving the company. When Dayton officials wanted to act quickly — before a full legal or contractual review could be completed — they had few immediate technical options available to them. The solution their workers reached for was bluntly physical: covering the cameras with trash bags to block their field of view and prevent them from capturing new data while the city sorted out the longer-term solution.

It is an almost absurdist image — a high-tech AI-powered surveillance network rendered inoperable by a $0.10 piece of plastic — but it underscores a very serious problem about how cities enter into technology contracts without fully understanding what control they are giving up.

A Broader Pattern Across American Cities

Dayton is not alone. As federal immigration enforcement has intensified, a growing number of municipalities have begun scrutinizing the surveillance contracts they signed during quieter political times. Many are discovering that the data their cameras collect flows through networks that are far more interconnected — and far less under local control — than they realized when they signed on the dotted line.

Civil liberties organizations have warned about this dynamic for years. The American Civil Liberties Union and other advocacy groups have published extensive research on how automated license plate readers create detailed records of people's movements, and how that data can end up in the hands of agencies that residents and local governments never intended to share it with.

What This Means for the Future of Municipal Surveillance Contracts

The Dayton incident should serve as a warning to every city currently operating or considering a contract with a private surveillance vendor. Key questions that local governments need to demand answers to before signing any such agreement include:

• Who has access to the data collected by these cameras beyond our local law enforcement agency?
• Does the vendor participate in any shared law enforcement data networks, and can we opt out?
• What are our contractual rights if we want to suspend or terminate data sharing mid-contract?
• How quickly can we disable the system or specific data-sharing features without vendor assistance?
• What data retention policies apply, and who controls deletion?

These are not hypothetical concerns. They are questions with real consequences for real people — particularly immigrant communities — living in cities that believed they had more control over their own surveillance infrastructure than they actually did.

The Trash Bag as a Symbol

There is something worth sitting with in the image of a city employee climbing a ladder to drape a trash bag over a sleek, solar-powered surveillance camera. It captures the gap between the promises of smart city technology and the messy, often poorly understood reality of how that technology actually operates. Cities have been sold surveillance systems as tools they control. Dayton's experience suggests that in some fundamental ways, the control runs in the other direction — and that when cities want to reassert authority over their own infrastructure, they may find that a trash bag is the most powerful tool they have.

As debates over immigration enforcement, data privacy, and the role of private technology vendors in public governance continue to intensify, the Flock camera controversy is unlikely to be the last of its kind. What Dayton's experience makes undeniable is that the time for cities to read the fine print is before the cameras go up — not after.