Documented Incident

Cities RejectingLegislationPublic OppositionPrivacyConnecticut

Milford, CT aldermen approve moratorium on speed cameras and new license plate readers

Milford's Board of Aldermen voted 9-5 along party lines to impose a moratorium on the use and installation of Automated Traffic Enforcement Safety Devices, including red light and speed cameras, following a public hearing attended by more than 200 residents, most of whom spoke against the technology. The resolution also directs Mayor Richard Smith to create a traffic safety and review committee, with the majority and minority leaders included as members by an approved amendment. The city currently has roughly 70 Flock Safety license plate readers and cameras plus six school-zone speed cameras. The mayor had announced on Aug. 26 that he would recommend suspending operational use of the enforcement devices and restricting ALPRs except those at the city's entry points.

Why this matters

Milford paused an already-installed surveillance and automated enforcement program rather than blocking a new one, showing that deployments can be revisited after the fact when residents press for oversight. The review committee's mandate — covering camera locations, fines, hearing procedures and data practices — offers a template other municipalities may follow.

Key facts

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

More from Connecticut

Everything we have documented in Connecticut, or search every Connecticut article in the archive.

About this record

BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.

Updated August 31, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.