Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Minnesota, USA Data Protection & Privacy Regulation

US-MN schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 91 claims · 38 sources in the cumulative register

Minnesota's data-protection enforcement posture shifted materially this cycle: the Minnesota Consumer Data Privacy Act's 30-day cure period, which had required the Attorney General to issue a warning letter before bringing an enforcement action, expired January 31, 2026.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Enforcement & Redress (1 open gap).

Framework & posture10 of 10 modules active
10 active · 9 binding instruments
Supervisory authorityMinnesota Attorney General
Next milestoneNo upcoming dated milestone on record
Record & confidence mix91 claims · 36 sources · machine-compiled
85 Probable6 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

United States federal law that applies in Minnesota, USA is covered once, on the United States page. This page covers Minnesota, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 8 November 2026

Lead Signal

Minnesota has joined a thirty-six-state coalition of attorneys general in a settlement with General Motors, announced October 29, 2026, resolving allegations that the automaker sold drivers' driving-behavior and location data to third parties, including data brokers who in turn resold that data to insurance companies without adequate consumer consent. Minnesota's share of the recovery is $7,095,664. The Attorney General's office frames the resolution as closing out conduct tied to driver-monitoring programs and data-broker resale, and states that General Motors remains subject to Minnesota's data-protection requirements going forward.

