Minneapolis Votes 9-4 to Seek End of Two Flock Contracts but Cannot Terminate Them

Minneapolis has formally called for two public agencies to end their Flock Safety license plate camera contracts, but the city cannot switch off the cameras or cancel the agreements. On Oct. 1, the City Council voted 9-4 for a nonbinding resolution directed at the Hennepin County Sheriff’s Office and the University of Minnesota, according to the city’s official council bulletin. The two institutions retain authority over whether their arrangements continue, change or end.

That split between political objection and operational control is the central systems issue. Minneapolis does not own or operate Flock cameras, so its resolution authorizes the city’s intergovernmental-relations director to send the request rather than ordering a shutdown. The council can increase public and institutional pressure, but the agencies controlling the equipment, access policies and contracts make the final decisions.

Flock’s automated license plate readers photograph passing vehicles and make plate information available for law-enforcement searches. A roadside image is only the first layer of the system. Once observations are retained and made searchable, investigators can use records from different times or cameras to reconstruct portions of a vehicle’s travel history.

This distinction changes the policy question from whether a plate is visible on a public road to how vehicle observations are aggregated, retained, shared and searched. The practical controls include which personnel receive accounts, whether a search requires a documented investigative purpose, how long records remain available, which outside agencies can gain access and whether audit logs are actively reviewed.

The resolution’s authors have framed the issue in civil-rights and data-protection terms. Council Member Robin Wonsley wrote before the vote that residents opposed the cameras and described them as being operated by companies that do not protect resident data and civil rights. Those are the council member’s criticisms; the two agencies have presented continued access as a public-safety capability.

The University of Minnesota Police Department says it uses the technology “for limited public safety purposes only” and prohibits its use for immigration enforcement. The university credits the cameras with helping recover stolen vehicles, locate missing people and track violent-crime suspects. It also said it would remove a recently installed West Bank camera in an effort to support community trust while maintaining safety coverage.

The Hennepin County Sheriff’s Office has taken a firmer position on continued access. Its spokesperson said the Criminal Intelligence Division needs the Flock network for investigations and noted that the Minneapolis council does not set county public-safety policy. The result is a direct institutional tradeoff: removing access reduces the availability of a vehicle-search tool, while retaining it preserves concerns about how broadly historical location records can be queried.

An Oct. 1 federal ruling illustrates why search controls, rather than photography alone, are drawing legal attention. In United States v. Kyle, U.S. District Judge Sara E. Hill found that a deputy violated a woman’s Fourth Amendment rights by searching historical vehicle-location information without a warrant. Hill suppressed evidence obtained after the search and characterized it as “indiscriminate mass surveillance.” The decision addresses that search’s circumstances; it does not ban Flock cameras nationwide or bind courts across the country.

Technical safeguards can narrow access and improve accountability, although policies vary by agency. Richfield police say their department retains data for 30 days, assigns individual user accounts, requires a second authentication step and permanently logs every search. The department also says it passed its last two state-required audits. Shakopee police say they publish a public search audit and use an internal function intended to flag potentially concerning search patterns.

Those controls illustrate a layered governance model: limited retention reduces the historical window, individual credentials tie activity to a user, authentication makes account misuse harder, and permanent logs provide records for review. None determines by itself whether a search is legally justified. Effective oversight also depends on clear authorization rules, routine audit review and consequences when access falls outside policy.

Agency-specific safeguards cannot be assumed to apply across the entire Flock network. Different retention periods, sharing configurations and audit practices mean that two jurisdictions using similar cameras may create materially different privacy and access conditions. A National Policing Institute evaluation notes that license plate reader effectiveness depends on implementation and that relatively few rigorous studies have established public-safety outcomes or privacy best practices.

Minnesota communities are already reaching different conclusions. St. Paul called for city and county contracts to end, Plymouth discontinued its cameras, and Duluth declined to renew a contract that expired Sept. 7. Minneapolis has now added a recorded 9-4 objection, but the next consequential decisions remain with the Hennepin County Sheriff’s Office and the University of Minnesota the institutions that control the two contracts and the associated access to searchable vehicle-location records.

By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.