Dayton, Minnesota officials say they were caught off guard when a Flock maintenance work order surfaced on September 17, 2026, months after the city had turned down the surveillance camera vendor. The disclosure, posted by the local government on Facebook, has reignited scrutiny of how automated license plate readers reach American streets.
How a Rejected Vendor Left a Work Order Behind
The city of Dayton posted on Facebook that its Police Department was made aware of a maintenance work order produced by Flock on September 17, 2026. The timing is notable because Dayton had already declined to move forward with the camera program.
The disclosure did not specify whether any cameras were installed or whether the work order was tied to existing infrastructure. City officials framed the notice as an alert to residents rather than a confirmation of active surveillance.
Flock has not publicly detailed the scope of the Dayton work order. The company's cameras are widely deployed in Minnesota and other states, which complicates the picture for cities trying to track vendor activity within their borders.
Why Vendor Transparency Is Becoming a Local Political Issue
Dayton's experience fits a broader pattern in which municipalities are learning about surveillance vendor activity after the fact. Procurement records, maintenance tickets and service requests can move through channels that elected officials and residents do not closely monitor.
For local governments, the challenge is not only whether to approve a technology but also how to verify that a rejected vendor is not quietly maintaining a presence. That gap has become a flashpoint in cities weighing public safety benefits against civil liberties concerns.
Civil liberties advocates have argued that license plate readers create searchable movement histories that can be accessed far beyond the city that installed them. Cities that reject the technology often cite those concerns alongside cost.
The Wider Pattern Behind Flock's Expansion
Flock has become one of the most visible names in automated license plate recognition, with contracts spanning hundreds of police departments. Its growth has made the company a focal point for debates over surveillance, data retention and interagency sharing.
The Dayton episode is unlikely to be the last of its kind. As more cities debate camera contracts, residents and officials are paying closer attention to the paperwork that follows a rejection.
Why This Matters
The Dayton disclosure changes the practical question for local officials. It is no longer enough to vote down a surveillance contract. Cities now need to verify that vendor activity has actually stopped, which means auditing maintenance records and service requests.
For residents, the implication is direct. A city's rejection of Flock cameras may not guarantee that the company has no operational footprint in the community. That uncertainty is likely to push more municipalities toward stricter procurement language and public reporting requirements.
For Flock, the reputational stakes are rising. Each episode in which a city discovers unexpected vendor activity gives critics a concrete example to cite in future contract debates.



