Automated license plate reader data restrictions enhanced, data centralized in Bureau of Criminal Apprehension, and use of automated license plate readers by private entities regulated.
HF4205 revises Minnesota’s data practices law for automated license plate readers (ALPRs) and adds a new chapter governing private ALPR systems. For government use, the bill tightens what data may be collected, shortens the retention period for non-investigative data from 60 days to 48 hours, and limits access to data to documented law enforcement purposes tied to an active criminal investigation. It also adds stronger safeguards for tracking individuals, requiring a warrant or probable cause/exigent circumstances for monitoring a subject of an active investigation, and restricts sharing or access outside Minnesota unless a court order or judicial warrant requires it.
The bill centralizes government ALPR data management in the Bureau of Criminal Apprehension (BCA). All ALPR data collected, created, or received by state and local law enforcement must be maintained by the BCA, stored on a server located in Minnesota, and transferred to the BCA by law enforcement agencies by December 1, 2026, unless the data are active or inactive criminal investigative data. The bill also creates a new section regulating private ALPR systems, requiring notice signage, classifying collected data as personal data, and prohibiting sale, transfer, sharing, or dissemination of ALPR data without affirmative consent, a court order, or a judicial warrant.
The bill’s impact on state law is significant because it amends Minnesota Statutes section 13.824 and adds new statutory provisions in chapters 299C and 325M. It changes data classification, retention, access controls, and audit-trail requirements for law enforcement ALPR use, while also creating a separate privacy framework for private entities that operate ALPR systems. It would shift operational responsibility for government ALPR data to the BCA and impose new compliance obligations on agencies and private operators alike.
Because no committee transcript or vote record is provided, there is no recorded debate or roll-call history to gauge legislative sentiment. Based on the bill text and caption, the measure appears to be framed as a privacy and oversight bill, with a clear emphasis on limiting surveillance, improving accountability, and preventing broad dissemination of location-related vehicle data. The overall direction suggests support for stronger civil-liberties protections while preserving law enforcement access for active investigations.
The main points of contention likely involve the balance between privacy and policing. Law enforcement agencies may object to the shortened retention period, centralized storage requirements, warrant limits, and restrictions on out-of-state sharing, arguing they could hinder investigations or create administrative burdens. Privacy advocates, by contrast, would likely support the tighter controls, especially the limits on private-sector data sharing and the requirement that ALPR data be treated as personal data.
HF4205 would amend Minnesota’s government data practices law to impose stricter limits on automated license plate reader data, including narrower collection, faster destruction of non-investigative data, stronger access controls, and restrictions on sharing outside the state. It would also create a new BCA-managed central repository for law enforcement ALPR data and establish a separate regulatory scheme for private ALPR systems under chapter 325M. The bill affects law enforcement agencies, the Bureau of Criminal Apprehension, private ALPR operators, and individuals whose vehicle-location data is captured.
No committee discussion or vote history is included, so there is no direct record of legislative sentiment. The bill’s text indicates a generally privacy-protective and oversight-oriented approach, suggesting likely support from members concerned with surveillance limits and data privacy. At the same time, the bill’s law-enforcement exceptions show an effort to preserve investigative use, which may reflect an attempt to balance privacy interests with public safety needs.
The likely contention centers on whether the bill goes too far in restricting law enforcement access to ALPR data. Potential critics from law enforcement may argue that the 48-hour destruction rule, warrant requirements for monitoring, and prohibition on out-of-state sharing could impede investigations and interoperability with other agencies. Supporters, likely privacy and civil-liberties advocates, would favor the bill’s tighter retention limits, BCA centralization, audit-trail requirements, and restrictions on private-sector sale or dissemination of ALPR data without consent or judicial authorization.