OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

Danbury Ad Hoc Committee on ATESD Privacy Policy - July 14, 2026

Meeting PortalTuesday, July 14, 2026
BodyDanbury, Connecticut
SessionMeeting Portal
DateTuesday, July 14, 2026
StatusNEW · FILED
Video Record

STREAMING COPY IN PREPARATION — RECORDING AVAILABLE FROM THE ORIGINAL SOURCE

Transcript — Verbatim
0:00

Are you five?

0:01

I'm gonna get this ad hoc started.

0:03

Uh this ad hoc uh officially starting at 6.05 p.m.

0:08

is the adoption of the privacy policy for the automated traffic enforcement safety devices.

0:16

My name is Frank Salvatore.

0:18

I'm the chair with me.

0:19

I have Cheryl Wallace Smith and Candace Faye, the two uh city council persons who are on the ad hoc.

0:27

We have uh Deputy Chief Sturdevant here.

0:30

We have Tot O'Brien from the mayor's office.

0:34

We have Robin Edwards and Caitlin Grace from the Corporation Council.

0:40

In the room, we also have ex officio members, uh President Peter Bazade and Paul Rotello and uh members of the community.

0:50

Did I miss anybody?

0:53

See if I don't have my glasses on, I don't I don't see.

0:55

So I don't miss anybody.

0:56

Okay.

0:57

So we're going to start off by asking corporation counsel to do a presentation because actually this uh ad hoc and the next ad hoc are kind of linked together.

1:10

But we wanted to do the privacy policy first because that's uh probably the easiest one to go through before we get to the ordinance for the cameras.

1:19

So ladies, you have the floor.

1:22

Thank you.

1:22

Thank you, Mr.

1:23

Salvatore.

1:24

Good evening, everyone.

1:25

And I just have a few opening comments, and then we're going to we have a PowerPoint presentation for you this evening that actually covers the privacy policy as well as the ordinance, and we'll walk you through a few slides until we get to the privacy policy, and then we can stop and answer any questions that you have.

1:42

But just by way of brief background information, this ad hoc is convened for the purposes of discussing the privacy policy.

1:50

And the privacy policy, as Mr.

1:52

Salvatore just pointed out, is to be adopted if an ordinance that provides for the use of automated traffic enforcement safety devices, ATE, SDs, as are known.

2:05

Um also people call them red light or speed cameras, is adopted by the city.

2:11

Um by way of very brief background information.

2:15

In 2023, the state of Connecticut enacted a public act, which is now codified, and it's enabling legislation that provides for allowing towns and cities to employ these devices.

2:29

Approximately 15 cities and towns throughout the state have adopted ordinances that provide for this at this time, and um which were actually approved by DOT.

2:41

There are five currently under consideration.

2:45

Adoption of such an ordinance represents a shift in traffic management.

2:50

You don't need to rely solely on police patrols.

2:53

Um the use of these devices provides for a more uniform oversight of high-risk areas.

2:59

The goal is to reduce crashes, injuries, and fatalities by using these devices to monitor and enforce the running of red lights and speed in excess of 10 miles per hour over the posted speed limit.

3:13

And you know, it's to improve traffic in school zones, pedestrian zones, and other high areas where there are safety concerns.

3:22

So the process begins tonight with the adoption of an ordinance and the privacy policy, which is required to be adopted as part of that.

3:32

And that's what we'll focus on tonight.

3:35

So at this point, we can turn to our PowerPoint presentation, and Caitlin will run you through the first few slides.

3:43

Um we hope it will be informative for you.

3:49

Okay.

3:50

Public Act 23116, which was codified as Connecticut General Statute sections 14307B through 1430H, allows municipalities to use ATSD, which is automatic traffic enforcement safety devices at locations within school zones, pedestrian safety zones, and other locations in such municipality.

4:12

As long as they adopt four specific things.

4:15

So first, it's the adoption of an ordinance in accordance with the statute's requirements.

4:20

Second is the adoption of a model privacy policy in accordance with the statutes requirements.

4:24

There also needs to be an adoption of a comprehensive safety action plan, which is currently being drafted by our planning and zoning department.

4:32

And a plan drafted by the Danbury Police Department and the city traffic engineer, which has to be approved by the Connecticut Department of Transportation.

4:40

An automatic uh automatic traffic and enforcement safety device.

4:44

And if I will for the rest of the presentation be calling it an ATESD device.

4:50

Um, those are two things.

4:51

So they're either a red light camera or a speed camera, which are used interchangeably throughout the statutes.

5:00

And we're currently focusing this evening on the first two steps.

5:04

So what is an ATSD?

5:05

