Five state laws · two already in force

Your Chatbot Says “Hi, How Can I Help?” In Four States That Now Require It To Say It Is Not A Person.

California’s bot disclosure law has been live since 2019 and its companion-chatbot law since January. Colorado, Washington and Oregon follow on 1 January 2027. Nobody on your team can tell you which of those reach the widget on your checkout page, what it currently discloses, or when anyone last checked.

Buy Now — $19
5
state laws tracked, side by side
2
already in force today
3
start 1 January 2027
$1,000
per violation under California SB 243

A register, not another explainer

There is no shortage of law-firm commentary on chatbot disclosure. There is nothing that tells you which of your own bots is exposed.

1

Rules matched per bot, not per company

Tick the states a bot can reach and pick what it does. A sales bot in California pulls the B.O.T. Act; a companion bot pulls SB 243 instead; a support bot in Colorado pulls a rule that has not started yet. The register works that out for each record.

2

“Not yet assessed” stays visible

A requirement nobody has checked is never quietly counted as met. It sits in its own band until someone answers it, so a half-configured bot cannot pass for a compliant one.

3

2027 readiness scored separately

Rules that start on 1 January 2027 are tracked as a readiness target rather than a failure today. A bot can be compliant now and still show a gap against next year.

4

A record you can hand over

One printable page per bot: which laws reach it, what the live deployment implements, the exact disclosure wording on record, when it was last reviewed and by whom.

The awkward part is not the law, it is the inventory. Most teams run a support widget, a sales bot and something a contractor installed two years ago, each with different wording and no owner. This keeps one row per bot, works out which of the five laws reach it, records what it actually does today, and puts a twelve-month review clock on it so the answer does not silently go stale.

What the register looks like

Eight example bots, every status band populated. This is the built-in example roster.

Chatbot Disclosure LogPer-bot register of US state AI disclosure duties
8 records
1
Compliant
1
Review due ≤30d
1
Review overdue
1
Not compliant
1
Not assessed
1
2027 readiness only
2
Out of scope
ChatbotStatesLaws in forceStatus
Companion coach beta
app.example.com · M. Larsen
CACA SB 243 Not compliant
A rule in force is not met: a crisis or self-harm escalation protocol.
Legacy upsell bot
help.example.com · unassigned
CA, WA, ORCA B.O.T. Act Review overdue
The 12-month review was due 135 days ago.
New companion pilot
app.example.com · M. Larsen
CACA SB 243 Not assessed
4 requirements in force are still marked not yet assessed.
Seasonal promo bot
promo landing pages · D. Achebe
CACA B.O.T. Act Review due ≤30d
The next review falls in 20 days.
Support widget (main site)
example.com · R. Okonjo
COfrom 2027: CO HB26-1263 2027 readiness only
Nothing on this list is in force for this bot yet.
Storefront sales bot
shop.example.com · D. Achebe
CA, COCA B.O.T. Act Compliant
Every rule in force is marked in place and the review is current.
Recruitment screener
careers.example.com · P. Nowak
CA Out of scope
None of the five listed laws reach a customer support bot in the states ticked.

What you get

A

Six requirements, tracked per bot

Opening disclosure, repeat reminders in long sessions, minor-specific safeguards, a crisis escalation route, a working handover to a human, and records you could hand a regulator. Each answered in place, not in place, or not yet assessed.

B

A jurisdiction tab you can read

One row per law: what it applies to, the disclosure it expects, the timing, how minors are treated, the exposure, and the specific thing to double-check before you rely on it.

C

Gap roll-up across the whole estate

Which requirement is missing on the most bots, and how many records are still unassessed. It is usually one requirement on several bots, not several on one.

D

Yours, offline, exportable

Everything is stored in your browser. Nothing is uploaded. CSV and JSON export, JSON restore, and an example roster to try it against before you enter real bots.

Built by Mulkern AI Systems. One file, no account, no subscription, no server. Open it, install it to your home screen if you want it offline, and it keeps working. Pay once.

One price, one file, no subscription

$19
One-time purchase
No account, no renewal, no per-seat pricing.
  • Unlimited chatbot records, stored in your browser
  • Five state laws matched automatically per bot
  • Seven status bands including a separate 2027 readiness score
  • Printable compliance packet for each bot
  • CSV and JSON export, JSON restore
  • Installs as an offline app on phone or desktop
  • Light and dark themes
Buy Now — $19