HB 5449 — AN ACT CONCERNING AUTOMATED LICENSE PLATE READER SYSTEMS.
Last action — FILE NO. 536
-
✓Introduced
-
2In Committee
-
3Passed House
-
4Passed Senate
-
5To Executive
-
6Enacted
This bill is in committee in the House. Introduced March 04, 2026. It must pass committee before a floor vote.
Next likely step: a committee vote, then a floor vote in the House.
Odds of enactment
Low chanceBased on the sponsor, cosponsors, and committee posture, this bill has a low chance of becoming law.
Upgrade to see the exact probability and what's driving it.
A statistical estimate from our own model of past outcomes — an insight, not a guarantee. Policymaking is volatile.
Prognosis
-
In Committee
Current position in the legislative process.
-
10 sponsors
10 primary, 0 co-sponsors signed on.
-
Single-party support
Sponsorship is currently within one party (10 D).
Based on stage, sponsorship breadth, committee status, recorded votes, and cross-state momentum — a description of the observable signals, not a prediction.
Bill Text
What changed in the latest version
724 added · 291 removedPlain-language change summary
The amended bill HB 5449 now allows law enforcement agencies to use automated license plate readers for additional purposes, such as conducting traffic analytics and enforcing work zone speed limits. It also removes references to the Federal Terrorist Screening Database, narrowing the scope of permissible data comparison. These changes aim to clarify the intended use of the technology while ensuring focused application on local traffic management and public safety. This matters because it may enhance the effectiveness of law enforcement in managing road safety without expanding surveillance capabilities unnecessarily.
House of Representatives General Assembly RaisedFile Bill No.
5449536 February Session, 2026 LCOSubstitute House Bill No.
26745449 ReferredHouse toof Representatives, April 9, 2026 The Committee on JUDICIARYJudiciary Introducedreported by:through REP.
(JUD)STAFSTROM ANof ACTthe CONCERNING129th AUTOMATEDDist., LICENSEChairperson PLATEof READERthe SYSTEMS.Committee on the part of the House, that the substitute bill ought to pass.
AN ACT CONCERNING AUTOMATED LICENSE PLATE READER SYSTEMS.
(NEW)(Effective from passage)(a)As used inthissectioninthissectionand and sections 2 and 3 of this act:
(1) "Automated license plate reader system" means a mobile or fixed electronic image recording device that is capable, in combination with computer programs or algorithms, of converting images of license plates or vehicle descriptors into computer-readable data;
LCOsHB5449 / File No.
2674536 1 ofsHB5449 11File RaisedNo. Bill No.5449 (4) "Hotlist" means a list of registration numbers displayed on license plates maintained for comparison against a registration number obtained by an automated license plate reader system;
536 (4) "Hotlist" means a list of registration numbers displayed on license plates maintained for comparison against a registration number obtained by an automated license plate reader system;
or (iii) assisting in the control of access to a secured area;
(iv) conducting traffic analytics;
or (v) enforcing traffic violations and collecting associated fines through the use of work zone speed control systems, as defined in section 13a- 261 of the general statutes, and automated traffic enforcement safety devices, as defined in section 14-307b of the general statutes;
(i) Comparing such data with (I) data contained in a hotlist, (II) records of the Connecticut Online Law Enforcement Communications Teleprocessing System, (III) data contained in the Federal Bureau of Investigations Kidnapping and Missing Persons list, (IV) data contained in the Connecticut Criminal Justice Information System,sHB5449 or/ (V)File dataNo. contained in the Federal Terrorist Screening Database;
(ii)536 entering2 asHB5449 licenseFile plate number into an automated license plate reader system upon a law enforcement officer's determination that LCO No.
2674536 2System, of(V) 11data Raisedcontained Billin No.the Federal Terrorist Screening Database, (VI) data contained in the National Crime Information Center database, or (VII) data contained in the National Center for Missing and Exploited Children database;
5449or (ii) entering a license plate number into an automated license plate reader system upon a law enforcement officer's determination that data in the system may (I) be relevant and material to a specific active investigationofainvestigation criminaloffenseof inwhichtherea isreasonablesuspicioncriminal offense in which there is reasonable suspicion that the offense has been or is being committed, provided any access by an officer of automated license plate reader data for suchsuchpurpose purpose shall result ininarecordofthefactual abasisfor recordtheaccess of the factual basis for the access and any associated case number for the complaint or incident that is being investigated and is the basis for the access, (II) assist in the apprehension of an individual with an outstanding felony warrant, (III) assist in locating a missing or endangered individual, or (IV) assist in the recovery of a stolen motor vehicle.
(2) Any automated license plate reader data collected or held by a public agency or law enforcement agency shall not be retained for a period in excess of seventhirty days, or for a shorter period when required pursuant to the terms of a contract between a public agency or law enforcement agency with a private vendor that accesses an automated license plate reader system or stores such data, unless such data is being retained (A) pursuant to a warrant or court order issued by a judge or magistratemagistrateonbehalfofthestateorfederaljudicialbranches,or on behalf of the state or federal judicial branches or pursuant to court rules governing the preservation of evidence, or (B) for the purpose of collecting highway usage fees if such fees exist, provided such data is deleted not later than thirty days following the collection of such fees.fees, or (C) as evidence in an active criminal investigation or prosecution, provided (i) at the time such data is designated for retention, such retention is approved by a supervisory law enforcement officer and documented by the law enforcement agency in a record stating the factual basis for such retention and any associated case number for the investigation or prosecution to which the data relates, and (ii) such data is deleted upon the conclusion of the investigation if no criminal charges are filed, or upon the final disposition of the criminal case to which the data relates, including the exhaustion of all sHB5449 / File No.
536 3 sHB5449 File No.
536 direct appeals, whichever occurs first, unless otherwise required to be retained under subparagraph (A) of this subdivision.
Any other access to such data beyond an initial seven-day retention period, but prior to the end of such thirty-day retention period, shall be upon the issuance of a warrant by a judge or magistrate on behalf of the state or federal judicial branches.
LCO(3) No.Use or assist in the use of an automated license plate reader data system or automated license plate reader data for the purpose of investigating a suspected immigration violation or otherwise assisting in any civil or criminal immigration enforcement activity;
2674 3 of 11 Raised Bill No.5449 (3) Use or assist in the use of an automated license plate reader data system or automated license plate reader data for the purpose of investigating a suspected immigration violation or otherwise assisting in any civil or criminal immigration enforcement activity;
(5) CollectUnless authorized pursuant to section 29-6d of the general statutes, collect automated license plate reader data on the premises or within a distance established by the Police Officer Standards and TrainingsHB5449 Council/ pursuantFile toNo. section 2 of this act, of a reproductive or sexual health facility, as defined in section 42-515 of the general statutes, facility that primarily provides gender-affirming health care services or a nonprofit or community organization that primarily serves immigrant communities, excluding any property under federal jurisdiction;
(6)536 Share4 orsHB5449 provideFile accessNo. to automated license plate reader data, unless the individual or entity requesting such data or access is (A) a public agency or law enforcement agency of this state, (B) a law enforcement agency of the state of New York or Rhode Island or the Commonwealth of Massachusetts or a municipality of said states or commonwealth, provided such requesting law enforcement agency provides a written declaration affirming that any data received will be used in compliance with the prohibitions set forth in this section, and will not be used for an immigration investigation or enforcement action or to investigate or prosecute any individual who has sought, received or provided reproductive health care services or gender-affirming healthcareservicesandwillnotbefurtherdisclosedexceptaspermitted by law;
(C)536 anyTraining otherCouncil lawpursuant enforcementto agencysection other2 thanof thosethis act, of thisa statereproductive or describedsexual insubparagraph(B)ofthishealth subdivision,includingfacility, anyas federaldefined lawin enforcementsection agency,42-515 ifof suchthe requestinggeneral lawstatutes, enforcementthat agencyprimarily hasprovides gender-affirming health care services or a judiciallynonprofit issuedor probablecommunity causeorganization warrantthat forprimarily serves immigrant communities, excluding any property under federal jurisdiction, provided such facility or organization notified the specificPolice LCOOfficer No.Standards and Training Council of such facility's or organization's location;
2674(6) 4Share or provide access to automated license plate reader data, unless the individual or entity requesting such data or access is (A) a public agency or law enforcement agency of 11this Raisedstate, Bill(B) No.5449a law enforcement agency of the state of New York or Rhode Island or the Commonwealth of Massachusetts or a municipality of said states or commonwealth or a multijurisdictional task force of which a public agency or law enforcement agency of this state is a participating member, provided (i) such requesting law enforcement agency or task force provides a written declaration affirming that any data received will be used in compliance with the prohibitions set forth in this section, and will not be used for an immigration investigation or enforcement action or to investigate or prosecute any individual who has sought, received or provided reproductive health care services or gender- affirming health care services and will not be further disclosed except as permitted by law, and (ii) in the case of a multijurisdictional task force, such specific data requested is approved by the head of such task force or such head's designee and is directly and reasonably relevant to a specific investigation of such task force, (C) any other law enforcement agency other than those of this state or described in subparagraph (B) of this subdivision, including any federal law enforcement agency, if such requesting law enforcement agency has a judicially issued probable cause warrant for the specific data requested, or is requesting specific data on an individual identified as a possible match in the Federal Terrorist Screening Database;Database, or (D) is an individual requesting data regarding a motor vehicle registered in such individual's name, provided if a motor vehicle has more than one owner, lessor or regular user, all such owners, lessors and regular users join in the request and sHB5449 / File No.
or536 (D)5 issHB5449 anFile individualNo. requesting data regarding a motor vehicle registered in such individual's name, provided if a motor vehicle has more than one owner, lessor or regular user, all such owners, lessors and regular users join in the request and are natural persons;
536 are natural persons;
LCO(e) Not later than January 1, 2027, a public agency, other than a law enforcement agency, that operates an automated license plate reader system or uses automated license plate reader data shall adopt and publicize a written automated license plate reader system usage and privacy policy prior to using or acquiring an automated license plate sHB5449 / File No.
2674536 56 ofsHB5449 11File Raised Bill No.
5449536 (e) Not later than January 1, 2027, a public agency, other than a law enforcement agency, that operates an automated license plate reader system or uses automated license plate reader data shall adopt and publicize a written automated license plate reader system usage and privacy policy prior to using or acquiring an automated license plate reader system or automated license plate reader data.
(3) Any vendor that entered into a contract or an agreement pursuant to this subsection shall be considered an agent of the contracting public agency or law enforcement agency for purposes of services provided pursuant to the contract or agreement and shall be subject to the same LCOprovisions No.of this section as are applicable to such public agency or law enforcement agency.
2674(g) 6On ofand 11after RaisedOctober Bill1, No.54492026, provisionsa ofpublic thisagency sectionor aslaw areenforcement applicableagency may be subject to suchan publicaction agencyby any aggrieved individual for injunctive or lawdeclaratory enforcementrelief, agency.including a determination of past violations, if an officer, employee or other individual otherwise paid by sHB5449 / File No.
(g)536 On7 andsHB5449 afterFile OctoberNo. 1, 2026, a public agency or law enforcement agency may be subject to an action by any aggrieved individual for injunctive or declaratory relief, including a determination of past violations, if an officer, employee or other individual otherwise paid by or acting as an agent ofsuch agency violates any provision of subsection (b), (c) or (d) of this section.
536 or acting as an agent ofsuch agency violates any provision of subsection (b), (c) or (d) of this section.
If the alleged violation that forms the basis of an action under this subsection is committed by any vendor contracting with a public agency or law enforcement agency, as described in subdivision (3) of subsection (f) of this section, the vendor shall be liable for such violation, not the law enforcement agency or public agency.
(1) Develop standards for the use of a hotlist, including the sources from which a hotlist may be compiled, supervisory approval requirements for use and management of, access to and validation procedures for the data on any hotlist, including time limitationsfor theinclusionofsuchdataona hotlist, (2)providefor data retention limits in accordance with subdivision (2) of subsection (b) of section 1 of this act, (3) establish data access and sharing requirements in accordance with subsection (c) of section 1 of this act, including internal access controls and supervisory review and conditions under LCOwhich such data may be shared with other public agencies or law enforcement agencies, (4) provide for a supervisory responsibility and accountability structure, including designation of an officer or unit sHB5449 / File No.
2674536 78 ofsHB5449 11File RaisedNo. Bill No.5449 which such data may be shared with other public agencies or law enforcement agencies, (4) provide for a supervisory responsibility and accountability structure, including designation of an officer or unit responsible for oversight of automated license plate reader system use and compliance with any policy adopted in accordance with the provisions of this section, (5) establish training requirements, including initial and periodic training for any officer or employee authorized to access the system or data, (6) establish audit and logging requirements, including the creation and retention of access logs sufficient to ensure compliance and facilitate independent review, (7) establish public transparency standards and requirements, including publication of agency-specific usage policies for an automated license plate reader system and annual statistical reports detailing such usage, (8) establish the distance described in subdivision (5) of subsection (c) of section 1 of this act, and (9) contain provisions concerning compliance with subsection (f) of section 1 of this act concerning contracting with vendorsforservicesassociatedwithaccessto anautomatedlicenseplate reader system or storage of, processing of, transmission of, or access to automated license plate reader data.
536 responsible for oversight of automated license plate reader system use and compliance with any policy adopted in accordance with the provisions of this section, (5) establish training requirements, including initial and periodic training for any officer or employee authorized to access the system or data, (6) establish audit and logging requirements, including the creation and retention of access logs sufficient to ensure compliance and facilitate independent review, of which the logs shall include documentation of access to and retention of automated license plate reader data pursuant to subdivision (2) of subsection (b) of section 1 of this act, including, but not limited to, (A) the number of times such data is retained, and (B) the duration of such retention, and require that such audits be conducted not less than quarterly, (7) establish public transparency standards and requirements, including publication of agency-specific usage policies for an automated license plate reader system and annual statistical reports detailing such usage, (8) establish the distance described in subdivision (5) of subsection (c) of section 1 of this act, and (9) contain provisions concerning compliance with subsection (f) of section 1 of this act concerning contracting with vendorsforservicesassociatedwithaccessto anautomatedlicenseplate reader system or storage of, processing of, transmission of or access to automated license plate reader data.
Show all 285 changed lines (245 more)
(c)(1)Not later thanJanuary 1,2028,the Commissioner ofEmergency Services and Public Protection shall, in consultation with the Police Officer Standards and Training Council, adopt regulations, in accordance with the provisions of chapter 54 of the general statutes, to enact a policy that at aminimum,satisfiestheprovisionsofsubdivisions (1) to (9), inclusive, of subsection (a) of this section and section 1 of this act.sHB5449 / File No.
LCO536 9 sHB5449 File No.
2674536 8act. of 11 Raised Bill No.5449 (2) Not later than January 1, 2033, and at least once during each five- year period thereafter, the commissioner shall, in consultation with the Police Officer Standards and Training Council, adopt regulations in accordance with the provisions of chapter 54 of the general statutes.
Suchregulationsshall(2) (A)complywithNot theprovisionsofthissectionandlater sectionthan 1January of1, this2033, act and shallat notleast reduceonce orduring limiteach thefive- protectionsyear affordedperiod bythereafter, saidsectionsorthe anycommissioner minimumstandardsestablishedshall, byin saidsections,consultation andwith (B)the bePolice basedOfficer onStandards aand considerationTraining ofCouncil, anyadopt changesregulations in law,accordance technologywith and best practices since the previousprovisions adoption of regulationschapter pursuant54 toof thisthe section.general statutes.
Suchregulationsshall(A)complywiththeprovisionsofthissectionand section 1 of this act and shall not reduce or limit the protections afforded by saidsectionsor any minimumstandardsestablishedby saidsections, and (B) be based on a consideration of any changes in law, technology and best practices since the previous adoption of regulations pursuant to this section.
(NEW) (Effective from passage) (a) The Police Officer Standards and Training Council, in consultation with the Commissioner of Emergency Services and Public Protection and the Institute for Municipal and Regional Policy at The University of Connecticut, shall develop and promulgate a standardized form for reporting automated license plate reader system usage, including, but not limited to, (1) the number of (A) license plates scanned, (B) searches performed by the law enforcement agency andas thea reasonresult forof theautomated search, (C) matches that resulted inanarrest andconviction, (D)stolen motor vehiclesandstolen license platesplate recoveredreader duesystem to the use ofand anthe automatedreason licensefor plateany readersuch system,search, (E)(C) times automated license plate reader data was shared with or accessed by another entity, the identity of each of those entities and the reason for sharing the data, and(D) (F) times automated license plate reader data was shared or accessed pursuant to a judicial warrant, and (E) instances, if any, when data was retained longer than permissible pursuant to subdivision (2) of subsection (b) of section 1 of this act, and (2) any changes to the law enforcement agency's data collection, retention or sharing policies that affect privacy of automated license plate reader data.
(b) Each law enforcement agency shall, not later than January thirty- first following a calendar year during which the law enforcement agency used an automated license plate reader system pursuant to LCOsHB5449 / File No.
2674536 910 ofsHB5449 11File Raised Bill No.
5449536 subsection (b) of section 1 of this act, submit a report detailing such usage to the Institute for Municipal and Regional Policy at The University of Connecticut using the standardized form promulgated pursuant to subsection (a) of this section and publish such report on the law enforcement agency's Internet web site.
(c) Not later than January thirty-first of each year, any public agency, other than a law enforcement agency, that uses an automated license plate reader system or automated license plate reader system pursuant to subsection (b) of section 1 of this act, shall publish on the agency's Internet web site an annual report containing the information described in subsection (a) of this section as it pertains to such agency for the previous calendar year.
(d) Not later than July 30, 2027, and annually thereafter, the Institute for Municipal and Regional Policy at The University of Connecticut shall,shall within available resources, compile, analyze and summarize the reports submitted pursuant to subparagraph (a) of this subsection and shall submit, in accordance with section 11-4a of the general statutes, a consolidated report regarding automated license plate reader system usage and any recommendations for legislation to the Governor and the joint standing committees of the General Assembly having cognizance of matters relating to public safety and the judiciary.
3 from passage New section Statement of Purpose:Legislative Commissioners:
ToIn regulateSection 3(a)(1)(B), "searches performed by the uselaw enforcement agency" was changed to "searches performed by the law enforcement agency as a result of automated license plate reader systemssystem anduse" safeguardfor dataclarity. derived from such systems.
LCOJUD No.Joint Favorable Subst.
2674sHB5449 10/ ofFile 11 Raised Bill No.
5449536 [Proposed11 deletionssHB5449 areFile enclosedNo. in brackets.
Proposed536 additionsThe following Fiscal Impact Statement and Bill Analysis are indicatedprepared byfor underline,the exceptbenefit thatof whenthe members of the entireGeneral textAssembly, solely for purposes of ainformation, billsummarization orand resolutionexplanation orand ado sectionnot ofrepresent athe billintent orof resolutionthe isGeneral new,Assembly itor iseither notchamber underlined.]thereof LCOfor No.any purpose.
2674In 11general, fiscal impacts are based upon a variety of 11informational sources, including the analyst’s professional knowledge.
Whenever applicable, agency data is consulted as part of the analysis, however final products do not necessarily reflect an assessment from any specific department.
OFA Fiscal Note State Impact:
None Municipal Impact:
None Explanation The bill makes various changes related to the use of automated license plate reader (ALPR) systems by law enforcement and other public agencies and does not result in a fiscal impact, as described below.
Section 1 allows certain individuals to bring an action in Superior Court for alleged violations of the bill’s provisions, resulting in no fiscal impact to the state.
The court system disposes of over 250,000 cases annually and the number of cases is not anticipated to be great enough to need additional resources.
Section 2 requires the Police Officer Standards and Training Council (POSTC) to adopt a model policy governing law enforcement acquisition and use of ALPR data and does not result in a fiscal impact because POSTC has already adopted an ALPR model policy.
To the extent that revisions to the current policy are needed to meet the requirements of the bill, POSTC can accomplish this within existing resources.
Section 2 also requires the Department of Emergency Services and Public Protection (DESPP) to adopt related regulations, which the agency has existing expertise to do.
Section 3 sets various ALPR reporting requirements and does not sHB5449 / File No.
536 12 sHB5449 File No.
536 have a fiscal impact because it is expected that agencies can comply within existing resources.
The Out Years State Impact:
None Municipal Impact:
None sHB5449 / File No.
536 13 sHB5449 File No.
536 OLR Bill Analysis sHB 5449 AN ACT CONCERNING AUTOMATED LICENSE PLATE READER SYSTEMS.
SUMMARY Starting October 1, 2026, this bill restricts law enforcement agencies and other public agencies from using automated license plate reader (ALPR) systems or ALPR data, except for certain listed reasons.
Among other things, it:
1.
setsa 30-day limit onhowlong agenciescankeep thisdata unless certain conditions are met (such as its use in an active criminal investigation), and in some cases requires agencies to get a warrant if they seek to access the data more than seven days after they obtained it;
2.
specifically prohibits several uses of ALPR systems or data, such as for investigating suspected immigration violations;
3.
establishes requirements and restrictions for ALPR contracts between agencies and private vendors;
4.
allows individuals aggrieved by violations to seek injunctive or declaratory relief;
5.
requires the Police Officer Standards and Training Council (POST) to adopt a model ALPR usage policy and the Department of Emergency Services and Public Protection (DESPP) to adopt related regulations for implementation by law enforcement agencies;
6.
requires POST, in consultation with UConn’s Institute for Municipal and Regional Policy (IMRP), to develop a sHB5449 / File No.
536 14 sHB5449 File No.
536 standardized form for reporting ALPR system usage;
and 7.
sets related reporting requirements for law enforcement agencies, other public agencies, and UConn’s IMRP.
Under the bill, an “ALPR system” is a mobile or fixed electronic image recording device that, in combination with computer programs or algorithms, canconvert imagesoflicense platesor vehicledescriptors into computer-readable data.
“ALPR data” is any data that an ALPR system captures, records, stores, or processes, or that is derived from the system.
This includes licenseplatecharacters,vehicles’stillorvideoimages,vehicleattributes, location data, time stamps, and metadata.
EFFECTIVE DATE:
Upon passage § 1 — ALPR USAGE AND PROHIBITIONS Permissible Uses Starting on October 1, 2026, the bill prohibits law enforcement agencies (such as municipal police departments or the State Police) and public agencies (see BACKGROUND) from operating ALPR systems or using ALPR data, except under the following conditions.
Public Agency Uses.
Under the bill, public agencies may operate these systems or use this data to:
1.
perform weigh station duties;
2.
monitor or maintain their own vehicles or equipment;
3.
help in controlling access to secured areas;
4.
analyze traffic;
or 5.
enforce traffic violations and collect associated fines by using work zone speed camera systems and automated traffic enforcement safety devices (“red light cameras”).
sHB5449 / File No.
536 15 sHB5449 File No.
536 Law Enforcement Uses.
The bill allows law enforcement agencies to operate these systems or use this data to compare with data in:
1.
a hotlist (a list of registration numbers displayed on license plates, kept for purposes of this comparison);
2.
the Connecticut Online Law Enforcement Communications Teleprocessing (COLLECT) system;
3.
the FBI’s Kidnapping and Missing Persons list;
4.
the Connecticut Criminal Justice Information System;
5.
the federal Terrorist Screening Database;
6.
the National Crime Information Center (NCIC) database;
or 7.
the National Center for Missing and Exploited Children database.
The bill also allows law enforcement agencies to enter license plate numbers into an ALPR system if an officer determined that system data may:
1.
help to apprehend someone with an outstanding felony warrant, 2.
help to locate a missing or endangered person or to recover a stolen vehicle, or 3.
be relevant and material to a specific active criminal investigation.
For criminal investigations, this use is allowed only if there is a reasonable suspicion that the offense has been or is being committed.
The agency must keep a record of (1) the factual basis for accessing the data and (2) any associated case number for the complaint or incident.
Retention Limit.
The bill generally allows public agencies or law enforcementagenciestokeepALPRdataforonly30days.Buttheymust keep it for a shorter period if that is required by a contract between the sHB5449 / File No.
536 16 sHB5449 File No.
536 agency and a private vendor that accesses the system or stores the data.
These periods do not apply to data being kept:
1.
under a state or federal judicial warrant or court order;
2.
under court rules on preserving evidence;
3.
for collecting highway usage fees (ifthey exist),but thedata must be deleted within 30 days after the fee is collected;
or 4.
as evidence in an active criminal investigation or prosecution.
For this last reason, a supervisory law enforcement officer must approve the longer retention period, and the agency must keep a record of (1) the factual basis for keeping the data and (2) any associated case number.
Unless a warrant, court order, or rules of evidence require otherwise, the data must be deleted upon the earlier of the (1) investigation’s conclusion, if no charges are filed, or (2) case’s final disposition, including all direct appeals being exhausted.
Under the bill, any other access to the data after the first seven days, and before the end of the 30-day retention period, is allowed only upon a state or federal judicial warrant or court order.
Specifically Prohibited Uses The bill prohibits public agencies and law enforcement agencies from operating an ALPR system or using ALPR data for various purposes.
These prohibitions apply starting on October 1, 2026.
Various Prohibitions.
Specifically, it bars them from using or helping in the use of ALPR data to monitor or investigate someone based on their actual or perceived race, ethnicity, criminal history, sexual orientation, gender identity or expression, sex, pregnancy status, disability, citizenship, nationality, or income.
It also bars them from using or helping in the use of an ALPR system or ALPR data to:
sHB5449 / File No.
536 17 sHB5449 File No.
536 1.
identify someone engaged in an activity protected by the First Amendment;
2.
investigate a suspected immigration violation or otherwise help in civil or criminal immigration enforcement;
or 3.
investigate or prosecute someone who has sought, received, or provided reproductive or gender-affirming health care services.
Collection Near Gender-Affirming Care Facilities or Facilities Serving Immigrants.
The bill also generally bars public agencies and law enforcement agencies from collecting ALPR data at or near a (1) reproductive or sexual health facility that primarily provides gender- affirming health care services or (2) nonprofit or community organization that primarily serves immigrant communities.
It requires POST to establish a distance for this prohibition (see below).
For these prohibitions to apply, the facility or organization must notifyPOSTofitslocation.Theprohibitions donotapply(1)ifcollecting the data would be allowed under the law on police body and dashboard cameras or (2) at properties under federal jurisdiction.
Information Sharing.
The bill also restricts when these agencies can share or provide access to ALPR data.
It allows them to do so only if the requesting person or entity is:
1.
anindividual requesting datafor avehicleregistered inhisor her own name (if a vehicle has multiple owners, lessors, or regular users, they all must be individuals and must join in the request);
2.
another Connecticut public agency or law enforcement agency;
or 3.
under certainconditions,alawenforcement agency fromanother jurisdiction or multi-jurisdictional task force.
Under the bill, public agencies or law enforcement agencies can share ALPR data with a state or municipal law enforcement agency from sHB5449 / File No.
536 18 sHB5449 File No.
536 Massachusetts, New York, or Rhode Island, or a multi-jurisdictional task force of which the Connecticut agency is a member, but only if the requesting agency or task force affirms in writing that in using the data, it will comply with the bill’s prohibitions and will not:
1.
use it for immigration investigations or enforcement, 2.
use it for investigations or prosecutions relating to reproductive or gender-affirming health care services, or 3.
further disclose it except as allowed by law.
Additionally, for ataskforce, thegroup’sheador designeemust have approved the specific data request, and the data must be directly and reasonably relevant to a specific investigation.
The bill also allows Connecticut agencies or law enforcement agencies to share data with other law enforcement agencies (including federal ones), but only if the requesting agency has a judicially issued probable cause warrant for the specific data requested or is requesting specific data on a possible match in the federal Terrorist Screening Database.
Network Participation.
Unless certain conditions are met, the bill bars public agencies and law enforcement agencies from (1) participating in a system or network that shares ALPR data or (2) giving data to or accessing it through a multi-state, intrastate, or national data- sharingsystemornetwork.
Thisisallowedonlyifthesystemornetwork requires participants to execute a written declaration affirming that the data will be used solely in line with the bill and other Connecticut law and that they will not share or use the data except in line with the bill.
Bulk or Automatic Access.
The bill also bars these agencies from allowing a public agency to have real-time, bulk, or automatic access to ALPRdata,unless (1)inresponsetoadocumented,case-specificrequest and (2) the bill does not otherwise prohibit the data sharing.
sHB5449 / File No.
536 19 sHB5449 File No.
536 Limits on Data Disclosure Under FOIA The bill prohibits ALPR data from being disclosed under the Freedom of Information Act (FOIA).
But it makes the following disclosable under FOIA:
1.
the locations of ALPR recording devices (of video or still images) and 2.
data other than ALPR data derived from a system audit, system usage logs, and data access logs, as long as ALPR data is redacted.
Required Policies for Public Agencies The bill requires public agencies (other than law enforcement agencies) that operate ALPR systems or use ALPR data to adopt and make public a written usage and privacy policy.
They must do this by January 1, 2027, and before they use or acquire a system or data.
The policy must (1) comply with the bill’s applicable provisions and (2) include standards and safeguards substantially equivalent to those required under POST’s model policy (see below).
Contracts With Private Vendors The bill sets restrictions on public agency or law enforcement agency contractsor agreementswithprivate vendorsthat accessALPRsystems, or store, process, transmit, or access this data, on the agency’s behalf for various purposes (such as selling or sharing the data).
The contract must expressly require the vendor to comply with the bill’s provisions in the same way as the bill applies to the agency, as applicable.
It must expressly prohibit the vendor from keeping, using, or disclosing ALPR data for any purpose other than fulfilling its contractual obligations.
The vendor is considered to be the agency’s agent for the contractual services and is subject to the bill’s provisions that apply to the agency.
These provisions do not apply to contracts that pre-dated the bill’s passage.
sHB5449 / File No.
536 20 sHB5449 File No.
536 Private Enforcement Staring October 1, 2026, the bill allows an aggrieved individual to bring an action against a public agency or law enforcement agency for injunctive or declaratory relief, including a determination of past violations.
This applies if the agency’s officer, employee, or agent violates any of the bill’s provisions on permissible or prohibited uses or data sharing (including under FOIA).
If a vendor committed the violation, the vendor itself (and not the agency) is liable.
Under the bill, an aggrieved individual can bring the case in the judicial district where he or she lives.
If the individual prevails and is granted an order for injunctive relief, the individual may be entitled to recover court costs and reasonable attorney’s fees (but only with respect to the case, or part of it, related to seeking and getting the injunction).
These cases must be privileged (prioritized) with respect to trial assignment.
§ 2 — POST POLICY, LAW ENFORCEMENT ADOPTION, AND DESPP REGULATIONS By December 1, 2026, the bill requires POST to adopt a model policy on law enforcement agencies’ acquisition and use of ALPR systems and data.
The policy must direct these agencies to comply with the bill, including allowed and prohibited uses of ALPR systems and data (however they acquired the data).
The policy must also:
1.
set standards for using a hotlist (including permissible sources) and supervisory approval requirements for using, managing, accessing, and validating hotlist data (including time limits to include data on a hotlist);
2.
set data retention limits in line with the bill’s requirements (see above);
3.
set data access and sharing requirements in line with the bill, including internal access controls and supervisory review and conditions under which the data may be shared with other sHB5449 / File No.
536 21 sHB5449 File No.
536 agencies;
4.
provide for a supervisory responsibility and accountability structure, including designating an officer or unit responsible for overseeing ALPR system use and complying with the policy;
5.
set training requirements, including for officers and employees authorized to access the system or data;
6.
set audit and logging requirements, including for access logs (see below), with audits done at least quarterly;
7.
set public transparency standards and requirements, including for publication of agency-specific ALPR system usage policies and annual statistical reports on this usage;
8.
set the distance for the general prohibition on collecting ALPR data near (a) facilities that primarily provide gender-affirming health care or (b) nonprofits or organizationsthat primarily serve immigrant communities (see above);
and 9.
include provisions on compliance with the bill’s vendor-related provisions (see above).
The modelpolicy’sprovisionsonaccesslogsmust ensure compliance and facilitate independent review.
The logs must document the access and retention of ALPR data, including how often the data is kept and for how long.
Law Enforcement Agency Adoption or Alternate Policy The bill requires each law enforcement agency, by January 1, 2027, to adopt and implement either POST’s model policy or another policy that gives greater privacy protections than the model policy.
Law enforcement agency policies are in effect until DESPP’s regulations are adopted (see below).
Once adopted, the regulations supersede agency policies.
sHB5449 / File No.
536 22 sHB5449 File No.
536 DESPP Regulations By January 1, 2028, the bill requires the DESPP commissioner, in consultation with POST, to adopt regulations setting a policy in line with the requirements for POST’s model policy and the bill’s other provisions.
By January 1, 2033, and at least every five years after, the commissioner, in consultation with POST, must update the regulations based on any changes in law, technology, or best practices.
The updated regulations must not reduce or limit the bill’s protections or minimum standards.
These regulations are binding on all law enforcement agencies.
§ 3 — STANDARD FORM AND REPORTING Standardized Form The bill requires POST, in consultation with DESPP and UConn’s Institute for Municipal and Regional Policy (IMRP), to develop a standardized form for reporting ALPR system usage.
The form must include the number of:
1.
license plates scanned;
2.
searches done by the law enforcement agency due to ALPR system use and the reasons why;
3.
times ALPR data was shared with or accessed by other entities, their identities, and the reasons why;
4.
times ALPR data was shared or accessed under a judicial warrant;
and 5.
any instances when the data was kept longer than allowed under the bill.
The form also must include any changes to the law enforcement agency’s data collection, retention, or sharing policies that affect ALPR data privacy.
sHB5449 / File No.
536 23 sHB5449 File No.
536 ALPR Usage Reporting Under the bill, if a law enforcement agency uses an ALPR system, it must annually report to UConn’s IMRP, using the standard form, and publishthe reportontheagency’swebsite.
Ifanother publicagencyuses an ALPR system, it must post an annual report on its website about that usage, with the applicable information from the standard reporting form.
In either case, the reporting or posting is due by January 31 following any year when the agency uses an ALPR system.
IMRP Reporting The bill requires UConn’s IMRP to annually compile, analyze, and summarize the submitted reports and prepare a consolidated report on ALPR usage along with any legislative recommendations.
The report must be sent to the governor and the Judiciary and Public Safety and Security committees, with the first report due by July 30, 2027.
BACKGROUND Public Agencies Under FOIA and the bill, a public agency generally includes any:
1.
executive, administrative, or legislative office of the state or any political subdivision of the state and any state or town agency;
2.
department, board, commission, authority, or official of the state or of any municipality, school district, or other district or other political subdivision;
3.
committee of, or created by, any of these offices or officials;
4.
judicial office, official, or body or committee, but only for administrative functions;
and 5.
person to the extent they are the functional equivalent of a public agency (CGS § 1-200(1)).
sHB5449 / File No.
536 24 sHB5449 File No.
536 Related Bills sSB 4, § 18 (File 285), favorably reported by the General Law Committee, prohibits the departments of transportation and motor vehicles, or law enforcement agencies, from entering or renewing contracts with ALPR users unless the contract bars the user from taking various actions.
sHB 5552, favorably reported by the Government Administration and Elections Committee, prohibits public agencies from entering into or renewing contracts with ALPR vendors unless the contract bars the vendor from taking various actions.
COMMITTEE ACTION Judiciary Committee Joint Favorable Substitute Yea 32 Nay 9 (03/23/2026) sHB5449 / File No.
536 25
Show all 285 changed rows (245 more)
View plain text versions (3)
- File No. 536 View text pdf
- Raised Bill View text Current pdf
- Substitute JUD Joint Favorable Substitute pdf
Action History
-
FILE NO. 536
-
HOUSE CALENDAR NUMBER 355
-
FAV. RPT., TABLED FOR HOUSE CALENDAR
-
RPTD. OUT OF LCO
-
REFERRED TO Office of Legislative Research AND Office of Fiscal Analysis 04/08/26
-
FILED WITH LCO
-
Joint Favorable Substitute
-
PUBLIC HEARING 0309
-
REF. TO JOINT COMM. ON Judiciary
Sponsors
- Aundre Bumgardner · Primary
- Julie Kushner · Primary
- Matt Blumenthal · Primary
- Gary A. Winfield · Primary
- Maryam Khan · Primary
- Anthony L. Nolan · Primary
- Fred Gee · Primary
- Nick Gauthier · Primary
- Josh Elliott · Primary
- Saud Anwar · Primary
Sponsorship breakdown
Export CSV (upgrade) →10 sponsors · 0 co-sponsors · 177 not signed on
Sponsors (10)
- Aundre Bumgardner Democratic
- Julie Kushner Democratic
- Matt Blumenthal Democratic
- Gary A. Winfield Democratic
- Maryam Khan Democratic
- Anthony L. Nolan Democratic
- Fred Gee Democratic
- Nick Gauthier Democratic
- Josh Elliott Democratic
- Saud Anwar Democratic
Co-sponsors (0)
None.
Not signed on (177)
177 members have not signed on to this bill.
Show all 177 →"Not signed on" means a member has not sponsored or co-sponsored this bill — it does not imply opposition. Members flagged Voted No have a recorded No vote on this bill.
Subjects
Frequently asked questions
- Who sponsors HB 5449?
- HB 5449 is sponsored by Aundre Bumgardner (Democratic), Julie Kushner (Democratic), Matt Blumenthal (Democratic), Gary A. Winfield (Democratic), Maryam Khan (Democratic), Anthony L. Nolan (Democratic), Fred Gee (Democratic), Nick Gauthier (Democratic), Josh Elliott (Democratic), and Saud Anwar (Democratic).
- What is the current status of HB 5449?
- This bill is in committee in the House. Introduced March 04, 2026. It must pass committee before a floor vote.
- Where can I track HB 5449?
- Track HB 5449 free on One Click Politics — get push/email alerts when it moves.
Make your voice heard on HB 5449
Find the representatives who decide this bill and tell them where you stand — for yourself, or mobilize your whole list in one click with One Click Politics advocacy software.
Stay ahead of HB 5449
Last checked for changes 3 months ago · updated continuously
One Click Politics tracks every bill in Congress and all 50 states.
Track this bill →