It's defined in Section 14307B1 of the state statute, which means a device designed to detect and collect evidence of alleged violations of an ordinance adopted under Section 14307C by recording images that capture the number, the license plate, date, time, and location of a motor vehicle that either exceeds the posted speed limit by 10 or more miles per hour, or fails to stop their vehicle when facing a steady red signal at a traffic control signal.

5:40

So disclosure of personally identifiable information.

5:43

So personally identifiable information, which is PII is defined under Section 14307B6 of the Connecticut General Statutes, and it's also defined in our ordinance definition section.

5:57

And this is information created or maintained by the city or a vendor that identifies or describes a motor vehicle owner.

6:05

This includes the owner's address, phone number, license plate, their photograph that was taken, bank account information, credit card number, debit card number, or the date, time, location, or direction of travel on a highway.

6:19

PII cannot be disclosed by the city or a vendor to any person or entity, including law enforcement units.

6:26

The only law enforcement officers who should have access to PII are trained operators if they are trained as an operator or a designated employee of the police department who is set up to review and approve the recorded images that are produced by the ATSD device vendor or operator.

6:45

No PII should be stored or retained by the city or a vendor unless such information is necessary for the charging collection and enforcement of the fines.

6:55

And the city or a vendor shall destroy all PII that identifies a motor vehicle and relates to a violation not later than 30 days after any fine is collected, or the resolution of a hearing conducted for the alleged commission of such violation, whichever is later.

7:14

As know that previously a municipality must destroy PII no later than 30 days after a fine is collected or a hearing is concluded, but there is one exception to this time window to destroy the PII, and that's for the limited purpose of determining whether or not a person committed a second or subsequent violation of the municipal ordinance.

7:33

This is referred to in ordinance section 4644.

7:37

So the municipality city or a vendor shall destroy the PIA not later than one year after the date of such person's most recent violation.

7:46

Pursuant to Connecticut General Statute 407, I mean 1430G at the minimum, the city is required to report annually the number of motor vehicles that were subject to one citation, two citations, three citations, or four or more citations.

8:02

If the city fails to report on the data, any ATSD location as required by 14307G, the state will decline to reauthorize the ATSD location once the plan has expired.

8:16

So without this data, the city will not be able to maintain the use of the ATSD devices because we would not meet the statutory requirements.

8:24

Additionally, any information or other data gathered from an ATSD device shall be subject to disclosure under FOIA as defined in CGS section 1200, except that no PII may do be disclosed.

8:39

What would you actually get?

8:42

Like what you can't get the time, date, location, what is it?

8:45

So you would get most likely the data of what we're collecting of how many citations are being given, but we can't give any information of who the citation was given to, anything that would identify the vehicle or that person.

8:59

Like the effectiveness of the camera or how many.

9:02

You can kind of get aggregate data.

9:04

Like so many people are stopped at this line.

9:06

Okay, which is all publicly available ultimately, anyways, through the state.

9:10

Yes, yes.

9:12

Okay.

9:13

That is so.

9:14

So that's the slide on the PII.

9:18

So that's what's before us tonight.

9:19

And so you have before you the personal privacy policy that was sent to you and was a part of our packet to the council.

9:28

It's been updated.

9:28

You know, we added some language to it.

9:31

So that's what uh the focus is on tonight.

9:34

So if you're inclined to adopt the ordinance, we would ask that you adopt this as well, hand in hand with it.

9:42

And this personal privacy policy, just so you know, this language comes directly from the state.

9:47

We're required to adopt a privacy policy that meets the state's requirements or is stricter than the state's policy, and it comes right out of their manual.

9:57

And a lot of it comes out of the statute.

10:00

They have a few other things they've added for additional protections, and that's that's really what's here.

10:07

So we're happy to answer any questions you might have.

10:11

It's fairly self-explanatory, I think.

10:15

I'm sorry, there's no public speaking here.

10:17

Sorry, can let me keep it at the table here first, please.

10:22

Um for purposes of this uh ad hoc.

10:27

Um, they did go over some topic stuff about the ATSD that isn't PII focused, but it's starting to lead into the next one.

10:36

So just on the PII only.

10:40

Um basically it's a policy, it's not an ordinance that we will approve a resolution to adopt the policy.

10:49

Yes.

10:50

It is taken directly from the not only the state statutes have a lot of this language that's in here, but it is also part of the the guidelines to start it, correct?

11:02

Yes, it's from the state policy manual.

11:04

That's where it comes from.

11:05

So we've copied we've copied the state's privacy information, so it's pretty stringent to begin with.

11:15

Yes, we've yes.

11:16

Okay.

11:17

All right.

11:18

I don't have any questions.