Key regulatory facts for Minnesota, USA
Key regulatory facts for Minnesota, USA
Regulatory DimensionMinnesota, USA Standing Position
JurisdictionMinnesota, USA (US-MN)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 91 sourced findings)
Regulator & FrameworkA comprehensive, currently in-force consumer privacy statute exists with a clearly identified enforcement authority and confirmed statutory citation (Minn.
Lawful Processing & Special DataStrong sensitive-data consent gate exists, but there is no GDPR Art.6-style enumerated lawful-basis framework, and pseudonymisation/anonymisation safe-harbour detail beyond the de-identified-data carve-out was not independently verified against statutory text.
Data Subject RightsRights are clearly enumerated by the regulator with a defined statutory response deadline (45 days) and complaint escalation path.
Controller/Processor DutiesCore accountability, assessment, processor-contract, and breach-notification duties are well evidenced from AGO guidance; DPO/ROPA specifics rely on pre-enactment secondary analysis and were not independently verified against final statute text.
Primary Instruments CitedNational Law Review, Madgett Law, Bloomberg Law, Madgett Law, Minnesota, USA Official Instrument (ag.state.mn.us 05_MCDPA-asp)
Last Confirmed / Updated (38 sources in cumulative register)

#

A comprehensive, currently in-force consumer privacy statute exists with a clearly identified enforcement authority and confirmed statutory citation (Minn. Stat. ch. 325M).

Primary frameworkMinnesota Consumer Data Privacy Act (MCDPA), Minn. Stat. ch. 325M (2024, effective July 31, 2025)
Traffic-light rationale — GreenA comprehensive, currently in-force consumer privacy statute exists with a clearly identified enforcement authority and confirmed statutory citation (Minn. Stat. ch. 325M).

Sub-modules (5)

Regulator and authorityGreen

The AGO is the sole enforcement authority for the MCDPA; the Act is not privately enforceable.

Claims (5):

  • The Minnesota Attorney General's Office is the exclusive enforcement authority for the MCDPA, and the Act is not privately enforceable.
  • Minnesota Attorney General — Minn. Stat. § 325M.20 vests exclusive MNCDPA enforcement authority in the AG; no private right of action.
  • Minnesota Attorney General's Office — The Minnesota Attorney General has exclusive enforcement authority over the MCDPA and there is no private right of action.
  • Minn. Stat. 325M.20 gives the Minnesota Attorney General exclusive enforcement authority over the MCDPA; the Act provides no private right of action.
  • Minnesota Attorney General — exclusive MCDPA enforcement authority; no private right of action for consumers

Act and instrumentsGreen

MCDPA signed May 19, 2024, codified at Minn. Stat. ch. 325M, effective July 31, 2025.

Claims (5):

  • The Minnesota Consumer Data Privacy Act was signed into law on May 19, 2024, codified at Minnesota Statutes chapter 325M, and took effect July 31, 2025.
  • Minnesota Consumer Data Privacy Act — The MCDPA is codified at Minn. Stat. Ch. 325M and took effect July 31, 2025.
  • The Minnesota Consumer Data Privacy Act took effect July 31, 2025 for most controllers.
  • Minnesota Consumer Data Privacy Act (MCDPA) — statutory 30-day cure period expired 31 January 2026; AG may now sue without prior notice
  • Sections 325M.10 to 325M.21 are cited as the Minnesota Consumer Data Privacy Act, effective July 31, 2025, except that postsecondary institutions regulated by the Office of Higher Education are not required to comply until July 31, 2029.

Material scopeGreen

Applicability thresholds are volume/revenue-based (100,000 MN residents, or 25%+ revenue from data sales plus 25,000 residents); small businesses per SBA definition are exempt.

Claims (3):

  • The MCDPA applies to entities that control or process the personal data of 100,000 or more Minnesota residents, or that derive over 25% of revenue from selling personal data and process or control personal data of 25,000 or more consumers.
  • Small businesses as defined by the U.S. Small Business Administration are exempt from the MCDPA, and there is no full exemption for HIPAA- or GLBA-covered entities, though targeted exemptions exist for health and financial data processing.
  • Minnesota Consumer Data Privacy Act — MCDPA applies to entities controlling/processing personal data of 100,000+ Minnesota consumers annually, or deriving over 25% of gross revenue from data sales while processing 25,000+ consumers' data.

Territorial scopeAmber

Coverage is triggered by processing volume tied to Minnesota residents rather than the controller's physical location, giving the statute extraterritorial reach over out-of-state online businesses.

Claims (1):

  • MCDPA applicability is triggered by the volume of Minnesota residents' personal data controlled or processed rather than the controller's physical presence in Minnesota, giving the statute extraterritorial reach.

Regulator registration and filingAmber

No controller/processor registration or pre-processing filing obligation with the AGO was identified in AGO guidance materials reviewed.

Claims (1):

  • No provision requiring controllers to register with or file notices to the Minnesota AGO prior to processing personal data was identified in reviewed AGO guidance.
Category narrative 83 words

Minnesota's data-protection landscape is anchored by the Minnesota Consumer Data Privacy Act (MCDPA), codified at Minnesota Statutes chapter 325M, which took effect July 31, 2025 and is enforced exclusively by the Minnesota Attorney General's Office (AGO). The statute applies to controllers/processors meeting Minnesota-resident-volume or data-sale-revenue thresholds, without a physical-presence nexus, and layers atop pre-existing sectoral and government-data statutes (e.g., the Minnesota Government Data Practices Act, Minn. Stat. ch. 13, which governs government-held data only and is out of scope for consumer-sector MCDPA obligations).

Sources and claims (15)
  1. Probable Minnesota Attorney General's Office — The Minnesota Attorney General's Office is the exclusive enforcement authority for the MCDPA, and the Act is not privately enforceable. observed
  2. Probable Minnesota Attorney General's Office — The Minnesota Consumer Data Privacy Act was signed into law on May 19, 2024, codified at Minnesota Statutes chapter 325M, and took effect July 31, 2025. observed
  3. Probable Minnesota Attorney General's Office — The MCDPA applies to entities that control or process the personal data of 100,000 or more Minnesota residents, or that derive over 25% of revenue from selling personal data and process or control personal data of 25,000 or more consumers. observed
  4. Probable International Association of Privacy Professionals — Small businesses as defined by the U.S. Small Business Administration are exempt from the MCDPA, and there is no full exemption for HIPAA- or GLBA-covered entities, though targeted exemptions exist for health and financial data processing. observed
  5. Probable Minnesota Attorney General's Office — MCDPA applicability is triggered by the volume of Minnesota residents' personal data controlled or processed rather than the controller's physical presence in Minnesota, giving the statute extraterritorial reach. observed
  6. Uncertain Minnesota Attorney General's Office — No provision requiring controllers to register with or file notices to the Minnesota AGO prior to processing personal data was identified in reviewed AGO guidance. observed
  7. Probable https://www.ag.state.mn.us/Office/Communications/2026/02/05_MCDPA.asp — Minnesota Attorney General — Minn. Stat. § 325M.20 vests exclusive MNCDPA enforcement authority in the AG; no private right of action.
  8. Probable National Law Review — Minnesota Consumer Data Privacy Act — The MCDPA is codified at Minn. Stat. Ch. 325M and took effect July 31, 2025. observed
  9. Probable Minnesota Attorney General — Minnesota Attorney General's Office — The Minnesota Attorney General has exclusive enforcement authority over the MCDPA and there is no private right of action. observed
  10. Probable National Law Review — The Minnesota Consumer Data Privacy Act took effect July 31, 2025 for most controllers. observed
  11. Probable Davis Wright Tremaine — Minnesota Consumer Data Privacy Act — MCDPA applies to entities controlling/processing personal data of 100,000+ Minnesota consumers annually, or deriving over 25% of gross revenue from data sales while processing 25,000+ consumers' data. observed
  12. Probable Koley Jessen — Minn. Stat. 325M.20 gives the Minnesota Attorney General exclusive enforcement authority over the MCDPA; the Act provides no private right of action. observed
  13. Probable White & Case — Minnesota Consumer Data Privacy Act (MCDPA) — statutory 30-day cure period expired 31 January 2026; AG may now sue without prior notice observed
  14. Probable White & Case — Minnesota Attorney General — exclusive MCDPA enforcement authority; no private right of action for consumers observed
  15. Probable Minnesota Office of the Revisor of Statutes — Sections 325M.10 to 325M.21 are cited as the Minnesota Consumer Data Privacy Act, effective July 31, 2025, except that postsecondary institutions regulated by the Office of Higher Education are not required to comply until July 31, 2029. observed

#

Strong sensitive-data consent gate exists, but there is no GDPR Art.6-style enumerated lawful-basis framework, and pseudonymisation/anonymisation safe-harbour detail beyond the de-identified-data carve-out was not independently verified against statutory text.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M
Traffic-light rationale — AmberStrong sensitive-data consent gate exists, but there is no GDPR Art.6-style enumerated lawful-basis framework, and pseudonymisation/anonymisation safe-harbour detail beyond the de-identified-data carve-out was not independently verified against statutory text.

Sub-modules (4)

Lawful basesAmber

Processing is governed by collection-limitation/purpose-limitation duties rather than an enumerated lawful-basis list.

Claims (1):

  • The MCDPA's operative model relies on consent plus collection/purpose-limitation duties (limiting collection to what is necessary and disclosed) rather than an enumerated multi-basis lawful-processing framework analogous to GDPR Article 6.

Special categoriesGreen

Sensitive data is defined broadly, including genetic and biometric data, health, and immigration status.

Claims (1):

  • MCDPA sensitive data includes race, ethnicity, religion, mental or physical health condition, sexual orientation, and precise geolocation, as well as genetic and biometric data, subject to enhanced consent requirements.

Pseudonymisation and anonymisationAmber

De-identified data that cannot be linked to individuals, and publicly available data, fall outside the Act's collection/consent restrictions.

Claims (1):

  • The MCDPA does not restrict processing of de-identified data, defined as data that cannot be linked to individual consumers, nor data that is publicly available.
Category narrative 60 words

The MCDPA does not adopt a GDPR-style enumerated multi-basis lawful-processing model; instead it relies on collection/purpose-limitation duties plus consent gates for sensitive data. Sensitive data is broadly defined (race, ethnicity, religion, health, sexuality, precise location, genetic and biometric data, citizenship/immigration status) and requires affirmative consumer consent before collection or sale. De-identified and publicly available data fall outside the Act's restrictions.

Sources and claims (5)
  1. Probable Minnesota Attorney General's Office — The MCDPA's operative model relies on consent plus collection/purpose-limitation duties (limiting collection to what is necessary and disclosed) rather than an enumerated multi-basis lawful-processing framework analogous to GDPR Article 6. observed
  2. Probable Minnesota Attorney General's Office — Controllers must obtain a consumer's affirmative consent before collecting or processing sensitive data, including specific location data or data revealing mental or physical health conditions or citizenship/immigration status. observed
  3. Probable Minnesota Attorney General's Office — MCDPA sensitive data includes race, ethnicity, religion, mental or physical health condition, sexual orientation, and precise geolocation, as well as genetic and biometric data, subject to enhanced consent requirements. observed
  4. Probable Minnesota Attorney General's Office — The MCDPA does not restrict processing of de-identified data, defined as data that cannot be linked to individual consumers, nor data that is publicly available. observed
  5. Probable Koley Jessen — Minnesota small businesses — A small business, as defined by the U.S. SBA, that conducts business in or targets Minnesota must not sell a consumer's sensitive data without the consumer's prior consent. observed

#

Rights are clearly enumerated by the regulator with a defined statutory response deadline (45 days) and complaint escalation path.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M, §325M.14
Traffic-light rationale — GreenRights are clearly enumerated by the regulator with a defined statutory response deadline (45 days) and complaint escalation path.

Sub-modules (5)

Access rightGreen

Consumers may access data held about them and obtain a list of specific third parties their data was sold to.

Claims (2):

  • Minnesota consumers have rights to know what data a company holds about them and to obtain a list of specific third parties to which their data has been sold.
  • Minnesota Consumer Data Privacy Act — MCDPA grants Minnesota consumers a right to confirm whether a controller is processing their personal data and to access it.

Rectification and erasureGreen

Consumers may correct inaccurate data and request deletion of personal/sensitive data.

Claims (1):

  • Consumers have the right to request correction of inaccurate data and deletion of their personal and sensitive data held by a business.

Restriction and objectionGreen

Consumers may opt out of sale, targeted advertising, and profiling, including profiling feeding automated decisions.

Claims (3):

  • Consumers may opt out of the sale of their personal data, use of their data for targeted advertising, and profiling, including profiling used in automated decision-making.
  • Minnesota Consumer Data Privacy Act — The Minnesota Act provides consumers with the right to question profiling decisions, a feature distinguishing it from some peer state laws.
  • Minnesota Consumer Data Privacy Act — MCDPA provides consumers a right to question profiling-based decisions producing legal or similarly significant effects and to seek correction of inaccurate data used in profiling.

Data portabilityGreen

The rights package includes a right to obtain a copy of one's data, per the AGO's own rights summary.

Claims (1):

  • The Act's consumer rights structure includes a right to obtain a copy of one's data in addition to rights to a third-party disclosure list, opt-out, access, correction, and deletion.

Deadlines and response windowsGreen

Businesses must respond to rights requests within 45 days; non-response triggers an AGO complaint pathway.

Claims (6):

  • Businesses must respond to consumer rights requests within 45 days, and consumers may file a complaint with the Attorney General's Office if a business fails to respond within that window.
  • Minnesota consumers — Consumers are advised to file a complaint with the AG if a business does not respond to a rights request within 45 days.
  • Minnesota Consumer Data Privacy Act — Minnesota consumers are entitled to a 45-day response window for data-privacy-related requests, with a right to appeal decisions.
  • Minnesota Consumer Data Privacy Act (MCDPA) — A controller must respond to a consumer's MCDPA rights request within 45 days; non-response entitles the consumer to file a complaint with the Attorney General's Office.
  • Minnesota Consumer Data Privacy Act (MCDPA) — A controller must respond to a consumer's MCDPA rights request within 45 days; if the controller does not respond within that period, the consumer may submit a complaint to the Minnesota Attorney General's Office, the exclusive enforcer of the Act.
  • Minnesota Consumer Data Privacy Act — If a controller does not take action on a consumer's rights request, it must inform the consumer without undue delay, and at the latest within 45 days of receipt of the request, of the reasons for not acting and how to appeal.
Category narrative 70 words

The MCDPA grants Minnesota consumers a materially complete rights package summarized by the AGO as 'LOCKED+': a list of third parties data was sold to, opt-out of sale/targeted-advertising/profiling, a copy of data held, knowledge of what is held, edit/correction rights, deletion rights, plus the right to question profiling and automated decisions. Businesses must respond to rights requests within 45 days, with a consumer complaint route to the AGO for non-response.

Sources and claims (13)
  1. Probable Minnesota Attorney General's Office — Minnesota consumers have rights to know what data a company holds about them and to obtain a list of specific third parties to which their data has been sold. observed
  2. Probable Minnesota Attorney General's Office — Consumers have the right to request correction of inaccurate data and deletion of their personal and sensitive data held by a business. observed
  3. Probable Minnesota Attorney General's Office — Consumers may opt out of the sale of their personal data, use of their data for targeted advertising, and profiling, including profiling used in automated decision-making. observed
  4. Probable International Association of Privacy Professionals — The Act's consumer rights structure includes a right to obtain a copy of one's data in addition to rights to a third-party disclosure list, opt-out, access, correction, and deletion. observed
  5. Probable Minnesota Attorney General's Office — Businesses must respond to consumer rights requests within 45 days, and consumers may file a complaint with the Attorney General's Office if a business fails to respond within that window. observed
  6. Probable Koley Jessen — Minnesota Consumer Data Privacy Act — The Minnesota Act provides consumers with the right to question profiling decisions, a feature distinguishing it from some peer state laws. observed
  7. Probable Davis Wright Tremaine — Minnesota consumers — Consumers are advised to file a complaint with the AG if a business does not respond to a rights request within 45 days. observed
  8. Probable Minnesota Attorney General — Minnesota Consumer Data Privacy Act — MCDPA grants Minnesota consumers a right to confirm whether a controller is processing their personal data and to access it. observed
  9. Probable Koley Jessen — Minnesota Consumer Data Privacy Act — MCDPA provides consumers a right to question profiling-based decisions producing legal or similarly significant effects and to seek correction of inaccurate data used in profiling. observed
  10. Probable Minnesota House Research Department — Minnesota Consumer Data Privacy Act — Minnesota consumers are entitled to a 45-day response window for data-privacy-related requests, with a right to appeal decisions. observed
  11. Probable Minnesota Attorney General's Office — Minnesota Consumer Data Privacy Act (MCDPA) — A controller must respond to a consumer's MCDPA rights request within 45 days; non-response entitles the consumer to file a complaint with the Attorney General's Office. observed
  12. Probable Minnesota Attorney General's Office — Minnesota Consumer Data Privacy Act (MCDPA) — A controller must respond to a consumer's MCDPA rights request within 45 days; if the controller does not respond within that period, the consumer may submit a complaint to the Minnesota Attorney General's Office, the exclusive enforcer of the Act. observed
  13. Probable Minnesota Office of the Revisor of Statutes — Minnesota Consumer Data Privacy Act — If a controller does not take action on a consumer's rights request, it must inform the consumer without undue delay, and at the latest within 45 days of receipt of the request, of the reasons for not acting and how to appeal. observed

#

Core accountability, assessment, processor-contract, and breach-notification duties are well evidenced from AGO guidance; DPO/ROPA specifics rely on pre-enactment secondary analysis and were not independently verified against final statute text.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M, §325M.13
Traffic-light rationale — AmberCore accountability, assessment, processor-contract, and breach-notification duties are well evidenced from AGO guidance; DPO/ROPA specifics rely on pre-enactment secondary analysis and were not independently verified against final statute text.

Sub-modules (7)

Accountability & DPIAGreen

Businesses must conduct data protection assessments and maintain data security practices.

Claims (1):

  • Businesses subject to the MCDPA must conduct data protection/privacy assessments and maintain data security practices to protect personal data.

DPO requirementsAmber

Pre-enactment IAPP analysis suggested an implied obligation to name a chief privacy officer or equivalent contact; not independently confirmed against final AGO guidance.

Claims (1):

  • Pre-enactment IAPP commentary on the MCDPA bill identified an implied obligation for covered entities to name a chief privacy officer or other individual with primary responsibility for privacy policies and procedures.

Ropa requirementsAmber

No standalone records-of-processing obligation distinct from the data protection assessment duty was identified.

Joint controller arrangementsGreen

Processor contracts must allocate responsibilities and support controller compliance and assessment obligations.

Claims (1):

  • Processor contracts under the MCDPA must require processors to assist controllers with security of processing, breach notifications, and data protection assessments, and must clearly allocate responsibilities between controller and processor.

Security measuresGreen

Processors must implement technical/organizational measures appropriate to processing risk.

Claims (1):

  • Processors must implement appropriate technical and organizational measures to ensure security appropriate to the risk of processing, and allow controller-directed assessments and inspections.

Breach notificationAmber

Processors must notify controllers of security breaches; Minnesota's general breach-notification statute (Minn. Stat. §325E.61) independently requires notice to affected residents, though full statutory text was not retrieved in this pass.

Claims (3):

  • Processors must provide notification to controllers upon a breach of the security of systems used to protect personal data, as part of MCDPA processor obligations.
  • Minnesota maintains a separate general data-breach-notification statute (Minn. Stat. §325E.61 et seq.) applicable to entities holding Minnesotans' personal information, distinct from MCDPA processor-to-controller notice duties.
  • Minnesota breach notification law — Minnesota's data breach notification law, Minn. Stat. §325E.61, requires businesses to notify consumers when their personal information has been compromised, operating alongside the MCDPA.

Retention and disposalGreen

Businesses may not retain data beyond what is relevant and reasonably necessary for the disclosed purpose.

Claims (1):

  • Businesses may not retain personal data longer than is relevant and reasonably necessary for the disclosed purpose.
Category narrative 64 words

Controllers must run data protection/privacy assessments, limit collection and retention to disclosed necessary purposes, and maintain risk-appropriate security. Processor contracts must impose breach-notification assistance, security cooperation, assessment-support, and audit/inspection rights, with a clear allocation of responsibilities. Evidence of a formal, freestanding ROPA obligation or an independent statutory DPO/chief-privacy-officer mandate (as opposed to a named privacy contact) was not conclusively confirmed against enacted statutory text.

Sources and claims (8)
  1. Probable Minnesota Attorney General's Office — Businesses subject to the MCDPA must conduct data protection/privacy assessments and maintain data security practices to protect personal data. observed
  2. Uncertain International Association of Privacy Professionals — Pre-enactment IAPP commentary on the MCDPA bill identified an implied obligation for covered entities to name a chief privacy officer or other individual with primary responsibility for privacy policies and procedures. observed
  3. Probable Minnesota Attorney General's Office — Processor contracts under the MCDPA must require processors to assist controllers with security of processing, breach notifications, and data protection assessments, and must clearly allocate responsibilities between controller and processor. observed
  4. Probable Minnesota Attorney General's Office — Processors must implement appropriate technical and organizational measures to ensure security appropriate to the risk of processing, and allow controller-directed assessments and inspections. observed
  5. Probable Minnesota Attorney General's Office — Processors must provide notification to controllers upon a breach of the security of systems used to protect personal data, as part of MCDPA processor obligations. observed
  6. Uncertain OneTrust DataGuidance — Minnesota maintains a separate general data-breach-notification statute (Minn. Stat. §325E.61 et seq.) applicable to entities holding Minnesotans' personal information, distinct from MCDPA processor-to-controller notice duties. observed
  7. Probable Minnesota Attorney General's Office — Businesses may not retain personal data longer than is relevant and reasonably necessary for the disclosed purpose. observed
  8. Probable Minnesota House Research Department — Minnesota breach notification law — Minnesota's data breach notification law, Minn. Stat. §325E.61, requires businesses to notify consumers when their personal information has been compromised, operating alongside the MCDPA. observed

#

This module is structurally inapplicable to a US state consumer-privacy statute; explicit absence confirmed via AGO guidance review rather than an unexamined gap.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M
Traffic-light rationale — RedThis module is structurally inapplicable to a US state consumer-privacy statute; explicit absence confirmed via AGO guidance review rather than an unexamined gap.

Sub-modules (6)

Transfer mechanismsRed

No transfer-mechanism regime beyond controller-processor contracts identified.

Claims (2):

  • The MCDPA does not establish an EU-style cross-border transfer regime; it imposes controller-processor contractual requirements and consumer rights but contains no identified adequacy determination, SCC/BCR mechanism, transfer impact assessment requirement, or data-localization mandate.
  • Minnesota Consumer Data Privacy Act — Minnesota's MCDPA contains no cross-border data-transfer mechanism analogous to GDPR adequacy/SCC frameworks.

Adequacy receivedRed

Not applicable; no adequacy concept in MCDPA.

Adequacy grantedRed

Not applicable; no adequacy concept in MCDPA.

SCCs and BCRsRed

No SCC/BCR uptake mechanism identified; not part of MCDPA structure.

Transfer impact assessmentRed

No TIA requirement identified.

Data localisationRed

No data-localisation mandate identified.

Category narrative 48 words

As a US state consumer-privacy statute, the MCDPA does not include an EU/GDPR-style cross-border transfer regime. No adequacy-determination mechanism (received or granted), standard contractual clauses/BCR framework, transfer impact assessment requirement, or data-localisation mandate was identified in AGO guidance; the statute's only cross-entity control is the controller-processor contract requirement.

Sources and claims (2)
  1. Probable Minnesota Attorney General's Office — The MCDPA does not establish an EU-style cross-border transfer regime; it imposes controller-processor contractual requirements and consumer rights but contains no identified adequacy determination, SCC/BCR mechanism, transfer impact assessment requirement, or data-localization mandate. observed
  2. Probable Minnesota Attorney General — Minnesota Consumer Data Privacy Act — Minnesota's MCDPA contains no cross-border data-transfer mechanism analogous to GDPR adequacy/SCC frameworks. observed

#

Financial, health, and education overlays are evidenced; several other sectors carry unresolved gaps requiring primary-source verification.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M (sectoral overlay with HIPAA, GLBA, COPPA)
Traffic-light rationale — AmberFinancial, health, and education overlays are evidenced; several other sectors carry unresolved gaps requiring primary-source verification.

Sub-modules (7)

Financial sector overlayAmber

Targeted exemption for GLBA-covered financial data processing; no full entity-level exemption.

Claims (1):

  • The MCDPA provides no full exemption for GLBA-covered financial institutions but includes targeted exemptions for financial data processing.

Health sector overlayAmber

Targeted exemption for HIPAA-covered health data processing; no full entity-level exemption; historical multistate health-breach enforcement precedent exists (Inmediata, 2023, pre-MCDPA).

Claims (2):

  • The MCDPA provides no full exemption for HIPAA-covered entities but includes targeted exemptions for health data processing.
  • In 2023, the Minnesota Attorney General joined a 32-state settlement with health-data clearinghouse Inmediata over a multi-year breach of protected health information affecting approximately 113,000 Minnesota residents, predating MCDPA but illustrating active health-data enforcement posture.

Telecoms and eprivacyRed

No MCDPA-specific ePrivacy/telecoms overlay identified.

Employment dataRed

Employment/B2B data exclusion status under MCDPA was not confirmed via retrieved sources.

Credit and scoringRed

FCRA-adjacent credit-scoring exemption status not confirmed.

educationAmber

Certain education technology providers are subject to MCDPA irrespective of general thresholds.

Claims (1):

  • Certain education technology providers are subject to the MCDPA regardless of the general consumer-volume thresholds applicable to other controllers.

insuranceRed

No insurance-sector-specific overlay identified.

Category narrative 56 words

The MCDPA does not fully exempt GLBA-covered financial institutions or HIPAA-covered health entities, instead layering targeted (data-level) exemptions on top of those federal regimes. Certain education-technology providers are subject to the MCDPA regardless of the general volume thresholds. Telecoms/ePrivacy, employment-data, credit/scoring, and insurance-specific overlays were not confirmed via retrievable AGO or T1/T2 sources in this pass.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (4)
  1. Probable International Association of Privacy Professionals — The MCDPA provides no full exemption for GLBA-covered financial institutions but includes targeted exemptions for financial data processing. observed
  2. Probable International Association of Privacy Professionals — The MCDPA provides no full exemption for HIPAA-covered entities but includes targeted exemptions for health data processing. observed
  3. Probable Minnesota Attorney General's Office — In 2023, the Minnesota Attorney General joined a 32-state settlement with health-data clearinghouse Inmediata over a multi-year breach of protected health information affecting approximately 113,000 Minnesota residents, predating MCDPA but illustrating active health-data enforcement posture. observed
  4. Probable Minnesota Attorney General's Office — Certain education technology providers are subject to the MCDPA regardless of the general consumer-volume thresholds applicable to other controllers. observed

#

Universal opt-out and targeted-advertising opt-out are strongly evidenced; dark patterns and clean-room provisions remain unconfirmed gaps.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M
Traffic-light rationale — AmberUniversal opt-out and targeted-advertising opt-out are strongly evidenced; dark patterns and clean-room provisions remain unconfirmed gaps.

Sub-modules (6)

Cookies and trackersGreen

Universal opt-out mechanisms operate via browser-level signals affecting tracking/targeted-ad collection.

Claims (1):

  • The MCDPA requires businesses to honor universal opt-out mechanisms (browser-based signals) that communicate a consumer's opt-out of targeted advertising and data collection/sale across websites.

Dark patternsRed

No MCDPA-specific dark-pattern prohibition confirmed via retrieved sources.

Opt out signalsGreen

Businesses must honor universal opt-out preference signals.

Claims (3):

  • The MCDPA requires businesses to honor universal opt-out mechanisms (browser-based signals) that communicate a consumer's opt-out of targeted advertising and data collection/sale across websites.
  • Minnesota Consumer Data Privacy Act — Minnesota requires controllers to allow consumers to communicate their privacy preferences through universal opt-out mechanisms (UOOMs).
  • Minnesota Consumer Data Privacy Act — Minnesota controllers must allow consumers to communicate opt-out preferences through a universal opt-out mechanism (UOOM).

Clean rooms and dcrRed

No clean-room/data-collaboration-room rule identified.

Cross context advertisingGreen

Consumers may opt out of sale and targeted advertising use of their personal data.

Claims (1):

  • Consumers have the right to opt out of the sale of personal data and its use for targeted advertising.

Direct marketingAmber

Direct-marketing-specific suppression rules beyond the general targeted-advertising opt-out were not separately confirmed.

Claims (1):

  • Consumers have the right to opt out of the sale of personal data and its use for targeted advertising.
Category narrative 39 words

The MCDPA mandates honoring browser-based universal opt-out mechanisms (GPC-style signals) for targeted advertising and data-sale opt-out, and grants a direct consumer opt-out right for sale/targeted-advertising/profiling. Dark-pattern-specific prohibitions and clean-room/data-collaboration-room rules were not confirmed via retrieved AGO or T1/T2 sources.

Sources and claims (4)
  1. Probable Minnesota Attorney General's Office — The MCDPA requires businesses to honor universal opt-out mechanisms (browser-based signals) that communicate a consumer's opt-out of targeted advertising and data collection/sale across websites. observed
  2. Probable Minnesota Attorney General's Office — Consumers have the right to opt out of the sale of personal data and its use for targeted advertising. observed
  3. Probable Koley Jessen — Minnesota Consumer Data Privacy Act — Minnesota requires controllers to allow consumers to communicate their privacy preferences through universal opt-out mechanisms (UOOMs). observed
  4. Probable Privacy World (Squire Patton Boggs) — Minnesota Consumer Data Privacy Act — Minnesota controllers must allow consumers to communicate opt-out preferences through a universal opt-out mechanism (UOOM). observed

#

Profiling/ADM rights are strongly evidenced and materially significant; biometric/genetic standalone-regime status and state-surveillance carve-outs remain unresolved gaps.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M, §325M.14
Traffic-light rationale — AmberProfiling/ADM rights are strongly evidenced and materially significant; biometric/genetic standalone-regime status and state-surveillance carve-outs remain unresolved gaps.

Sub-modules (6)

Profiling restrictionsGreen

Consumers may opt out of profiling in furtherance of decisions with legal or similarly significant effects.

Claims (2):

  • Minnesota's Attorney General has characterized the MCDPA as providing some of the nation's strongest protections against harmful data profiling and automated decision-making, including a consumer right to opt out of profiling used in furtherance of significant decisions.
  • Minn. Stat. §325M.40 — A $10,000 statutory-damages claim for a child or parent over addictive/algorithmic social-media design features, added by Laws 2026 ch. 111 (signed 2026-05-26), effective 2027-07-01.

Automated decision making transparencyGreen

Consumers may request the reasoning and underlying data behind a profiling/automated decision, including AI-facilitated decisions.

Claims (1):

  • Consumers may request information regarding a profiling or automated decision made about them, including the reasoning behind the decision and the data used to reach it, and may question automated decisions facilitated by artificial intelligence.

AI risk assessmentsAmber

The Act creates rights intended to prevent AI/automated systems from depriving residents of critical goods and services.

Claims (1):

  • The MCDPA creates rights intended to ensure that AI and automated systems cannot deprive Minnesota residents of critical goods and services.

Biometric regimeAmber

Biometric data is a sensitive-data category requiring consent; a standalone biometric-specific statute status is unconfirmed.

Claims (2):

  • Biometric data is classified as sensitive data under the MCDPA and subject to consent requirements before collection; no standalone biometric-specific statute comparable to Illinois' BIPA has been confirmed as currently enacted in Minnesota.
  • SF 4351 — New Minn. Stat. ch. 325M coding requiring consent before collecting biometric data, prohibiting sale, and requiring deletion, with civil penalties.

Genetic dataAmber

Genetic data is a sensitive-data category requiring consent; separate government-data-practices genetic provisions (Minn. Stat. §13.386) exist but full text was not retrieved.

Claims (1):

  • Genetic data is classified as sensitive data under the MCDPA requiring consumer consent before collection; Minnesota separately maintains government-data-practices provisions addressing genetic information (Minn. Stat. §13.386), though current text of that provision was not independently retrieved.

State surveillance carveoutsRed

No MCDPA government/law-enforcement exemption language was confirmed via retrieved sources.

Claims (1):

  • xAI, LLC v. Ellison (8th Cir. No. 26-2806) — Eighth Circuit granted xAI an injunction pending appeal on 2 October 2026, blocking enforcement of Minnesota's AI-nudification statute (HF1606) against xAI; opening appellate brief due 29 October 2026
Category narrative 86 words

The AGO has characterized the MCDPA as one of the nation's strongest statutes against harmful profiling and automated decision-making, granting consumers a right to question and obtain the reasoning/data behind profiling decisions and to opt out of profiling in furtherance of legally or similarly significant decisions, including AI-facilitated decisions. Genetic and biometric data are classified as sensitive data requiring consent, but standalone biometric- or genetic-specific statutes (comparable to Illinois' BIPA) and government/law-enforcement surveillance carve-outs were not independently confirmed as currently enacted MCDPA provisions in this pass.

