HF4205 (Legislative Session 94 (2025-2026))
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.
Related bill: SF4739
AI Generated Summary
Purpose
This bill tightens how automated license plate reader (ALPR) data is collected, stored, and used. It creates a central role for the Bureau of Criminal Apprehension (BCA) to manage ALPR data, limits what data can be collected, strengthens privacy protections, and regulates how private entities can use ALPR data. It also sets a clear timeline to move data into a state-controlled system and sets destruction and access rules to protect individuals’ privacy.
Main provisions
ALPR definitions and scope
- Defines what an automated license plate reader is and notes that traffic safety camera systems are not covered by these ALPR rules.
- Identifies law enforcement agencies as those using ALPRs.
Centralized data management
- The BCA becomes the central repository for all data created or received from ALPRs.
- All ALPR data must be stored on a state-based server.
- The bureau will allow law enforcement agencies to access this data as permitted.
Data collection limits and privacy
- Data collection is limited to: (1) license plate numbers, (2) date/time and location data about vehicles, and (3) pictures of plates, vehicles, and surrounding areas.
- Most ALPR data are private or nonpublic unless they are public by law or part of an active criminal investigative data set.
- Data matching is allowed only with Minnesota’s license plate data file, and only if related to an active criminal investigation. Data not tied to active investigations cannot be used for broad matching.
- A central state repository of ALPR data is prohibited unless explicitly authorized by law.
- ALPR data cannot track or monitor a person in an active criminal investigation without a warrant or, in some cases, exigent circumstances.
Data destruction and retention
- Data not related to an active investigation must be destroyed within 60 days (or per applicable rules).
- If a person is charged or has a pending case, data may be preserved if requested and tied to the case number.
- Data related to program participants (e.g., pilots or pilots’ data) must be destroyed on collection or upon request, unless the data are active investigative data.
- Inactive criminal investigative data must be destroyed according to the state retention schedule.
Access, audits, and cross-state sharing
- Law enforcement access must follow existing state rules and require written authorization from a chief or head of the agency, with a documented reason tied to an active investigation.
- Access is controlled by role-based permissions and must be recorded in an audit trail.
- All queries and actions involving ALPR data are public to the extent allowed by law.
- Data may not be accessed or shared outside Minnesota unless required by a court order or judicial warrant. The policy includes limits on sharing with federal agencies, other states, and private entities.
Private use and disclosures
- The bill regulates private use of ALPR systems, including posting signs to inform drivers that ALPR is in use.
- Private entities may not sell, transfer, share, or disseminate ALPR data about a person or their vehicle without the person’s consent, a court order, or a judicial warrant.
- Data from private ALPR use is treated as personal data under Minnesota law and subject to privacy protections.
ALPR data management by the BCA (section 299C.158)
- The BCA administers all ALPR data and must store it on a state-based server.
- Any contracts or agreements involving ALPR data must comply with the same privacy protections.
Private use governed by ALPR statute (section 325M.40)
- Defines ALPR systems and clarifies that the general private-use rules apply.
- Reiterates that ALPR data is personal data and subject to privacy protections.
Transfer timeline
- By December 1, 2026, all ALPR data used by law enforcement agencies must be transferred to the BCA, unless the data are active or inactive criminal investigative data.
Significant changes to current law
- Creates a single, state-wide central repository for ALPR data housed at the BCA.
- Significantly narrows what data may be collected and stored, emphasizing privacy (limited data categories; private vs. public data; mandatory destruction timelines).
- Tightens access controls and requires audit trails, with strict conditions for outside-the-state sharing.
- Introduces strict limits on private use of ALPR data, including mandatory signage, prohibitions on selling or disseminating data without consent or a court order, and classification of ALPR data as personal data.
- Establishes a firm deadline to transfer existing ALPR data to the centralized BCA system.
Potential impacts to consider
- Increased privacy protections for individuals, with tighter data retention and destruction rules.
- Greater oversight and traceability of ALPR data access and usage through audit trails.
- Reduced use of ALPR data for non-investigative purposes and stricter limits on private entities’ access.
- A potential shift in law enforcement workflows due to centralized data management and access controls.
Relevant Terms automated license plate reader, ALPR, Bureau of Criminal Apprehension, central repository, data privacy, private data, active criminal investigation, inactive criminal investigative data, data retention, destruction, data audit trail, role-based access, court order, judicial warrant, probable cause, exigent circumstances, data matching, Minnesota Statutes section 13.824, section 299C.158, section 325M.40, traffic safety camera, data sharing, signs for ALPR use, Minnesota license plate data file.
Bill text versions
- Introduction PDF PDF file
Past committee meetings
- Judiciary Finance and Civil Law on: March 17, 2026 10:15
Actions
| Date | Chamber | Where | Type | Name | Committee Name |
|---|---|---|---|---|---|
| March 12, 2026 | House | Action | Introduction and first reading, referred to | Judiciary Finance and Civil Law |
Citations
[
{
"analysis": {
"added": [
"Definitions for Automated license plate reader and Law enforcement agency."
],
"removed": [],
"summary": "Amendment to Minnesota Statutes 13.824 subd. 1 establishing definitions related to automated license plate readers (ALPR) and related terms.",
"modified": []
},
"citation": "13.824",
"subdivision": "1"
},
{
"analysis": {
"added": [
"New subdivision 1a: Bureau of Criminal Apprehension to act as central repository of ALPR data."
],
"removed": [],
"summary": "Adds a new subdivision (1a) designating the Bureau of Criminal Apprehension as central repository for ALPR data.",
"modified": []
},
"citation": "13.824",
"subdivision": "1a"
},
{
"analysis": {
"added": [
"Data collection limited to license plate numbers, date/time/location data, and photos of plates/areas."
],
"removed": [],
"summary": "Amendment to subd. 2 outlining data collection classifications and restrictions for ALPR data.",
"modified": [
"Establishes data classifications (private data on individuals or nonpublic data unless public or active criminal investigative data).",
"Prohibits collection of non-authorized data and restricts matching to specific conditions."
]
},
"citation": "13.824",
"subdivision": "2"
},
{
"analysis": {
"added": [
"Destruction of non-active data within defined timelines; preservation for exculpatory or program-participant data upon request."
],
"removed": [],
"summary": "Destruction and preservation provisions for ALPR data; retention and destruction requirements.",
"modified": [
"Destruction timelines (e.g., within 60 days) and special preservation provisions for exculpatory evidence and program participants."
]
},
"citation": "13.824",
"subdivision": "3"
},
{
"analysis": {
"added": [
"Written authorization requirements for access; creation of data audit trails; public availability of audit data where not legally restricted."
],
"removed": [],
"summary": "Access authorization and audit-trail requirements for ALPR data access.",
"modified": [
"Access limited to legitimate purposes; role-based access; documentation of basis for access and incident/case numbers."
]
},
"citation": "13.824",
"subdivision": "7"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Notwithstanding provision referencing 138.17 related to data destruction timelines.",
"modified": [
"Infers retention/destruction framework tied to 138.17 timelines when applicable."
]
},
"citation": "138.17",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Uses data classification rules from 13.82 subd. 2 in relation to ALPR data.",
"modified": [
"Specifies public data availability under 13.82 when data are public, otherwise private/nonpublic unless active investigative data per subd. 7."
]
},
"citation": "13.82",
"subdivision": "2"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Additional data classification reference within 13.82 for ALPR data.",
"modified": [
"Aligns ALPR data handling with 13.82 subsections addressing public/nonpublic data and investigative data status."
]
},
"citation": "13.82",
"subdivision": "3"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Further data classification reference within 13.82 for ALPR data.",
"modified": [
"Specifies when ALPR data may be public or private under 13.82."
]
},
"citation": "13.82",
"subdivision": "6"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Active criminal investigative data status under 13.82 for ALPR data.",
"modified": [
"Clarifies that ALPR data may be active criminal investigative data under 13.82 subd. 7."
]
},
"citation": "13.82",
"subdivision": "7"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Defines a traffic safety camera system as per 169.011 subd. 85a.",
"modified": [
"References to traffic safety camera system definition from 169.011(85a)."
]
},
"citation": "169.011",
"subdivision": "85a"
},
{
"analysis": {
"added": [
"BCA to administer and maintain ALPR data; data storage on an intra-state server."
],
"removed": [],
"summary": "ALPR data management framework under 299C.158; BCA duties and data hosting requirements.",
"modified": [
"Requires compliance with 13.824 and cross-references with 299C.158 for administration/management."
]
},
"citation": "299C.158",
"subdivision": ""
},
{
"analysis": {
"added": [
"Definition of ALPR system (automated license plate recognition system) as a searchable database combining cameras and algorithms."
],
"removed": [],
"summary": "Definition of ALPR system under 325M.40 subd. 1.",
"modified": []
},
"citation": "325M.40",
"subdivision": "1"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Data privacy provisions applying to ALPR data within the 325M framework.",
"modified": [
"Notes that data collected by ALPR is personal data as defined by 325M.11 and subject to 325M.10 through 325M.21."
]
},
"citation": "325M.10 to 325M.21",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Definition of ALPR data as personal data under 325M.11 with application of 325M.10-325M.21.",
"modified": []
},
"citation": "325M.11",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "References compliance with 13.05(5) in the ALPR data access framework.",
"modified": [
"Incorporates 13.05(5) access/compliance requirements for ALPR data handling."
]
},
"citation": "13.05",
"subdivision": "5"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "References to 13.055 in relation to ALPR data governance.",
"modified": [
"Incorporates cross-reference to 13.055 provisions impacting ALPR data."
]
},
"citation": "13.055",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Data collection classification and use restrictions (duplicate entry for clarity).",
"modified": []
},
"citation": "13.824",
"subdivision": "2"
}
]Progress through the legislative process
In Committee