11:20

I'll open it up to my fellow council persons.

11:23

I I don't have any questions.

11:24

I did speak with corporation counsel yesterday, and it does appear to track very closely with what the state has instructed us to do.

11:33

So I don't think I don't have any questions either.

11:39

It seems like we pretty much copied what the state said.

11:42

So there's not really room to wiggle.

11:46

We took what they provided.

11:48

Right.

11:49

So I'm I'm pretty sure.

11:51

You agree with that?

11:52

Okay.

11:53

Mayor's office.

11:58

I'm sorry.

11:59

Uh ex officio members.

12:01

I I do have a question.

12:02

Um, so so going forward, assuming the original steps are all followed and we get to the point where we're gonna have a contract with a vendor.

12:10

Yes.

12:11

Uh these vendors are approved by the state already.

12:14

Is it is that how this works?

12:18

I think it's our plan is.

12:19

I don't know if they're approved by the state, but there are vendors okay.

12:24

And and this this part of this contract would include reference to the policy that you're asking that we're asking the council to adopt.

12:31

Absolutely.

12:32

Okay, yes.

12:33

I have no other questions.

12:35

Okay.

12:36

Any other ex officios?

12:38

Oh, you got anything?

12:40

You know, I do, but I don't I don't know if this is the proper venue, but I'll just put it out there anyway.

12:45

I I noticed that no PII can be held for more than a year, basically under those circumstances.

12:52

So it can be held up to a year, and obviously if there's another violation nine or ten months later, it can be held for another year after that.

13:00

So if you do a California stop a couple of times, you could wind up having your data held for several years.

13:08

And then the other issue is uh I'm not really worried about the state of Connecticut or the city of Anthro surveilling its own constituents, but I'm very worried about the federal government doing that, especially now.

13:19

It's getting worse.

13:21

There's nothing in here that would prevent the federal government, which trumps the state government from subpoenaing this data or taking it by other means.

13:29

Flock is doing that now.

13:30

Los Angeles just cancel all their contracts with Flock because Flock is giving their information without LA's permission to the Fed.

13:39

There's nothing here that would protect protect the data of our constituents from any intrusion by the federal government, as far as I can see.

13:46

We're not I don't think the state of Connecticut is really the city of Danbury is not prepared to stand up to Washington to prevent that.

13:55

So my guess is once it's collected, and if somebody else wants it who is more powerful than us, which is just about everybody, they can just get it.

14:04

I just want to make sure that that this data is not in a format that would prevent anybody else from getting it.

14:12

Basically, if the federal government wants it, they can get it.

14:15

So that just let me know if I'm I'm on the right track on that.

14:19

Thank you.

14:21

I know I mean, so one of my notes was you know, like they in the statute, there's no warrant exception.

14:27

However, everything's subject to a warrant search or a subpoena or anything like that.

14:32

So I don't I don't, even if the city wanted to, I don't know if there's any way to legislate around that.

14:36

And the only thing I would say is that these are maximums that the city can hold it, not minimums.

14:42

So this doesn't mean that we have to hold it for a year.

14:45

This is just by statute, the longest we can.

14:48

Our policy could go shorter if we wanted to.

14:52

I don't know that we need to do that tonight, but it's as we're considering these ordinances, we certainly could do less than what's required by the state statute in terms of destruction of evidence.

15:03

You could.

15:04

I think you'd have to work with it and see how it works.

15:06

Right.

15:06

Do we need that?

15:07

Right.

15:07

But yes, that's a point well taken.

15:09

Also, something that I do want to mention is the data that's being held for up to the maximum of one year.

15:17

That is only for the purposes of identifying if someone committed a subsequent offense.

15:22

And so it could be as simple as it's supposed to be for the limited purpose, it reads.

15:28

So that could be something as simple as someone's a license plate marker.

15:32

I mean, you they would have to have enough information to issue the citation for the So if Led Frank went through a red light, okay, and I got caught.

15:41

Yes.

15:42

And then I paid my fine, but the police department has no reasonable cause to suspect that I did something different as soon as I pay that fine, which would be through my bank account or my credit card.

15:54

So I see why that stuff's up there.

15:56

Um once I pay, though, 30 days later, that data's got to be scrubbed.

16:01

Except they have to keep some I some information to show that if you committed another offense within a year, it could be remarkably so it's only one year.

16:11

So they look at you in one year, right?

16:14

And um after that it's destroyed.

16:17

But that's the those are the guide rails is one year.

16:20

So if you do it, you know, 13 months later, the year starts over again.

16:26

Yeah, so yeah, but so that would be destroyed, you know, everything would be destroyed before that.

16:34

