A Milwaukee case exposes the dark side of the surveillance infrastructure quietly spreading through American neighborhoods.

There's a pitch that sounds pretty reasonable on the surface. A company called Flock Safety installs sleek, solar-powered cameras throughout your neighborhood. They read license plates. They help police catch car thieves, find missing persons, and solve hit-and-runs. Your HOA might even foot the bill. What's not to like?

Here's what's not to like: in February 2026, a Milwaukee police officer was charged with using Flock's license plate reader (LPR) network to track the movements of his ex-girlfriend and her new partner. Not for any investigation. Not under any warrant. He allegedly used a law enforcement surveillance system one marketed as a community safety tool to conduct a personal stalking campaign.

This case isn't just about one bad actor with a badge. It's a warning sign about the surveillance architecture we're allowing to be built around us, often without fully understanding who has access to the data, how it's being used, or what happens when that access is abused.

The Milwaukee Case: A Textbook Abuse of Power

The details of the Milwaukee case are disturbing precisely because they're so predictable. According to charges filed in late February 2026, a police officer allegedly used his department's access to Flock's camera network to monitor where his ex-girlfriend's vehicle was showing up and when. He reportedly did the same with her ex-partner's vehicle.

This wasn't a case of an officer stumbling across information in the course of legitimate duties. This was, prosecutors allege, a deliberate and sustained misuse of surveillance tools for personal purposes purposes that meet the legal definition of stalking.

In practice this means without ever physically following someone, without hiring a private investigator, without planting a GPS tracker (which would itself be illegal without a warrant), this officer could allegedly sit at a computer and pull up a detailed log of another person's movements across the city. Where she went. When she went there. How often. Whether another specific car was nearby.

The surveillance infrastructure made it trivially easy.

The Access Problem Nobody Wants to Talk About

Flock Safety will point out that the company has audit logs and policies in place. Flock's system does record which officers search for which plates, and the company says it encourages agencies to adopt strict use policies. When cases like Milwaukee come to light, the system's logging capabilities are often what help build the case against the offending officer.

But this defense "we can catch them after they abuse the system" misses the point in a fundamental way. Deterrence through after-the-fact accountability is not the same as prevention, nor does it help when accountability isn't delivered. By the time an audit log reveals that an officer has been tracking his ex-girlfriend's car for weeks or months, the harm has already been done. The victim's sense of safety has already been shattered. The stalking has already occurred, nor was it stopped.

And audit logs only matter if someone is actually reviewing them. Routine audits of database queries are, in many departments, more theoretical than actual. The Milwaukee case raises an uncomfortable question: how many other officers, in how many other departments, are running personal searches that nobody is catching?

The problem is structural. When you build a system that gives thousands of individual officers easy, low-friction access to detailed movement data on millions of people, some percentage of those officers will abuse that access. It's a statistical certainty, borne out by decades of documented misuse of every law enforcement database from the FBI's NCIC to state DMV records. Researchers have a name for it: "LOVEINT," a play on intelligence community jargon, referring to officers who use surveillance tools to spy on romantic interests.

The Private Surveillance Pipeline

What makes Flock cameras particularly concerning is the way they blur the line between private and public surveillance. Many Flock cameras aren't installed by police departments at all — they're installed by HOAs, business improvement districts, and private property owners. But the data frequently flows to law enforcement through data-sharing agreements.

This creates a troubling end-run around the kind of oversight that would normally apply to government surveillance. A city council might debate and vote on whether to install a police-operated camera network. But when an HOA in a gated community installs Flock cameras and then shares the feed with local police, that democratic check largely disappears. Residents of the surrounding area people who drive past those cameras on public roads often have no idea the cameras are there, no say in their installation, and no knowledge that their movements are being tracked and stored.

The result is a patchwork surveillance network that is vast, growing, and operates in a regulatory gray zone. Flock reportedly has cameras in more than 5,000 communities across the United States. Stitch those networks together, and you have something approaching a national vehicle tracking system assembled not through any single government decision, but through thousands of individual sales pitches to nervous neighborhood associations.

"If You Have Nothing to Hide..."

Whenever surveillance concerns come up, someone inevitably trots out the old line: "If you have nothing to hide, you have nothing to fear." The Milwaukee case is a perfect rebuttal.

The officer's ex-girlfriend had nothing to hide. She was simply living her life — driving to work, running errands, maybe visiting a friend. She wasn't a suspect in any crime. She was a private citizen whose movements were captured by a system she probably didn't know existed, stored in a database she certainly never consented to, and accessed by someone who had no legitimate reason to look.

The "nothing to hide" argument assumes that surveillance data will only ever be used for its intended purpose, by trustworthy people, under proper oversight. The Milwaukee case demonstrates — as case after case has demonstrated before it — that this assumption is naive. Surveillance systems don't just get used for their stated purpose. They get used for whatever purposes the people with access decide to use them for.

What Can Be Done?

This isn't a call to abolish all technology in policing. License plate readers can be genuinely useful investigative tools. But usefulness doesn't exempt a technology from oversight, and the current framework around Flock cameras and similar systems is alarmingly thin.

There are several reforms worth pushing for. First, data retention limits matter enormously — there's a significant difference between a system that stores plate reads for 30 days and one that stores them for a year or indefinitely. Shorter retention windows limit the depth of retroactive surveillance that's possible. Second, access controls need to be tightened so that officers can only query the system in connection with active, documented investigations rather than running open-ended searches on any plate they choose. Third, communities deserve transparency and democratic input before these systems are installed, whether by police departments or by private entities that share data with law enforcement. Fourth, independent and regular audits of system access should be mandatory, not optional, with real consequences for misuse.

State legislatures are beginning to pay attention. Some jurisdictions have introduced bills requiring warrants before law enforcement can access ALPR data, mandating data retention limits, or requiring public notice before cameras are installed. But legislative action has been slow relative to the speed at which Flock's network is expanding.

The Bigger Picture

The Milwaukee officer's arrest is, in one sense, a system working. He was caught. He was charged. But zoom out, and the picture is far less reassuring. The system that enabled his alleged stalking is still in place. It's still growing. And the fundamental dynamics that made the abuse possible — broad access, minimal real-time oversight, massive data collection on non-suspects — haven't changed.

Every community considering a Flock camera installation, every HOA board entertaining a sales pitch, every city council weighing a contract should be asking a simple question: Who has access to this data, and what's actually stopping them from misusing it?

Because a stalker with a badge and a database is far more dangerous than a stalker with a pair of binoculars. And we're building the infrastructure that makes it possible, one camera at a time.

What you can do today: Find out whether Flock cameras or similar ALPR systems are operating in your community by checking https://deflock.org/. Attend your next city council or HOA meeting and ask about data-sharing agreements with law enforcement. Support state-level legislation that requires warrants, retention limits, and transparency for automated license plate reader data.