My town just voted for more Flock cameras than cops—and the false arrests nobody’s talking about convinced them anyway

Your small town just voted to blanket itself with license plate readers—more cameras than it has police officers—and nobody stopped it.

That’s the reality now unfolding in a South Carolina municipality where residents, despite explicit warnings about false arrests tied to Flock surveillance technology, approved an expansion of automated camera networks that will feed data into a private company’s servers. The vote itself is a window into how surveillance infrastructure spreads in America: not through federal mandate, but through local decisions made in the absence of meaningful public debate about what happens when police rely on algorithmic identification.

Flock Safety operates the largest private surveillance network in the United States. The company manufactures license plate recognition cameras and operates a cloud platform that aggregates footage from thousands of locations. Police departments across the country subscribe to access that data—paying per search or per month for the ability to query video feeds, run plate lookups, and receive automated alerts when a flagged vehicle passes a camera. For a deeper look at how license plate readers have evolved into multi-signal tracking nodes, see our analysis of license plate reader surveillance.

The South Carolina town’s decision to install more Flock cameras than sworn officers represents a specific kind of governance inversion: the town is outsourcing investigative capacity to a private vendor whose incentive structure is fundamentally misaligned with accuracy or due process. Flock’s business model depends on deployment volume and search frequency. The more cameras installed, the more searches police run, the more data the company collects and the more valuable its network becomes.

What the False Arrest Cases Actually Reveal

What residents in this town learned—too late to change the vote—is that Flock’s technology has generated false arrests. In 2023, a man in Georgia was arrested based on a Flock alert that misidentified his vehicle as one involved in a crime. He spent time in jail. The arrest was eventually dismissed, but only after he had already been detained and processed. Similar incidents have been documented in other jurisdictions. Police officers, trusting the algorithmic match, acted on incomplete or incorrect data.

The town’s decision is particularly striking because residents had raised these concerns explicitly during the public process. They cited the false arrest cases. They mentioned data breaches—Flock has experienced security incidents that exposed user information. They questioned whether a private company should be the custodian of this much surveillance infrastructure. And yet the vote proceeded.

Is This Governance or Outsourcing?

This is where the mechanics of modern surveillance differ from older models of state monitoring. Flock isn’t a government program that citizens can directly vote down through electoral pressure. It’s a private infrastructure layer that police departments adopt, which then becomes embedded in municipal operations. Once installed, the cameras are difficult to remove. The data flows to a private server. The company’s terms of service, not democratic process, govern how that data can be used or shared.

The structural parallel to Cambridge Analytica is worth naming explicitly. Cambridge Analytica built its persuasion operation on the principle of data aggregation at scale—collecting behavioral signals from millions of people, inferring psychological profiles, and using those inferences to target individuals with micro-tailored messages. The company’s power derived from the fact that the data collection happened outside the awareness or explicit consent of the people being profiled. Flock operates on a similar principle: it aggregates surveillance data from thousands of locations, builds a searchable database of vehicle movements, and sells access to that database to law enforcement. The data subject—you, driving your car through town—has no idea which cameras are Flock cameras, has no mechanism to opt out, and has no visibility into how many times their vehicle has been queried or flagged.

The difference is that Cambridge Analytica was eventually shut down. Flock is expanding.

How Does a Private Surveillance Network Grow Without Federal Oversight?

The company has installed cameras in over 4,000 locations across the United States, according to public reporting. It has raised hundreds of millions in venture funding. It has cultivated relationships with police departments in small towns and major cities. And it has done this with minimal federal regulation, minimal transparency requirements, and minimal accountability mechanisms. The broader pattern of governments struggling to regulate surveillance technology is documented in our coverage of facial recognition restrictions—a parallel policy battle where legislative responses have consistently lagged behind deployment.

What makes this particular South Carolina vote significant is that it demonstrates how this expansion happens at the local level, often without the kind of sustained public scrutiny that might slow it down. The town council voted. The vote passed. The cameras will be installed. And the residents who raised concerns about false arrests and data security will live in a town where their vehicle movements are continuously recorded, aggregated, and searchable by police—with no legal requirement that they be told when they’ve been flagged, no right to know if they’ve been misidentified, and no recourse if the algorithmic match is wrong.

Why the Error Costs Fall on the Wrong People

The false arrest cases matter because they reveal something crucial about how this technology actually functions in practice. Flock’s license plate recognition is not perfectly accurate. The company doesn’t claim it is. But police departments, when they receive an alert, often treat it as a lead rather than as definitive evidence. An officer sees a match and pulls over a vehicle. The driver is detained. A background check runs. Sometimes the error is caught immediately. Sometimes it isn’t. Sometimes the person is arrested, booked, and only later exonerated when a human investigator realizes the plate match was wrong.

That’s a cost borne by the person who was misidentified, not by Flock or the police department that relied on the match. There’s no compensation mechanism. There’s no legal liability for false identification. The technology is treated as a tool, not as a decision-maker, which means the errors it produces are classified as human error—the officer should have verified the match more carefully—rather than as systemic failures of the platform itself. This accountability gap mirrors the dynamics explored in our analysis of cloud security failures, where the costs of institutional data mismanagement are routinely displaced onto individuals rather than the organizations responsible for the infrastructure.

What Comes After the Vote?

The South Carolina town’s decision to install more cameras than officers suggests a particular vision of public safety: one where algorithmic surveillance is cheaper and more scalable than hiring police. That’s not wrong as an economic calculation. But it’s a choice with consequences that residents may not fully understand until they experience them. Until they’re pulled over because their vehicle matched a flagged plate. Until they discover that their movements have been tracked and recorded. Until they realize that the infrastructure for that tracking is now permanent.

The vote is done. The cameras are coming. What happens next will depend on whether residents continue to push for transparency about how the system is being used, whether they demand access to their own data, and whether they hold their police department accountable for how the Flock alerts are being acted upon. Those are the questions that should have been asked before the vote. They’re urgent now.