Periodic update · new data 2026-10-26

The most significant development touching this module is litigation rather than legislation. On 2 October 2026 the Eighth Circuit Court of Appeals granted xAI, LLC an injunction pending appeal in its challenge to Minnesota's AI-nudification statute, identified in the underlying case record as HF1606. The injunction blocks enforcement of the statute against xAI while its appeal, docketed before the Eighth Circuit, proceeds. xAI's opening appellate brief is due 29 October 2026, which sets the next concrete marker in a case that will determine, at least as to this defendant, whether the statute can be enforced at all during the pendency of the litigation.

The statute at issue restricts the creation or distribution of AI-generated sexually explicit depictions of identifiable individuals without consent, a category sometimes referred to in commentary as nudification technology. Framed this way, the law sits at the intersection of content-safety regulation and governance of algorithmic systems that process biometric or identity-linked inputs to generate synthetic outputs. It is understood to touch this module because an AI system generating a depiction of a real, identifiable person necessarily processes some representation of that person, even where the statute itself is drafted primarily in content-restriction rather than data protection terms. That said, the classification is not settled: the statute's core concern, restricting a category of harmful synthetic content, looks in important respects more like a content-safety or criminal law than a rule governing the lawful basis for processing personal data, the rights of data subjects, or the duties of controllers and processors in the conventional data protection sense. Readers should treat its placement here as provisional pending further clarification of how the statute's mechanics map onto data protection concepts proper.