Okay, I I can think uh through the chair, of course, yeah.

16:37

I can think of instances where you would want law enforcement to get this information, right?

16:43

Suppose we have a tally and and the speed cameras caught it.

16:48

You would want the police department to able to execute a warrant to see what was happening, who was going that fast, right?

16:55

Who else was in the area, were there witnesses, any kind of information that a video footage would reveal.

17:00

Right.

17:00

In addition to that, if what's his name again?

17:03

Ledfoot.

17:04

Lead foot friend.

17:05

Led foot frame goes as Peter calls me.

17:08

Goes through a light doing 80 miles an hour by Connecticut state statute.

17:14

You're not allowed a police officer is not allowed to chase, correct?

17:18

Right.

17:18

But a camera can't catch that.

17:20

Catch that license plate going through that.

17:23

So it's yeah, yeah.

17:25

It right, they don't engage in pursuit, but they could still exactly so see the red car.

17:29

Lead foot Pete or whoever his name is.

17:32

You can change it to people.

17:33

That's fine.

17:34

Does that it also protects us that way as well, where we don't have to worry about a chase because this camera is gonna is gonna catch at least get a snapshot of it.

17:43

Okay, right, exactly.

17:45

Yeah.

17:45

So I think at this time we're probably good for a motion to uh recommend to the council to uh adopt the resolution which adopts the uh policy.

17:55

So moved.

17:56

The resolution as amended as amended as updating to next because we're gonna present this back this way, right?

18:03

To them.

18:04

So yeah.

18:05

Um motion to made a second to um ask the city council to approve the amended uh policy resolution, however.

18:19

And I would just say to adopt it simultaneously at the time the ordinance is adopted.

18:24

Understood without the ordinance, yeah.

18:26

We don't need the response.

18:27

Yeah, I will amend my motion to be ex uh acted on contemporaneously with you guys help Elisa with that when she's it's in the it's in the resolution.

18:38

It's in the resolution I take the resolution since uh whereas the adoption of city it adopts the ATESD privacy policy attached as exhibit A.

18:50

Um temporine have something right here.

18:57

Okay, yeah, you can do that.

19:02

So we're we're just redoing the motion.

19:04

I would withdraw my prior motion and I move to recommend the council approve the proposed privacy policy related to the use of ATESDs with addition of language to the last section regarding the retention of PPI as presented by corporation council said policy to be adopted concurrently with the ordinance uh that we're considering next.

19:24

Second.

19:25

Motion made second any remarks to that motion?

19:28

None all in favor say aye.

19:29

Aye.

19:30

Opposed, vote sowarded.

19:32

I'll entertain that motion to adjourn this ad hoc.

19:36

Next, maybe second all in favor say aye.

19:38

Aye.

19:39

Okay.

Discussion Breakdown — Share of Meeting
Transportation Safety█████████████████████████████████████████████86%
Public Safety████7%
Procedural████7%
Summary of Proceedings

Danbury Ad Hoc Committee on ATESD Privacy Policy - July 14, 2026

On July 14, 2026, the Danbury City Council Ad Hoc Committee on Automated Traffic Enforcement Safety Devices (ATESD) met at 6:05 p.m. to consider the adoption of a privacy policy required by state statute (Public Act 23-116, codified as CGS §§ 14-307b through 14-307h). The meeting was chaired by Frank Salvatore, with Council members Cheryl Wallace Smith and Candace Faye, Deputy Chief Sturdevant, Tot O'Brien from the Mayor's Office, and Corporation Counsel representatives Robin Edwards and Caitlin Grace. Ex officio members Peter Bazade and Paul Rotello also attended.

Presentation on Privacy Policy

Corporation Counsel presented a PowerPoint covering both the privacy policy and the underlying ordinance (to be considered separately). The privacy policy is mandated by Connecticut law as a prerequisite for deploying red-light and speed cameras in school zones, pedestrian safety zones, and other high-risk areas. The policy governs personally identifiable information (PII) collected by the devices, including license plate numbers, photos, dates, times, locations, and payment data. Key points:

  • PII cannot be disclosed to any person or entity, including law enforcement, except for trained operators or designated police employees reviewing citations.
  • PII must be destroyed within 30 days after a fine is collected or a hearing is resolved, whichever is later.
  • An exception allows retention of PII for up to one year from the most recent violation solely to identify repeat offenders.
  • The city must report annually the number of vehicles receiving one, two, three, or four or more citations; failure to report could result in the state declining to reauthorize camera locations.
  • Aggregate data (e.g., citation counts, effectiveness) is subject to FOIA disclosure, but no PII may be released.

