SF4739 (Legislative Session 94 (2025-2026))
Automated license plate reader data regulations and provisions modifications
Related bill: HF4205
AI Generated Summary
Purpose
This bill tightens how automated license plate reader (ALPR) data is collected, stored, used, and shared in Minnesota. It creates a central management system under the Bureau of Criminal Apprehension (BCA), adds privacy protections for individuals, and regulates both government and private use of ALPR systems.
Key definitions (selected)
- Automated license plate reader (ALPR): a device (mounted on a patrol car or fixed) that records vehicle data and photos to compare with law enforcement databases. Includes devices operated by non-government entities if data are shared with law enforcement. Traffic safety cameras are not ALPRs.
- Bureau of Criminal Apprehension (BCA): now acts as the central repository for ALPR data.
- Data types: data must generally be limited to license plate numbers, date/time/location data, and pictures of plates/areas around vehicles.
- Active criminal investigative data: data relevant to ongoing investigations.
- Private data / public data / nonpublic data: how data are classified under Minnesota privacy laws.
Main provisions
- Central data management
- All ALPR data collected, created, or received must be stored and managed by the BCA, on a server located in Minnesota.
- The BCA may allow access to this data for law enforcement agencies, under the bill’s rules.
- Data collection limits
- Data collection is restricted to: (1) license plate numbers, (2) date/time/location data, and (3) pictures of license plates and surrounding areas.
- Other collected data are prohibited unless explicitly allowed.
- A central state repository of ALPR data is allowed only if explicitly authorized by law.
- Data matching and use
- Data may be matched with the Minnesota license plate data file, and additional data sources may be used only if they relate to an active criminal investigation.
- Data about individuals or their vehicles cannot be shared or sold without consent, a court order, or a judicial warrant.
- Privacy protections and access controls
- Data are private/nonpublic unless public or active investigative data.
- Access to ALPR data requires written authorization and a documented, legitimate law enforcement purpose.
- Access is limited by role-based permissions, with an audit trail recording all data queries and actions.
- Data cannot be accessed or shared outside Minnesota unless required by a court order or warrant.
- Private use of ALPRs
- Private ALPR users must post clear signs informing drivers that ALPRs are in use.
- Data from private ALPRs is personal data and cannot be sold or disseminated without consent, court order, or warrant.
- Retention and destruction
- Data not related to an active investigation must be destroyed within about 60 days (specific wording in the bill).
- If a person is the subject of a pending charge, data may be preserved until the case is resolved.
- Data linked to program participants (if applicable) must be destroyed at collection or upon request unless they are active investigative data.
- Inactive investigative data must be destroyed according to the state retention schedule.
- Data access outside the state
- ALPR data may not be accessed, disseminated, or shared outside Minnesota unless required by a court order or warrant.
- “Outside the state” includes federal agencies, other states, or private entities under cross-state agreements.
Data storage, transfer, and implementation
- Transfer deadline
- By December 1, 2026, agencies using ALPR must transfer all ALPR data to the BCA, unless the data are active or inactive criminal investigative data.
- Placement and contracts
- The BCA administers and stores all ALPR data; all related contracts must comply with this law and section 13.824.
Significant legal changes
- Establishes the BCA as the central repository for all ALPR data, shifting from dispersed storage to centralized management.
- Introduces strict data collection limits, enhanced privacy classifications, and mandatory access controls with audit trails.
- Requires signage and explicit consent procedures for private ALPR use.
- Sets a firm deadline to transfer existing ALPR data to the BCA.
- Tightens restrictions on sharing ALPR data outside the state and outside official warrants.
Implementation considerations
- Agencies will need to implement new data governance, storage, and access procedures.
- Private ALPR operators must comply with signage and data protection requirements.
- A formal process will be needed for warrants and exigent circumstances to access data in active investigations.
Relevant Terms - Automated license plate reader (ALPR) - Bureau of Criminal Apprehension (BCA) - Minnesota Statutes section 13.824 - Private data / public data / nonpublic data - Active criminal investigative data - Court order / judicial warrant - Exigent circumstances - Role-based access - Data audit trail - Minnesota license plate data file - Data retention and destruction - In-state data storage / server location within Minnesota - Central repository - Private ALPR use / signage requirements - Data sharing outside Minnesota - Public access to audit trails - Data matching and data sources for investigations - Consent requirements for data dissemination
Bill text versions
- Introduction PDF PDF file
Actions
| Date | Chamber | Where | Type | Name | Committee Name |
|---|---|---|---|---|---|
| March 23, 2026 | Senate | Action | Introduction and first reading | ||
| March 23, 2026 | Senate | Action | Referred to | Judiciary and Public Safety |
Citations
[
{
"analysis": {
"added": [
"Adds definitions for Automated license plate reader and related terms, including ownership/operation considerations and cross-references to other data categories."
],
"removed": [],
"summary": "Amends section 13.824 to define key terms related to automated license plate readers (ALPR) and related concepts.",
"modified": []
},
"citation": "13.824 Subd.1",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"Specifies data collection limits (license plate numbers, date/time/location, and pictures)."
],
"removed": [],
"summary": "Imposes data collection restrictions and data classification for ALPR data.",
"modified": [
"Defines how data are classified (private/nonpublic unless public or active criminal investigative data).",
"Allows matching only under certain conditions with additional data in active investigations."
]
},
"citation": "13.824 Subd.2",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"Sets destruction timelines for data not related to active investigations (e.g., within 60 days/48 hours).",
"Provides preservation requirements upon written requests in certain criminal proceedings."
],
"removed": [],
"summary": "Destruction and retention requirements for ALPR data.",
"modified": []
},
"citation": "13.824 Subd.3",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
"Requires compliance with specific data access controls and audit trail requirements.",
"Outlines role-based access and documentation for data access."
],
"removed": [],
"summary": "Access control provisions for ALPR data.",
"modified": [
"Tightly regulates who can access ALPR data and how access is recorded and audited."
]
},
"citation": "13.824 Subd.7",
"subdivision": "Subd.7"
},
{
"analysis": {
"added": [
"Designates BCA as central repository and requires data to be maintained by the BCA under section 299C.158."
],
"removed": [],
"summary": "Establishes the Bureau of Criminal Apprehension (BCA) as the central repository for ALPR data.",
"modified": [
"Shifts data storage/management responsibilities to the BCA, with access controls aligned to this role."
]
},
"citation": "13.824 Subd.1a",
"subdivision": "Subd.1a"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Defines traffic safety camera system in reference to ALPR-related provisions.",
"modified": [
"Uses the traffic safety camera system meaning from 169.011 Subd.85a to interpret ALPR data/system context."
]
},
"citation": "169.011 Subd.85a",
"subdivision": "Subd.85a"
},
{
"analysis": {
"added": [
"Clarifies that data are private/nonpublic unless conditions apply (public, active investigative data, or 13.82 Subd.2 or Subd.6)."
],
"removed": [],
"summary": "Reiterates data classification and permitted uses for ALPR data under the 13.82 framework.",
"modified": []
},
"citation": "13.82 Subd.2",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"States that a central state repository of ALPR data is prohibited unless explicitly authorized by law."
],
"removed": [],
"summary": "Clarifies policy on central data repositories for ALPR data.",
"modified": []
},
"citation": "13.82 Subd.3",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
"Allows matching with additional data sources if related to an active criminal investigation."
],
"removed": [],
"summary": "Addresses matching and data sources in active investigations.",
"modified": []
},
"citation": "13.82 Subd.6",
"subdivision": "Subd.6"
},
{
"analysis": {
"added": [
"Specifies access must be tracked (data audit trail) and that audit trail data are public to the extent not restricted by law."
],
"removed": [],
"summary": "Access controls and public auditability for ALPR data.",
"modified": []
},
"citation": "13.82 Subd.7",
"subdivision": "Subd.7"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "References destruction/retention under 138.17 retention planning.",
"modified": [
"Links destruction timelines to the retention schedule under 138.17."
]
},
"citation": "138.17",
"subdivision": ""
},
{
"analysis": {
"added": [
"Requires BCA to administer and maintain all ALPR data; mandates state-based storage."
],
"removed": [],
"summary": "ALPR data management entrusted to the Bureau of Criminal Apprehension.",
"modified": [
"Aligns data management with 13.824 and related sections."
]
},
"citation": "299C.158",
"subdivision": ""
},
{
"analysis": {
"added": [
"Provides a definition for automated license plate recognition (ALPR) system."
],
"removed": [],
"summary": "Defines ALPR system for purposes of this section.",
"modified": []
},
"citation": "325M.40 Subd.1",
"subdivision": "Subd.1"
},
{
"analysis": {
"added": [
"States government entities are excluded from certain ALPR uses; cross-references 13.824."
],
"removed": [],
"summary": "Excludes government entities from certain provisions and directs cross-reference to 13.824.",
"modified": []
},
"citation": "325M.40 Subd.2",
"subdivision": "Subd.2"
},
{
"analysis": {
"added": [
"Requires signs for ALPR usage; restricts sale/transfer of ALPR data without consent or court order; defines data as personal data under 325M."
],
"removed": [],
"summary": "Regulates private use of ALPR data.",
"modified": []
},
"citation": "325M.40 Subd.3",
"subdivision": "Subd.3"
},
{
"analysis": {
"added": [
"Specifies that ALPR data are personal data subject to 325M.10 through 325M.21."
],
"removed": [],
"summary": "Classifies ALPR data as personal data under chapter 325M.",
"modified": []
},
"citation": "325M.11",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Part of the 325M privacy data framework referenced for ALPR data.",
"modified": []
},
"citation": "325M.10",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Part of the 325M privacy data framework referenced for ALPR data.",
"modified": []
},
"citation": "325M.21",
"subdivision": ""
},
{
"analysis": {
"added": [
"References compliance with 13.05 Subd.5 for operation and maintenance of ALPR data."
],
"removed": [],
"summary": "Permits data access/operation constraints to apply to ALPR data management.",
"modified": []
},
"citation": "13.05 Subd.5",
"subdivision": "Subd.5"
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "Cross-reference for fundamental data handling related to ALPR data.",
"modified": [
"Discussion of data handling alignment with the ALPR provisions in this bill."
]
},
"citation": "13.055",
"subdivision": ""
},
{
"analysis": {
"added": [],
"removed": [],
"summary": "References to Minnesota Statutes Chapter 5B relating to restricted data environments.",
"modified": [
"Incorporates Chapter 5B provisions where applicable to program participants or related data practices."
]
},
"citation": "5B",
"subdivision": ""
}
]Progress through the legislative process
In Committee