Can Minnesota consumers opt out of AI profiling?
Answer
Yes. Minnesota HF-4757 gives consumers the right to opt out of automated profiling decisions that produce legal or similarly significant effects. Controllers must honor opt-out requests within a reasonable time frame and may not deny goods, services, or employment opportunities solely because a consumer exercised this right. The opt-out right applies to profiling used in employment, lending, insurance, and similar high-stakes contexts.
Applicable Regulations
Minnesota Consumer Data Privacy Act (MCDPA)
Enacted May 24, 2024 as Chapter 121 of the 2024 Minnesota Session Laws, codified at Minnesota Statutes Chapter 325O. Effective July 31, 2025 with full enforcement (no cure period) from February 1, 2026. Applies to controllers and processors of personal data of Minnesota residents meeting the thresholds below. Grants consumers rights to access, correct, delete, and port personal data; to opt out of targeted advertising, data sales, and profiling; and — uniquely among state laws — to question the result of a profiling decision, receive the reason for that outcome, and request reevaluation if inaccurate data was used. Requires data protection assessments before processing personal data for targeted advertising, data sales, sensitive data, and profiling with heightened risk. Enforced exclusively by the Minnesota Attorney General; no private right of action.
Key Requirements
Full State Analysis
Where this lands operationally
Gridex turns the compliance or coverage question into operated workflow controls: intake, review points, audit trails, and the places a person stays in the decision.
Map This Workflow With Gridex
Use this research to identify the workflow, review points, and operating controls that would matter in your organization.
Map This Workflow With Gridex →Related Questions
- Does the Minnesota Consumer Data Privacy Act cover employment AI decisions? Yes. Minnesota HF-4757 classifies AI-based employment profiling — including automated resume screening, candidate scoring, and interview analysis — as high-risk processing that requires a data protection assessment. Controllers must document the purpose, necessity, and risk of harm before deploying such systems, and employees and applicants retain the right to opt out of solely automated employment decisions.
- When is a data protection assessment required in Minnesota? Minnesota HF-4757 requires controllers to conduct data protection assessments before processing personal data in ways that present a reasonably foreseeable risk of harm to consumers. Mandatory triggers include: automated profiling that produces legal or significant effects, processing sensitive personal data, and AI-based decisions in employment, insurance, lending, or healthcare. Assessments must weigh the benefits of processing against the risks and document risk mitigation measures.
- How do Colorado and Minnesota AI privacy requirements compare? The two states take different approaches. Colorado's AI Act (SB 26-189, which repealed and reenacted SB 24-205 and whose obligations begin January 1, 2027) is a disclosure-and-notice framework: it does not require data protection assessments or high-risk AI classification. Instead, deployers of automated decision-making technology (ADMT) that makes or substantially influences consequential decisions must give consumers interaction notice, disclose adverse outcomes within 30 days, allow data correction, and provide meaningful human review. Minnesota HF-4757 takes the opposite approach, embedding AI governance within broader consumer data privacy protections and requiring data protection assessments before processing that presents foreseeable risk — including automated profiling producing legal or significant effects.