Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Automated Enforcement topic
No spam. Unsubscribe anytime.
Ordinance committee reviews draft authorizing speed and red-light cameras; privacy and vendor questions prompt vendor briefing at next meeting
Summary
The committee reviewed a draft ordinance authorizing the use of speed and red-light cameras under state law, discussed data-retention and privacy safeguards, and agreed to hold a public hearing and invite a vendor to brief the committee at its April 15 meeting.
The Norwalk City Ordinance Committee on March 18 reviewed a draft ordinance authorizing the city to use automated enforcement devices (speed and red-light cameras) under Connecticut statute and agreed to continue detailed consideration in April with vendor briefings and public outreach planned.
Tom (staff) introduced the draft, noting similar ordinances in Stamford, New Haven, New London and other municipalities and said the draft largely mirrors state law and other municipal ordinances. “One of the first conditions is that the municipality adopt an ordinance,” he told the committee; the Connecticut Department of Transportation (CT DOT) must approve specific camera locations before any devices can be installed.
Why it matters: Automated enforcement targets speed and red-light violations in school zones, pedestrian safety zones and other high-crash locations. Staff said revenues generated by the program must be reinvested in transportation safety improvements and the program can be structured to be revenue-neutral to the city.
Privacy, data retention and vendor controls: Committee members raised questions about personally identifiable information, data retention timelines and vendor practices. Nora asked whether independent privacy reviews would be required and who would verify that vendors destroy non-violation images. Garrett (staff) said Connecticut law requires data used to issue citations to be destroyed 30 days after payment or adjudication and that imagery captured without a violation is subject to strict limitations; he also said the city would include privacy and storage requirements in any RFP/RFQ.
Process and next steps: Staff described a multi-stage implementation process: (1) adoption of a municipal ordinance; (2) procurement of a vendor through RFQ/RFP; (3) development of a comprehensive plan and public meeting(s) on chosen locations and equity considerations; (4) submission to CT DOT for approval. The committee asked staff to invite a vendor to the April 15 meeting to explain technical, privacy and data-disposition practices.
Committee action: Committee members agreed to bring the ordinance and a vendor briefing to the April 15 meeting for a more detailed public hearing and discussion.
Ending: Staff emphasized the multi-step, data-driven process; committee members requested vendor transparency and stronger public outreach as part of future steps.