What the injunction establishes, provisionally, is that a federal appellate court found xAI's challenge sufficiently likely to succeed, or the balance of harms sufficiently in xAI's favor, to warrant blocking enforcement during the appeal. That is a meaningful signal about the statute's litigation exposure, but it is not a ruling on the merits, and the statute remains on the books and presumably enforceable against other parties who are not subject to the injunction. The scope of the injunction, whether it runs only to xAI or has broader practical effect on the state's ability to enforce the statute pending resolution, is not resolved by the material available.

For institutions and developers operating AI systems that generate synthetic depictions of individuals, the Minnesota case is one data point in a wider pattern of state-level attempts to regulate AI-generated content involving real people, and of the inevitable constitutional and statutory challenges such attempts invite from affected companies. The specific legal theory underlying xAI's challenge, and the specific basis on which the Eighth Circuit found an injunction warranted, are not detailed in the material reviewed, and so cannot be stated here. What can be stated is that the law's enforceability against at least one major AI developer is currently suspended, and that the appellate briefing process now underway, beginning with the brief due 29 October 2026, is the mechanism through which that suspension will either be lifted, extended or made permanent.

Outlook

The appellate schedule is the governing timeline here: xAI's opening brief is due 29 October 2026, and the state's response and any reply will follow on whatever schedule the Eighth Circuit sets, with oral argument and a ruling to come at some later point not yet fixed. Whether the Eighth Circuit's eventual ruling will be confined to the facts of xAI's challenge or will speak more broadly to the constitutionality or scope of AI-nudification statutes of this kind cannot be determined from the material reviewed. Separately, the question of whether this statute is properly understood as falling within algorithmic and surveillance governance as a data protection matter, or is better understood as sitting outside that frame entirely, remains open and is flagged for further clarification as the litigation develops.

