Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

MD HB952: Consumer Protection - Companion Chatbots - Regulation

Dead/Failed Maryland · 2026 session

Last verified Oct 10, 2026 · official bill text

HB952 · where it stands

This bill did not become law (dead/failed) · last action Mar 23, 2026.

What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

Maryland's HB 952 (2026, third reader text) would have required operators of companion chatbots available to Maryland users to keep and publish self-harm and minor sexual-content protocols, display warnings that the chatbot is not human (a persistent on-screen warning plus pop-ups at the start and after every hour of continuous use), limit personal data use, and run a complaint system. A chatbot would be treated as a product with strict liability exposure. It passed the House 123-4, was referred to Senate Finance, and died when the 2026 session ended.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

None: the bill died and did not become law. It would have required companion-chatbot operators to publish safety protocols, warn users and handle complaints.

Key provisions

  1. Would have added Commercial Law section 14-1330 and listed violations as unfair, abusive or deceptive trade practices under Title 13 (except section 13-411)
  2. Operators must maintain and publish a protocol keeping the chatbot from producing self-harm or suicide content for users who express such thoughts, with referral to the Maryland Behavioral Health Crisis Response System and 988 Lifeline
  3. Operators must maintain and publish a protocol preventing the chatbot from presenting minors with sexually explicit visual depictions or content urging sexually explicit conduct
  4. Clear, conspicuous warning that companion chatbots are artificially generated, not human, and may not be suitable for some minors; a developer would also have to show a persistent on-screen not-human warning and a pop-up requiring a response at the start, after every hour of continuous use, and when the user asks how the chatbot works
  5. A controller would have to limit personal data collection to what is reasonably necessary and proportionate, and could not use data on emotional state or mental health vulnerabilities to tailor algorithms to increase use
  6. Complaint system: review within 3 calendar days, remove violating content and report to the Office of Suicide Prevention; annual reports to the Office starting March 1, 2027
  7. A companion chatbot is treated as a product; operators and developers have an affirmative duty not to harm users and may be held strictly liable, and individuals may sue for design, manufacturing or marketing defects
  8. Would have taken effect October 1, 2026; passed the House 123-4 and died in Senate Finance

Latest legislative action

Mar 23, 2026. Hearing 3/26 at 1:00 p.m.; died when the Maryland General Assembly's 2026 session ended April 13, 2026

Sponsors (showing 5 of 61)

NameRole
Primary
Primary
Primary
Primary
Primary

Roll call votes

On Third Reading Mar 9, 2026

123 yea4 nay14 otherPassed

Topics and industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error