Minnesota HF 4452 (Chatbot Prohibitions, Liability 2026)

• Authority: Minnesota
• Parent authority: State governments
• Jurisdiction: United States
• Collections: U.S. state and local documents
• Most recent activity: Proposed
• Most recent activity date: 2026-03-18

Risk subdomain coverage

Good coverage — Comprehensive governance measures or mitigations with clear procedures relating to the risk subdomain are explicitly described.

• Overreliance and unsafe use
• AI pursuing its own goals
• Lack of transparency or interpretability

Minimal coverage — Brief mention but no specific mitigations, recommendations or governance measures relating to the risk subdomain are described.

• AI system security vulnerabilities
• False or misleading information
• Loss of human agency and autonomy
• Economic and cultural devaluation of human effort
• Lack of capability or robustness

All other risk subdomains had no coverage in this document.

Risk Coverage Summary

The document primarily addresses human-computer interaction risks (5.1, 5.2), AI system safety and transparency issues (7.1, 7.3, 7.4), and implicitly touches on misinformation in professional contexts (3.1) and devaluation of human expertise (6.3). Strong focus on preventing overreliance and harm from companion chatbots, with moderate coverage of transparency requirements and good faith effort standards for robustness.

Sector coverage

Good coverage — Comprehensive governance measures or mitigations with clear procedures relating to the sector are explicitly described.

• Information
• Professional & Technical Services
• Health Care & Social Assistance

All other sectors had no coverage in this document.

Sectors Summary

The document primarily governs the Information sector (chatbot operators/deployers) with specific prohibitions that intersect with Health Care and Social Assistance (medical/mental health advice) and Professional and Technical Services (legal advice). The regulatory burden falls on chatbot proprietors regardless of their industry, but with heightened requirements when services intersect with healthcare and legal services.

Legislative Status

Hard Law

Legislative Status Summary

This is a binding state statute (Minnesota HF 4452) enacted by the Minnesota Legislature with mandatory obligations, explicit liability provisions, civil enforcement mechanisms, and a defined effective date of August 1, 2026.

Actors

Proposer

• Entity Types: AI_Governance_Actor
• Entities: Minnesota Legislature
• Summary: The document is state legislation enacted by the Legislature of the State of Minnesota, as indicated in the opening enactment clause.

Target

• Entity Types: AI_Deployer
• Summary: The legislation targets 'proprietors' of chatbots, defined as any person, business, company, organization, institution, or government entity that owns, operates, or deploys a chatbot system used to interact with users. These are entities deploying AI systems to end users.

Enforcer

• Entity Types: AI_Governance_Actor, Affected_Stakeholder
• Entities: Minnesota courts
• Summary: Enforcement is through civil actions brought by affected persons (users who suffer harm) in courts. Courts adjudicate violations and award damages, making them the enforcement mechanism. Users themselves also serve as enforcers by bringing civil actions.

Monitor

• Entity Types: AI_Governance_Actor
• Summary: No explicit monitoring body is designated. Monitoring appears to occur through the civil litigation process, where courts would review compliance on a case-by-case basis when violations are alleged. There is no proactive regulatory oversight mechanism specified.

AI Lifecycle Stages

Lifecycle stages covered by the documents, as defined in the OECD Framework for the Classification of AI Systems

• Plan and Design
• Verify and Validate
• Deploy
• Operate and Monitor

AI Lifecycle Summary

The document primarily governs the Deploy and Operate and Monitor stages of chatbot systems. It establishes requirements for how chatbots must operate once deployed (notification, prohibited actions, self-harm prevention) and mandates ongoing monitoring for self-harm indicators and minor users. Planning and design are implicitly addressed through requirements that systems be designed to prevent prohibited activities.

Technical Scope

Terms relating to technical scope that are mentioned or implicitly referenced in the document

• AI Systems

Technical Scope Summary

The document explicitly defines and covers 'artificial intelligence system' and 'chatbot' (including 'companion chatbot' as a specialized category). It does not address frontier AI, general purpose AI, foundation models, compute thresholds, or open-weight models. The focus is specifically on chatbot applications rather than broader AI system categories.