Sources and claims (8)
  1. Probable Minnesota Attorney General's Office — Minnesota's Attorney General has characterized the MCDPA as providing some of the nation's strongest protections against harmful data profiling and automated decision-making, including a consumer right to opt out of profiling used in furtherance of significant decisions. observed
  2. Probable Minnesota Attorney General's Office — Consumers may request information regarding a profiling or automated decision made about them, including the reasoning behind the decision and the data used to reach it, and may question automated decisions facilitated by artificial intelligence. observed
  3. Probable Minnesota Attorney General's Office — The MCDPA creates rights intended to ensure that AI and automated systems cannot deprive Minnesota residents of critical goods and services. observed
  4. Uncertain Minnesota Attorney General's Office — Biometric data is classified as sensitive data under the MCDPA and subject to consent requirements before collection; no standalone biometric-specific statute comparable to Illinois' BIPA has been confirmed as currently enacted in Minnesota. observed
  5. Uncertain Minnesota Attorney General's Office — Genetic data is classified as sensitive data under the MCDPA requiring consumer consent before collection; Minnesota separately maintains government-data-practices provisions addressing genetic information (Minn. Stat. §13.386), though current text of that provision was not independently retrieved. observed
  6. Probable Madgett Law — Minn. Stat. §325M.40 — A $10,000 statutory-damages claim for a child or parent over addictive/algorithmic social-media design features, added by Laws 2026 ch. 111 (signed 2026-05-26), effective 2027-07-01. observed
  7. Probable Reclaim The Net — SF 4351 — New Minn. Stat. ch. 325M coding requiring consent before collecting biometric data, prohibiting sale, and requiring deletion, with civil penalties. observed
  8. Probable Bloomberg Law — xAI, LLC v. Ellison (8th Cir. No. 26-2806) — Eighth Circuit granted xAI an injunction pending appeal on 2 October 2026, blocking enforcement of Minnesota's AI-nudification statute (HF1606) against xAI; opening appellate brief due 29 October 2026 observed

