Skip to content

Session Expired

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

Sign In Again

MD SB827: Consumer Protection and Product Liability - Chatbots

Dead/Failed Maryland · 2026 session

Last verified Oct 10, 2026 · official bill text

SB827 · where it stands

This bill did not become law (dead/failed) · last action Feb 12, 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 SB 827 (2026, first reader text, cross-filed with HB 1250) would have regulated operators and developers of generative AI chatbots made available to Maryland users: affirmative consent for training on input data, a ban on using chat logs for advertising, a 10-year cap on chat log retention, protections for users under 13, hourly not-human warnings, monthly safety testing, and product liability with possible strict liability. It had a Senate Finance hearing set for March 12, 2026 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 set consent, data, warning and testing duties for chatbot operators and developers and exposed them to product liability.

Key provisions

  1. Would have added Commercial Law Title 14, Subtitle 51 (sections 14-5101 to 14-5112; short title "Curbing Harmful AI Technology Act") and listed violations as unfair, abusive or deceptive trade practices under Title 13
  2. Chatbot: a generative AI system with a natural-language interface giving adaptive responses; operator: any person, including a developer, that makes a chatbot available to a user in Maryland
  3. Operators could not make available a chatbot capable of training on input data without affirmative consent, using chat logs for advertising decisions, profiling users beyond what a prompt needs, keeping chat logs more than 10 years unless required by law, or giving financial, legal or medical advice in violation of licensing law
  4. If an operator or developer knows or should know a user is under 13, no training on input data or processing of other personal data without written parental consent
  5. Persistent on-screen warning that the chatbot is artificial and not human, plus pop-up warnings requiring a response at the start, after each hour of continuous use, and when a user asks how it works; monthly safety testing with published findings
  6. Users could inspect and download their chat logs; operators could not sell chat logs or retaliate against users who refuse consent
  7. A chatbot is treated as a product with an affirmative duty not to harm users and possible strict liability; individuals could sue for injunction, declaratory relief or damages, with punitive damages up to three times actual damages for knowing violations; the Attorney General could seek declaratory relief
  8. Would have taken effect October 1, 2026

Latest legislative action

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

Sponsors (showing 5 of 16)

NameRole
Primary
Primary
Primary
Primary
Primary

Related and companion bills

Topics and industries

Affected 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