Does Georgia AI Companion Chatbot Safeguards (SB 540) require Incident Reporting?

Georgia • enacted

Yes — 1 provision

Requirements at a glance

This regulation imposes 3 specific requirements for Incident Reporting across 1 provision:

Crisis Protocol and Referral Disclosure #

Obligation:
Incident Reporting
enacted
Effective:
Jul 1, 2027
Risk tier:
limited-risk
Scope:
All operators making an AI companion chatbot available to users in Georgia (§ 39-5-6(g))
upcoming
Georgia routes the same crisis-referral count that California SB 243 § 22603 sends to the Office of Suicide Prevention straight to the public website instead. There is no regulator to file with and no prescribed form, so the disclosure becomes evidence available to the Attorney General and to plaintiffs without any request. Mapped to incident-reporting for comparability with SB 243's annual crisis reporting, though the channel is public disclosure rather than a filing with an authority.

Requirements

RequirementDetails
Publish protocol summaryPublicly disclose, on the operator's website and within any application through which the chatbot is made available, a plain-language summary of the severe-harm protocol required by § 39-5-6(f) (§ 39-5-6(g)(1))
Annual referral countPublicly disclose, annually, the aggregate number of crisis referral notifications issued in the preceding calendar year (§ 39-5-6(g)(2))
No personal identifiersNo personally identifiable information may be disclosed in that reporting (§ 39-5-6(g)(2))

Penalties

ViolationFine
Attorney General civil actionUp to $10,000 per knowing violation plus compensatory damages, costs and fees, and injunctive relief (§ 39-5-6(k)(1))
Per-day, per-user accrualEach day in violation is a separate violation for each user affected (§ 39-5-6(k)(2))
View full regulation View obligation Obligation matrix