#

Children's-data provisions are clearly documented by the regulator with specific age thresholds and guardianship extension.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M (with COPPA, 15 U.S.C. §§6501-6506, cross-reference)
Traffic-light rationale — GreenChildren's-data provisions are clearly documented by the regulator with specific age thresholds and guardianship extension.

Sub-modules (5)

Age verificationAmber

No standalone age-verification mandate identified beyond 'known child'/'known consumer age 13-16' actual-knowledge standards.

Claims (2):

  • Controllers may not process a consumer's personal data for targeted advertising or sell that consumer's personal data without the consumer's consent where the controller knows the consumer is between 13 and 16 years of age.
  • Minn. Stat. §325M.33 — Laws 2026, ch. 111, §1 adds an age-estimation disclosure clause to the list of required social-media platform disclosures, effective 2027-07-01.

Minor profiling bansAmber

Consent (rather than an outright ban) is required for targeted advertising/sale involving consumers known to be 13-16.

Claims (1):

  • Controllers may not process a consumer's personal data for targeted advertising or sell that consumer's personal data without the consumer's consent where the controller knows the consumer is between 13 and 16 years of age.

Education settingsAmber

Certain education technology providers are covered by the MCDPA regardless of general applicability thresholds.

Claims (1):

  • Certain education technology providers are subject to the MCDPA regardless of the general applicability thresholds, extending coverage into student-data contexts.

Dependent adultsGreen

Consumers may exercise MCDPA rights on behalf of persons under their guardianship or conservatorship.

Claims (1):

  • The MCDPA allows consumers to exercise their statutory rights on behalf of their children or any person over whom the consumer has guardianship or conservatorship.
Category narrative 65 words

The MCDPA requires parental/guardian consent before processing a 'known child's' personal data (with limited exceptions) and COPPA compliance, plus an opt-in consent requirement for targeted advertising or sale of data for consumers known to be 13-16 years old. Certain education technology providers are covered regardless of general thresholds, and the Act permits consumers to exercise rights on behalf of children or persons under their guardianship/conservatorship.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Probable Minnesota Attorney General's Office — Controllers may not process a consumer's personal data for targeted advertising or sell that consumer's personal data without the consumer's consent where the controller knows the consumer is between 13 and 16 years of age. observed
  2. Probable Minnesota Attorney General's Office — Controllers may not process the personal data concerning a known child without obtaining consent from the child's parent or lawful guardian (with limited exceptions), and must comply with COPPA. observed
  3. Probable Minnesota Attorney General's Office — Certain education technology providers are subject to the MCDPA regardless of the general applicability thresholds, extending coverage into student-data contexts. observed
  4. Probable Minnesota Attorney General's Office — The MCDPA allows consumers to exercise their statutory rights on behalf of their children or any person over whom the consumer has guardianship or conservatorship. observed
  5. Probable Madgett Law — Minn. Stat. §325M.33 — Laws 2026, ch. 111, §1 adds an age-estimation disclosure clause to the list of required social-media platform disclosures, effective 2027-07-01. observed
  6. Probable Minnesota House of Representatives — HF4138 — Verifiable parental consent required to create or maintain a social-media account for a user under age 16, commencing 2027-07-01. observed

#

Enforcement powers, penalties, and activity are well documented and robust, but the absence of a private right of action and expiration of the cure period both materially shift risk allocation, and no collective-redress mechanism exists.

Primary frameworkMinnesota Consumer Data Privacy Act, Minn. Stat. ch. 325M
Traffic-light rationale — AmberEnforcement powers, penalties, and activity are well documented and robust, but the absence of a private right of action and expiration of the cure period both materially shift risk allocation, and no collective-redress mechanism exists.

Sub-modules (6)

Regulator powers and penaltiesGreen

AGO may seek injunctive relief, litigation costs, and civil penalties up to $7,500/violation.

Claims (7):

  • The Minnesota Attorney General may seek injunctive relief, litigation expenses, and civil penalties of up to $7,500 per violation against MCDPA violators.
  • After January 31, 2026, the Minnesota Attorney General is under no obligation to provide any warning letter to a potential violator before initiating an enforcement action.
  • Minnesota Consumer Data Privacy Act — MCDPA violations are subject to civil penalties of up to $7,500 per violation, recoverable by the Attorney General along with injunctive relief and litigation expenses.
  • Minnesota Consumer Data Privacy Act — Civil penalties up to $7,500 per violation plus reasonable attorneys' fees; mandatory 30-day cure period expired 2026-01-31.
  • Minnesota Consumer Data Privacy Act (MCDPA) — civil penalties up to $7,500 per violation plus attorneys' fees; no statutory cap tied to revenue
  • The Minnesota Attorney General may bring an enforcement action for civil penalties of up to $7,500 per violation, plus reasonable attorney's fees and injunctive relief, under Minn. Stat. 8.31.
  • Minnesota Attorney General — The Attorney General has exclusive MCDPA enforcement authority, no private right of action exists, civil penalties of up to $7,500 per violation plus reasonable litigation expenses are available, and the mandatory 30-day warning-letter cure period expired January 31, 2026, after which the Attorney General may bring an enforcement action without prior notice.

Enforcement activity indexAmber

Hundreds of education letters and dozens of warning letters sent since July 2025; cure period sunset January 31, 2026.

Claims (7):

  • Since the MCDPA took effect, the Attorney General's Office sent hundreds of education letters and dozens of formal warning letters to companies regarding privacy policy, consent, and universal opt-out compliance issues, and the Act's mandatory pre-enforcement cure/notice period expired on January 31, 2026.
  • Minnesota Attorney General — On 2026-02-05 the AG announced the end of the mandatory warning/cure period and a shift to full enforcement, having received 200+ consumer complaints since 2025-07-31, many concerning the right to delete.
  • Minnesota Attorney General — The MN AG's office described its early cure-period enforcement engagement as generally resulting in productive, quick corrections by businesses.
  • Minnesota Attorney General's Office — The Minnesota AG's Office sent hundreds of education letters to companies during the MCDPA's initial warning period.
  • Minnesota Attorney General — More than 200 consumer complaints under the MCDPA and sent dozens of warning letters between 2025-07-31 and February 2026.
  • The MCDPA's mandatory 30-day cure period for alleged violations expired 2026-01-31; on 2026-02-05 the Attorney General announced the Act's full-enforcement phase, under which enforcement action may proceed without advance warning.
  • Minnesota Consumer Data Privacy Act enforcement record — As of the most recent secondary commentary reviewed, no publicly reported MCDPA enforcement action, settlement or civil-penalty decision has been located, notwithstanding the Attorney General's Feb 5 2026 announcement that the office had already issued 'dozens of warning letters' during the cure period.