Corporation Counsel noted that the policy language is taken directly from the state's model policy, ensuring it meets or exceeds statutory requirements.

Discussion Items

  • Statutory Compliance: Council members confirmed that the policy tracks state guidelines closely and leaves little room for deviation.
  • Data Retention and Federal Access: Ex officio member Paul Rotello raised concerns that the policy does not prevent federal government subpoenas or other demands for data, citing examples like Flock Safety sharing data without local consent. Corporation Counsel acknowledged that warrants or subpoenas could compel disclosure, and noted that the one-year retention period is a maximum, not a minimum—the city could adopt a shorter retention period. Chair Salvatore suggested that in some cases (e.g., serious speeding), law enforcement access via warrant could be beneficial.
  • Contemporaneous Adoption: It was clarified that the resolution to adopt the privacy policy would be effective only when the accompanying ordinance authorizing the cameras is also adopted by the full City Council.

Key Outcomes

  • The committee voted unanimously (all ayes, no opposed) to recommend that the City Council approve the proposed privacy policy, as presented, with the understanding that the policy will be adopted concurrently with the ATESD ordinance.
  • The motion was made by Chair Salvatore, seconded by Council member Wallace Smith, and passed without further amendment.
  • The ad hoc committee then adjourned to proceed to the next agenda item (the ordinance).

Meeting Transcript

Are you five? I'm gonna get this ad hoc started. Uh this ad hoc uh officially starting at 6.05 p.m. is the adoption of the privacy policy for the automated traffic enforcement safety devices. My name is Frank Salvatore. I'm the chair with me. I have Cheryl Wallace Smith and Candace Faye, the two uh city council persons who are on the ad hoc. We have uh Deputy Chief Sturdevant here. We have Tot O'Brien from the mayor's office. We have Robin Edwards and Caitlin Grace from the Corporation Council. In the room, we also have ex officio members, uh President Peter Bazade and Paul Rotello and uh members of the community. Did I miss anybody? See if I don't have my glasses on, I don't I don't see. So I don't miss anybody. Okay. So we're going to start off by asking corporation counsel to do a presentation because actually this uh ad hoc and the next ad hoc are kind of linked together. But we wanted to do the privacy policy first because that's uh probably the easiest one to go through before we get to the ordinance for the cameras. So ladies, you have the floor. Thank you. Thank you, Mr. Salvatore. Good evening, everyone. And I just have a few opening comments, and then we're going to we have a PowerPoint presentation for you this evening that actually covers the privacy policy as well as the ordinance, and we'll walk you through a few slides until we get to the privacy policy, and then we can stop and answer any questions that you have. But just by way of brief background information, this ad hoc is convened for the purposes of discussing the privacy policy. And the privacy policy, as Mr. Salvatore just pointed out, is to be adopted if an ordinance that provides for the use of automated traffic enforcement safety devices, ATE, SDs, as are known. Um also people call them red light or speed cameras, is adopted by the city. Um by way of very brief background information. In 2023, the state of Connecticut enacted a public act, which is now codified, and it's enabling legislation that provides for allowing towns and cities to employ these devices. Approximately 15 cities and towns throughout the state have adopted ordinances that provide for this at this time, and um which were actually approved by DOT. There are five currently under consideration. Adoption of such an ordinance represents a shift in traffic management. You don't need to rely solely on police patrols. Um the use of these devices provides for a more uniform oversight of high-risk areas. The goal is to reduce crashes, injuries, and fatalities by using these devices to monitor and enforce the running of red lights and speed in excess of 10 miles per hour over the posted speed limit. And you know, it's to improve traffic in school zones, pedestrian zones, and other high areas where there are safety concerns. So the process begins tonight with the adoption of an ordinance and the privacy policy, which is required to be adopted as part of that. And that's what we'll focus on tonight. So at this point, we can turn to our PowerPoint presentation, and Caitlin will run you through the first few slides. Um we hope it will be informative for you. Okay. Public Act 23116, which was codified as Connecticut General Statute sections 14307B through 1430H, allows municipalities to use ATSD, which is automatic traffic enforcement safety devices at locations within school zones, pedestrian safety zones, and other locations in such municipality. As long as they adopt four specific things. So first, it's the adoption of an ordinance in accordance with the statute's requirements. Second is the adoption of a model privacy policy in accordance with the statutes requirements. There also needs to be an adoption of a comprehensive safety action plan, which is currently being drafted by our planning and zoning department. And a plan drafted by the Danbury Police Department and the city traffic engineer, which has to be approved by the Connecticut Department of Transportation. An automatic uh automatic traffic and enforcement safety device. And if I will for the rest of the presentation be calling it an ATESD device. Um, those are two things.

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com