An opinion piece in The Atlantic makes a blunt case: localities should ban Flock and its competitors until regulation better protects people from mass surveillance. The argument, published in the magazine's newsletter, lands at a moment when a Flock license plate reader surveillance ban is a live question in many communities, and it frames the issue as one local governments can act on now rather than waiting for Washington.
This post looks at what the Atlantic argues, why plate-reader networks matter for ordinary drivers, and what cities and residents can realistically do.
What the Atlantic Argues About Flock and Its Competitors
The piece's core claim is simple. Until stronger rules exist, cities should not operate or contract with Flock or rival automated license plate reader (ALPR) networks. The headline, "Make Big Brother Bad for Big Business," signals the strategy: if local governments stop buying these systems, the commercial incentive to build ever-larger surveillance networks weakens.
It is an opinion column, not a news report, so it presents a policy position rather than new investigative findings. The argument is also notable for what it targets. It is not only aimed at one vendor but at the whole category of competitors, which suggests the concern is the business model of networked, searchable location data rather than a single company's practices.
How Plate-Reader Networks Track Ordinary Drivers
An ALPR camera photographs passing vehicles and converts the plate into searchable text, usually with a timestamp and location. One camera tells you little. Hundreds or thousands of cameras, linked into a shared system, can show where a vehicle has been over time.
That is the privacy concern in plain terms. Most drivers captured by these systems are not suspected of anything. Their routine trips, such as commuting, visiting a clinic, attending a place of worship, or dropping children at school, can become entries in a database. Critics argue that this kind of broad, warrantless collection amounts to mass surveillance, a view that has fueled pushback in many places, as reported by outlets such as the Associated Press.
The legal and policy questions that follow are practical ones:
- How long is the data kept?
- Who can search it, and for what reasons?
- Is a warrant or documented justification required?
- Is data shared with other agencies, including those outside the community?
- Is there an independent record of every search?
Where answers are vague, the risk of misuse grows, which is why advocates focus on rules rather than only on the technology.
What Cities Can Do Before Federal Regulation Arrives
The Atlantic's central point is that local governments do not need to wait. Cities and counties control their own procurement, and that gives them real leverage.
Options include:
- Pause or end contracts. A council can decline to renew an ALPR agreement or vote to remove existing cameras.
- Require public approval. Many places allow police to buy surveillance tools without a council vote. An ordinance can require open debate and a vote first.
- Set conditions in writing. If cameras stay, contracts can include strict limits on retention, sharing, and permitted uses.
- Publish transparency reports. Regular public reporting on how many searches occur, and why, gives residents something to evaluate.
Reporting on the wider debate points to a patchwork. Florida, for example, recently revoked the ability of local police to place plate readers on state highways, though that is not a statewide ban on the cameras. A federal bill dubbed the Ban Flock Act has also been proposed to stop federal agencies from using ALPRs. These moves show the issue is active at several levels of government, while leaving most decisions to individual localities.
Safeguards Residents Should Push For
A ban is one outcome, but not the only one residents may want. If a community keeps plate readers, these safeguards are worth demanding:
- Short retention limits. Data on vehicles not tied to an investigation should be deleted quickly.
- Warrant or clear-cause requirements for searching historical location data.
- Audit logs that record every search and are reviewable by an independent party.
- Sharing restrictions that limit access by outside agencies.
- Public contracts so residents can read the terms rather than rely on summaries.
- Penalties for misuse that are real and enforced.
Privacy and public safety are often presented as opposites. The more useful framing is that strong rules let a community make an informed trade-off. A similar tension appears in other legislation, such as the KOSA debate over child safety and privacy, where well-intentioned goals can collide with privacy concerns.
What This Means For You
A VPN does nothing about a camera pointed at your license plate. Plate readers capture what is visible on public roads, so this is a civic issue more than a personal-tech one. The most effective tools are local: council meetings, public records requests, and votes.
If you drive, your movements may already be recorded by systems you never agreed to. Whether that data is kept for days or years, and who can search it, is often decided by a contract most residents have never seen.
Takeaways
- Find out whether your city or county uses Flock or a competing ALPR network by searching council agendas and public contracts.
- Ask your council to require a public vote before any surveillance purchase.
- Push for retention limits, audit requirements, and sharing restrictions, whether or not your community considers a Flock license plate reader surveillance ban.
- Attend a meeting or submit written comments; local officials often hear from very few residents on these topics.
The Atlantic's argument is that local pressure can change the market. Checking your own community's contracts is a practical first step.