Regulator funding and capacityGreen

MCDPA funded four new AGO attorneys plus an investigator dedicated to enforcement.

Claims (1):

  • The MCDPA included funding for the Attorney General's Office to hire four new attorneys and an investigator focused primarily on enforcing the Act, placing Minnesota among the most heavily resourced state privacy enforcers per independent industry analysis.

Collective redress and class actionsRed

No collective-redress/class-action mechanism specific to MCDPA identified; enforcement is AGO-exclusive.

Claims (1):

  • No collective-redress or class-action mechanism specific to MCDPA enforcement has been identified; enforcement is vested exclusively in the Attorney General.

Private right of actionRed

The MCDPA contains no private right of action.

Claims (3):

  • The MCDPA contains no private right of action; only the Attorney General may enforce the Act.
  • Minnesota Consumer Data Privacy Act — The MCDPA does not create a private right of action for violations.
  • Minnesota Consumer Data Privacy Act — No private right of action; enforcement is exclusively through the Attorney General.

Recent developments 180dAmber

June 2026: Minnesota joined an 18-attorney-general coalition opposing the federal SECURE Data Act on preemption grounds.

Claims (7):

  • In June 2026, Minnesota joined a coalition of 18 attorneys general and agencies opposing the proposed federal SECURE Data Act, with the Minnesota AGO stating the bill would preempt and weaken protections under the state's Consumer Data Privacy Act.
  • Minnesota Consumer Data Privacy Act — The MCDPA's mandatory 30-day cure/warning period sunset on January 31, 2026, removing the AG's prior obligation to warn before enforcing.
  • On June 2, 2026, the Minnesota Attorney General joined an 18-state coalition opposing the federal SECURE Data Act as a threat to MCDPA protections.
  • Minnesota Attorney General's Office — The MCDPA's 30-day advance-notice cure period expired January 31, 2026; the MN AG announced Feb 5, 2026 it can now bring enforcement actions without prior notice.
  • Minn. Stat. §325M.20(a) — The MCDPA's mandatory 30-day attorney-general warning-letter cure period expired 2026-01-31; for any enforcement action begun thereafter, no statutory warning letter or cure window applies.
  • General Motors — 36-state AG coalition settlement with GM, announced 2026-10-29; Minnesota's recovery is $7,095,664.
  • Minnesota joined a 36-state AG coalition settlement with General Motors, announced 2026-10-29, resolving allegations GM sold drivers' driving-behavior and location data to third parties including data brokers who resold to insurers without adequate consent; Minnesota's recovery is $7,095,664.
Category narrative 112 words

The AGO holds exclusive investigative and enforcement authority, able to seek injunctive relief, litigation expenses, and civil penalties up to $7,500 per violation; the Act carries no private right of action or identified class-action mechanism. A mandatory 30-day cure/notice period sunset on January 31, 2026, after which the AGO may bring enforcement actions without prior warning. The office was funded to add four attorneys and an investigator, and has sent hundreds of education letters and dozens of formal warning letters since the Act took effect. Within the last 180 days, Minnesota joined an 18-state coalition opposing the proposed federal SECURE Data Act, which the AGO says would preempt and weaken MCDPA protections.

Periodic update · new data 2026-10-18

The Minnesota Consumer Data Privacy Act's mandatory 30-day Attorney General warning-letter cure period under Minn. Stat. §325M.20(a) expired on 31 January 2026. Before that date, a business alleged to be in violation of the MCDPA was entitled to a 30-day warning letter and cure opportunity before the Attorney General could proceed to enforcement; for any enforcement action begun after 31 January 2026, no such statutory warning letter or cure window applies. This is a material tightening of the enforcement posture: the Attorney General may now bring enforcement actions immediately, without the earlier procedural cushion.

Consistent with that tightened posture, the Attorney General's office is understood to have received more than 200 consumer complaints under the MCDPA and to have sent dozens of warning letters in the period between the law's 31 July 2025 effective date and February 2026. No private right of action exists under the MCDPA, including under the general consumer-protection private-attorney-general provision at §8.31, subdivision 3a, so all of this enforcement activity runs exclusively through the Attorney General's office rather than through private litigation.

Outlook

The cure period's expiry removes the main procedural buffer between an alleged MCDPA violation and an actual enforcement action. The marker to watch is whether the volume of complaints already on file translates into a visible increase in enforcement actions now that the cure window is no longer available, and whether the Attorney General's office signals any informal practice of pre-enforcement outreach notwithstanding the absence of a statutory requirement to do so.

3 earlier distinct updates
Periodic update · new data 2026-10-11

The Minnesota Attorney General announced on 5 February 2026 the end of the mandatory warning-and-cure period under the Minnesota Consumer Data Privacy Act, Minnesota Statutes Chapter 325M, which vests exclusive enforcement authority in the Attorney General with no private right of action for consumers. The statutory cure period, which required 30 days notice and an opportunity to cure before enforcement, expired on 31 January 2026, six months after the Act took full effect on 31 July 2025. The Attorney General's announcement disclosed that the office had received more than 200 consumer complaints during that initial six-month period, a substantial portion of which concerned the right to delete personal data.

The Act's enforcement mechanism includes civil penalties of up to 7,500 dollars per violation, recoverable reasonable attorneys fees, and injunctive relief, all of which remain available to the Attorney General now that the cure buffer has lapsed. Because the statute excludes a private right of action, consumers whose complaints are not resolved through the Attorney General's process have no independent litigation avenue under this statute; their only redress channel is the Attorney General's enforcement discretion.

The shift from an education-first enforcement posture to full enforcement is itself the enforcement-and-redress development of this cycle: the underlying statutory penalty structure, complaint-handling process, and exclusive-authority design were established when the Act took effect in mid-2025 and have not changed. What has changed is that the procedural protection against immediate enforcement, the cure opportunity, no longer applies to new violations identified after 31 January 2026. No public fine or settlement under the Act had been identified as concluded as of this cycle.

Outlook

Whether the Attorney General's office proceeds to a public enforcement action, such as a fine or settlement, in the period following the 5 February 2026 full-enforcement announcement is the open question for subsequent cycles. The concentration of complaints around the right to delete suggests that any early enforcement action may focus on that obligation specifically, though this cannot be stated as established fact on the evidence available this cycle.

Periodic update · new data 2026-09-28

The Minnesota Consumer Data Privacy Act's cure-period provision, which required the Attorney General to give written notice of noncompliance and thirty days to cure before bringing an enforcement action, expired on January 31, 2026. The Minnesota Attorney General's Office confirmed on February 5, 2026 that it can now bring enforcement actions without providing advance notice, marking the state's transition from a notice-based enforcement posture to a direct-enforcement posture. The MCDPA carries exclusive enforcement authority with the Attorney General and there is no private right of action for Minnesota consumers; this exclusivity was established when the statute took effect on July 31, 2025 and is unchanged by the cure-period sunset. The Attorney General's February 5, 2026 announcement described this shift as strengthening the office's ability to protect consumer data, consistent with the broader pattern among comprehensive state privacy statutes of an initial grace period followed by a harder-edged enforcement phase once the statute has had time to bed in.

Outlook

The expiry of the cure period raises near-term compliance risk for controllers who had relied on the notice-and-cure window as an informal grace period. Whether the Attorney General has brought any concluded, non-warning enforcement action under the MCDPA since the January 31, 2026 expiry has not been confirmed and remains the key open question to watch in this jurisdiction.

Periodic update · new data 2026-09-22

