← Go back

Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team

California's AI Transparency Act: The Other 2026 Date for Chatbot Builders

The short answer

CompanionGuard's summary pairs two 2026 transparency timelines: EU AI Act Article 50 duties applied from 2 August 2026, 'and California's AI Transparency Act is operative the same date'. For companion builders this means California carries two transparency regimes at once — SB 243's companion-specific duties (operative 1 January 2026) and the broader Transparency Act — and the same disclosure mechanisms answer both. This page is the toolkit's orientation, not legal advice.

What is the California AI Transparency Act, for a bot builder?

In CompanionGuard's summary, it is California's general AI transparency law, operative 2 August 2026 — distinct from SB 243, the companion-chatbot-specific law operative since 1 January 2026. A companion builder in California therefore works under both: the companion duties (disclosure, protocol, referral, minors, reporting) and the state's general transparency expectations for AI interaction.

Create the free safety kit Next guide All guides

CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.

Two California regimes, one disclosure habit

It is easy to treat 'California AI law' as one thing. The product's own materials distinguish two: the SB 243 pack, companion-specific, with its five listed duties; and the AI Transparency Act, named in the llms summary with its 2 August 2026 operative date. The practical overlap is large — both regimes want users to know they are dealing with AI — but the sources differ, and a builder verifying their position should verify against both, not assume the companion pack exhausts California.

The engineering conclusion is reassuring: nothing in the Transparency Act's arrival asks for a different disclosure mechanism than the one SB 243 already required. The banner at first interaction, disclosure on request, the public protocol page and per-session disclosure state form one habit that answers the transparency instinct wherever it is codified. Build the habit once; map it to each regime's text with counsel.

Why 2 August 2026 mattered twice

The same calendar date carried the EU Article 50 application and California's Transparency Act operative date, per the product's summary — a coincidence worth noticing because it marks the moment 'transparency is coming' stopped being true anywhere in this product's world. After August 2026, every regime CompanionGuard tracks has its transparency duty either live (California both laws, EU) or dated (Colorado, 1 January 2027).

For planning, that collapses the strategy space: there is no longer a major-market version of a companion bot that may skip disclosure while remaining within the tracked regimes. The remaining design questions are about quality — how clear, how early, how evidenced — which is a better class of question for a builder to be answering. The Article 50 guide covers the European side of the same date.

Transparency beyond the banner

A general transparency act invites a broader reading than a banner checklist: transparency as a property of the whole interaction. Does the bot's marketing imply a human? Do its store screenshots show disclaimers or hide them? When the bot is quoted, embedded or white-labelled by a partner, does the disclosure travel with it? CompanionGuard's embeddable snippet is built for the travelling case — the disclosure and crisis line ride inside the embed itself (the /embed script), so a partner page showing your bot shows your disclosure too.

The protocol page plays the same role for the public record: a single stable URL where what-the-bot-is is stated in the operator's own name. Transparency regimes are ultimately about whether a person encountering the system — as user, parent, partner or reviewer — can discover the truth without special access. Audit your surfaces with that person's eyes, not your counsel's checklist alone.

Keeping the summary honest

This guide is deliberately thin where the product is thin: CompanionGuard's materials name the Transparency Act and its date but do not publish a duty pack for it comparable to the SB 243 and Colorado packs. Inventing one here would be exactly the kind of confident fabrication the product refuses elsewhere. What the product does claim is its mechanism set and the dates above; what it instructs, implicitly, is verification against the Act's text for anything more.

That restraint is worth copying in your own compliance writing. State what your mechanisms do; cite the regimes and dates you are tracking; mark summaries as summaries. The builders who get in trouble with transparency law are rarely the ones who disclosed too precisely.

Five actions for California's double transparency regime

  1. List both California regimes in your compliance notes — SB 243 (operative 1 Jan 2026, companion-specific) and the AI Transparency Act (operative 2 Aug 2026) — as separate verification items for counsel.
  2. Confirm the disclosure banner appears at first interaction and on request; that single habit is the shared core of both regimes.
  3. Audit marketing surfaces — store pages, screenshots, partner embeds — for anything implying a human, and confirm the embed carries the disclosure with it.
  4. Link the public protocol page from every California-facing surface, so the transparency statement is one click from any encounter.
  5. Keep the runtime's disclosure evidence accumulating; when two regimes ask the same question, per-session proof is the shortest answer to both.

Worked example: one audit, two regimes, zero new machinery

A fictional California companion, Golden Hour, commissions a compliance review in September 2026 expecting two work programmes: one for SB 243 (done in January) and a new one for the Transparency Act. The review's actual finding is narrower: the SB 243 mechanisms — banner, on-request disclosure, protocol page, runtime state — already embody the transparency the second regime asks about; the gaps are presentational, not architectural. Two store screenshots crop out the banner; a partner's embedded demo strips the snippet's footer line.

The fixes take days: recapture the screenshots with the banner in frame, and re-issue the partner embed so the disclosure and crisis line render inside it (the embed script carries both by design). The review closes with counsel verifying the mapping against both texts. The story is invented; the dates and mechanisms are the product's own — and the moral, that transparency failures are usually surface failures, is the product's design premise.

Frequently asked questions

When did California's AI Transparency Act become operative?

Per CompanionGuard's summary: California's AI Transparency Act is operative 2 August 2026 — the same date the summary gives for EU AI Act Article 50 duties applying.

How is it different from SB 243?

SB 243 is companion-chatbot-specific, operative 1 January 2026, with the pack's five duties: disclosure at first interaction and on request, a published prevention protocol, crisis referral, minor break reminders, and annual reporting from 1 July 2027. The Transparency Act is California's broader AI transparency law; the product names it and its date without publishing a separate duty pack.

Do I need different mechanisms for the two California laws?

The disclosure habit is shared: banner at first interaction, disclosure on request, a public protocol page, per-session disclosure state in the runtime. Verify the mapping against both texts with counsel; the engineering is one build.

Does disclosure travel when my bot is embedded elsewhere?

In CompanionGuard, yes: the embeddable snippet carries the disclosure and crisis line inside the embed, so partner pages showing the bot show the disclosure. Audit partner surfaces anyway — screenshots and custom wrappers are where disclosure gets cropped.

Is this guide a complete statement of the Transparency Act?

No. It reflects what the product's own materials state — the Act's name and operative date — plus the mechanism mapping. The Act's full duties are a counsel question against its text; CompanionGuard is a toolkit, not legal advice.

Keep going