The debate over automated license plate readers has arrived in St. Paul, Minnesota, with a clarity that cuts through the usual political fog. City Council President Rebecca Noecker is leading a charge to end the city’s contract with Flock Safety, a company whose cameras dot roads across America. Her concern is straightforward: the pervasive collection and sharing of personal data. Yet, standing opposite her are local law enforcement officials who call that notion misinformation, arguing the technology is a crucial tool for solving crimes. This isn’t just a local policy tiff; it’s a microcosm of a national struggle to balance public safety against personal privacy in an era of ubiquitous surveillance.
At the heart of the issue are two cameras owned by the St. Paul Police Department, positioned at Kellogg Boulevard and Smith Avenue. Jeff Potts, executive director of the Minnesota Police Chiefs Association, describes their function in simple terms. “It’s really just a picture of the license plate at a particular time and date,” he says. That image also typically includes the vehicle’s make, model, and color. Potts is quick to add, “That system itself does not collect any of the vehicle owner or driver data.” The data from these cameras is stored locally in St. Paul, not in a corporate cloud. Flock’s official stance reinforces this point: whoever owns the camera owns the data.
But ownership doesn’t imply isolation. This is where Noecker’s concerns gain traction. While St. Paul owns its data, police departments can—and frequently do—share that data with other jurisdictions. This creates a vast, interconnected web of vehicle movement records. The practice is governed by Minnesota state law, which mandates data be deleted after 60 days unless part of an active investigation and requires system audits every two years. Yet, the rules governing sharing are far less uniform, often left to the discretion of individual police chiefs.
A look at other Minnesota cities reveals a patchwork of policies. The city of St. Louis Park operates a public Flock Transparency Portal, a level of openness Flock offers but does not require. Their portal shows 16 cameras detected over 400,000 vehicles last month. Officers conducted 76 manual searches, and the system generated alerts for “hotlist” hits, which include stolen vehicles or Amber Alerts. St. Louis Park limits data sharing to other Minnesota jurisdictions but receives data from as far away as Fort Worth, Texas, and from private companies like Home Depot. In contrast, the Faribault Police Department shares its data only with local dispatch. St. Paul’s own portal is less detailed but indicates it shares data solely with other Minnesota departments.
| City | Data Sharing Policy | Notable Features |
|---|---|---|
| St. Paul | Shares data solely with other Minnesota departments | Less detailed portal |
| St. Louis Park | Shares data with other Minnesota jurisdictions | Operates a public Flock Transparency Portal |
| Faribault | Shares data only with local dispatch | N/A |
This inconsistency is the problem, privacy advocates argue. The technology’s value for law enforcement is demonstrable. There are two primary uses: manual searches by trained officers and automatic alerts to patrol cars for “hotlist” hits. These hits can help locate missing persons, recover stolen cars, and apprehend individuals with active warrants. Each successful recovery is a powerful anecdote for keeping the cameras. However, the sheer scale of data collection—hundreds of thousands of plates per month from just one small city—creates a permanent record of ordinary citizens’ movements, a digital trail ripe for potential abuse or mission creep without robust, uniform safeguards.
The special public meeting scheduled at St. Paul City Hall is where these abstract concerns meet civic reality. Residents will weigh in on a fundamental question: does the investigative utility of tracking every vehicle outweigh the privacy risk of creating a searchable database of everyone’s comings and goings? The council’s vote remains uncertain. They could vote to sever ties with Flock, a symbolic blow to the surveillance industry. They could seek to amend the contract with stricter data-sharing prohibitions. Or they could uphold the status quo, trusting the existing state laws and departmental discretion.
As a political correspondent, I’ve observed these debates from Washington to city halls nationwide. They rarely offer perfect solutions. The data shows these cameras can solve crimes. The principle shows they can quietly erode a reasonable expectation of privacy. What happens in St. Paul this week will be decided not by a sweeping federal mandate, but by local officials listening to their constituents, weighing imperfect evidence, and making a choice about the character of their community’s public space. The outcome will be a telling indicator of which scale—security or privacy—currently carries more weight in the heart of the Midwest.
