Companion chatbot laws · what to count and keep · updated

New York's AI companion law: General Business Law Article 47

Since 5 November 2025, New York has required an operator of an AI companion to keep a protocol that detects expressions of suicidal ideation or self-harm and refers the user to crisis services such as 988, and to tell users they are not talking to a human at the start of an interaction and “at least every three hours for continuing AI companion interactions” (N.Y. Gen. Bus. Law § 1702) (read 9 October 2026). The Attorney General enforces it, with civil penalties of up to $15,000 a day. New York asks for no yearly number; the record it implies is the notice's schedule and the sessions that ran past it, and the protocol by version.

Each duty, in the statute's words

N.Y. Gen. Bus. Law §§ 1700–1704; in force since 5 November 2025.

a protocol to detect expressions of suicidal ideation or self-harm and refer the user to crisis services

“a notification to the user that refers them to crisis service providers such as the 9-8-8 suicide prevention and behavioral health crisis hotline”

N.Y. Gen. Bus. Law § 1701

Applies from 5 November 2025. To keep: the protocol document, each version with the date it took effect.

a notice that the user is not talking to a human, at the start of an interaction (not more than once a day)

“at the beginning of any AI companion interaction which need not exceed once per day”

N.Y. Gen. Bus. Law § 1702

Applies from 5 November 2025. To keep: when the notice shows: its text, each release that changed it, and the sessions that began without it.

the same notice again at least every three hours of a continuing interaction

“at least every three hours for continuing AI companion interactions”

N.Y. Gen. Bus. Law § 1702

Applies from 5 November 2025. To keep: the interval the app uses, and the sessions that ran past it without the notice.

Enforcement

The Attorney General may sue for an injunction and civil penalties of up to $15,000 a day for a violation of § 1701 or § 1702 (§ 1703).

A hosted record of your crisis-referral counts and notice cadence, with the Oregon and Washington public pages kept current for you, is not built

It would take your daily totals (never a conversation or anything about a user), keep them in a hash-chained log with each protocol version, and keep California's yearly draft and the Oregon and Washington pages current.

What exists today: these pages, and the counts and documents you keep yourself. okgate's hash-chained log records the tool calls AI agents make, not your app's events, so it cannot keep this record today.

I want that record

Sources, each read on 9 October 2026