Minnesota's enforcement posture under the Consumer Data Privacy Act shifted materially this cycle. The Act's mandatory 30-day cure/warning period, which had required the Attorney General to give controllers an opportunity to remedy violations before facing penalties, sunset on January 31, 2026. The Minnesota Attorney General's Office publicly confirmed this sunset on February 5, 2026, and in doing so noted that hundreds of education letters had been sent to companies during the initial warning period that preceded it.

The MCDPA's underlying enforcement design remains structurally unchanged around this development: the Attorney General holds exclusive enforcement authority over the Act, and there is no private right of action available to individual consumers. Violations are subject to civil penalties of up to $7,500 per violation, recoverable by the Attorney General together with injunctive relief and litigation expenses. What has changed is that these penalties are no longer preceded by a mandatory cure opportunity; controllers now face direct civil-penalty exposure for MCDPA violations without a guaranteed warning window.

This structural shift materially raises compliance risk for any organization doing business in Minnesota and subject to the Act's applicability thresholds, even though no public monetary enforcement action following the cure period's sunset has been confirmed as of this cycle. The Attorney General's confirmed communication about the sunset, combined with the prior education-letter campaign, is understood as a public signal that enforcement is expected to intensify following the transition, though the evidence available this cycle does not establish that any specific enforcement action has in fact been brought.

Outlook

The key question going forward is whether the Minnesota Attorney General brings or settles a post-cure-period enforcement action, which would be the clearest indicator of how the AG intends to exercise its now-unencumbered civil-penalty authority. This has not been established this cycle and is flagged as an open gap for future monitoring rather than assumed either way.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (26)
  1. Probable Minnesota Attorney General's Office — The Minnesota Attorney General may seek injunctive relief, litigation expenses, and civil penalties of up to $7,500 per violation against MCDPA violators. observed
  2. Probable Minnesota Attorney General's Office — Since the MCDPA took effect, the Attorney General's Office sent hundreds of education letters and dozens of formal warning letters to companies regarding privacy policy, consent, and universal opt-out compliance issues, and the Act's mandatory pre-enforcement cure/notice period expired on January 31, 2026. observed
  3. Probable Minnesota Attorney General's Office — The MCDPA included funding for the Attorney General's Office to hire four new attorneys and an investigator focused primarily on enforcing the Act, placing Minnesota among the most heavily resourced state privacy enforcers per independent industry analysis. observed
  4. Probable Minnesota Attorney General's Office — No collective-redress or class-action mechanism specific to MCDPA enforcement has been identified; enforcement is vested exclusively in the Attorney General. observed
  5. Probable Minnesota Attorney General's Office — The MCDPA contains no private right of action; only the Attorney General may enforce the Act. observed
  6. Probable Minnesota Attorney General's Office — In June 2026, Minnesota joined a coalition of 18 attorneys general and agencies opposing the proposed federal SECURE Data Act, with the Minnesota AGO stating the bill would preempt and weaken protections under the state's Consumer Data Privacy Act. observed
  7. Probable https://www.ag.state.mn.us/Office/Communications/2026/02/05_MCDPA.asp — Minnesota Attorney General — On 2026-02-05 the AG announced the end of the mandatory warning/cure period and a shift to full enforcement, having received 200+ consumer complaints since 2025-07-31, many concerning the right to delete.
  8. Probable https://www.ag.state.mn.us/Office/Communications/2026/02/05_MCDPA.asp — Minnesota Consumer Data Privacy Act — The MCDPA's mandatory 30-day cure/warning period sunset on January 31, 2026, removing the AG's prior obligation to warn before enforcing.
  9. Probable Minnesota Attorney General — After January 31, 2026, the Minnesota Attorney General is under no obligation to provide any warning letter to a potential violator before initiating an enforcement action. observed
  10. Probable Davis Wright Tremaine — Minnesota Attorney General — The MN AG's office described its early cure-period enforcement engagement as generally resulting in productive, quick corrections by businesses. observed
  11. Probable Minnesota Attorney General — On June 2, 2026, the Minnesota Attorney General joined an 18-state coalition opposing the federal SECURE Data Act as a threat to MCDPA protections. observed
  12. Probable The CommLaw Group — Minnesota Consumer Data Privacy Act — MCDPA violations are subject to civil penalties of up to $7,500 per violation, recoverable by the Attorney General along with injunctive relief and litigation expenses. observed
  13. Probable https://www.ag.state.mn.us/Office/Communications/2026/02/05_MCDPA.asp — Minnesota Attorney General's Office — The Minnesota AG's Office sent hundreds of education letters to companies during the MCDPA's initial warning period.
  14. Probable Minnesota Attorney General — Minnesota Consumer Data Privacy Act — The MCDPA does not create a private right of action for violations. observed
  15. Probable National Law Review — Minnesota Attorney General's Office — The MCDPA's 30-day advance-notice cure period expired January 31, 2026; the MN AG announced Feb 5, 2026 it can now bring enforcement actions without prior notice. observed
  16. Probable RecordingLaw — Minnesota Attorney General — More than 200 consumer complaints under the MCDPA and sent dozens of warning letters between 2025-07-31 and February 2026. observed
  17. Probable Madgett Law — Minn. Stat. §325M.20(a) — The MCDPA's mandatory 30-day attorney-general warning-letter cure period expired 2026-01-31; for any enforcement action begun thereafter, no statutory warning letter or cure window applies. observed
  18. Probable https://www.ag.state.mn.us/Office/Communications/2026/02/05_MCDPA.asp — Minnesota Consumer Data Privacy Act — Civil penalties up to $7,500 per violation plus reasonable attorneys' fees; mandatory 30-day cure period expired 2026-01-31.
  19. Probable https://www.whitecase.com/insight-alert/minnesota-enacts-comprehensive-consumer-data-privacy-law — Minnesota Consumer Data Privacy Act — No private right of action; enforcement is exclusively through the Attorney General.
  20. Probable Didomi — Minnesota Consumer Data Privacy Act (MCDPA) — civil penalties up to $7,500 per violation plus attorneys' fees; no statutory cap tied to revenue observed
  21. Probable The CommLaw Group — The Minnesota Attorney General may bring an enforcement action for civil penalties of up to $7,500 per violation, plus reasonable attorney's fees and injunctive relief, under Minn. Stat. 8.31. observed
  22. Probable The CommLaw Group — The MCDPA's mandatory 30-day cure period for alleged violations expired 2026-01-31; on 2026-02-05 the Attorney General announced the Act's full-enforcement phase, under which enforcement action may proceed without advance warning. observed
  23. Probable Minnesota Attorney General — General Motors — 36-state AG coalition settlement with GM, announced 2026-10-29; Minnesota's recovery is $7,095,664. observed
  24. Probable Minnesota Attorney General — Minnesota joined a 36-state AG coalition settlement with General Motors, announced 2026-10-29, resolving allegations GM sold drivers' driving-behavior and location data to third parties including data brokers who resold to insurers without adequate consent; Minnesota's recovery is $7,095,664. observed
  25. Probable Minnesota Attorney General — Minnesota Attorney General — The Attorney General has exclusive MCDPA enforcement authority, no private right of action exists, civil penalties of up to $7,500 per violation plus reasonable litigation expenses are available, and the mandatory 30-day warning-letter cure period expired January 31, 2026, after which the Attorney General may bring an enforcement action without prior notice. observed
  26. Uncertain Madgett for MN (commentary) — Minnesota Consumer Data Privacy Act enforcement record — As of the most recent secondary commentary reviewed, no publicly reported MCDPA enforcement action, settlement or civil-penalty decision has been located, notwithstanding the Attorney General's Feb 5 2026 announcement that the office had already issued 'dozens of warning letters' during the cure period. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 91 claim(s) (91 category placement(s)), 38 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (9 confirmed against the cited source; 2 contradicted by the cited source; 1 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressregulator powers and penalties
Art. 79Enforcement & Redresscollective redress and class actions
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties