Key takeaways
- California SB 942, the AI Transparency Act, applies to covered providers: anyone who produces a generative AI system that is publicly accessible in California. SB 1000 removed the old 1,000,000-user threshold on 30 September 2026. Covered-provider duties have been operative since 2 August 2026.
- The mandatory latent disclosure, in practice an imperceptible watermark embedded in the image, video or audio, must carry five fields, directly or through a link to a permanent website: provider name, system name and version, time and date, a unique identifier, and whether the system created or altered the content. A bare 'AI-generated' signal does not qualify.
- Providers must also offer a free disclosure verification tool (the 'AI detection tool' before SB 1000) with upload, URL input and an API, or direct users to a compliant third-party one. If a licensee's system stops complying, the provider has 72 hours to end the licence or notify the licensee.
- Each violation carries a $5,000 penalty, and every day a violation continues counts as a separate violation. AB 853 adds duties for large platforms (1 January 2027, since rewritten by AB 2713) and capture devices (1 January 2028).
What SB 942 requires
California's AI Transparency Act requires a covered provider (anyone who produces a generative AI system that is publicly accessible in California) to embed a latent disclosure, in practice an imperceptible watermark, in the image, video and audio its system creates or alters, to offer a free disclosure verification tool, and to act when a licensee stops keeping the disclosure intact. It has been operative since 2 August 2026, and each day of violation is a separate $5,000 penalty.
The Act is California Business and Professions Code, Chapter 25 (commencing with Section 22757), enacted by SB 942 and amended by AB 853, then by SB 1000 and AB 2713 on 30 September 2026. SB 1000 is an urgency statute, so its changes applied the day it was signed. Unlike EU AI Act Article 50, SB 942 is specific about what the mark has to say.
Are you a covered provider?
§ 22757.1 defines a covered provider as a person that creates, codes or otherwise produces a generative artificial intelligence system that is publicly accessible within the geographic boundaries of California. Until SB 1000, the system also had to have over 1,000,000 monthly users. That threshold is gone.
Four things follow, and each catches somebody out:
- There is no size test. Not users, not revenue, not headcount. A small team with a niche product is covered as much as a large one.
- It is not a California-company test. Public accessibility within California is what matters, so a provider anywhere in the world can be covered.
- The 2,000,000 figure is not a provider threshold. The number people often quote belongs to AB 853's separate large online platform duties, below.
- The exemptions are narrow. SB 1000 leaves two: products that provide exclusively non-user-generated videogames, and, until 1 January 2029, systems designed primarily as assistive technology.
The latent disclosure, field by field
§ 22757.3 requires a latent disclosure, to the extent it is technically feasible, in image, video or audio content the system creates or alters. It can convey the fields directly or through a link to a permanent website. This is the part of the statute that decides whether a watermark is adequate, because a bare “this is AI” signal does not carry these fields.
| In practice | |
|---|---|
| Provider name | The name of the covered provider |
| System name and version | Which generative AI system, and which version of it, created or altered the content |
| Time and date | When the content was created or altered |
| Unique identifier | An identifier for the content itself |
| Created or altered | Whether the system created the content or altered existing content (added by SB 1000) |
From 1 January 2029 the disclosure must also say whether the system is designed primarily as assistive technology.
The statute also requires the latent disclosure to be compatible with the provider's disclosure verification tool, compliant or interoperable with widely recognized industry standards, and permanent or extraordinarily difficult to remove or tamper with.
No visible label any more
As first enacted, SB 942 also made a covered provider offer users the option of a visible disclosure identifying content as AI-generated. SB 1000 deleted that option. The latent disclosure is now the only disclosure the statute asks a provider to put in the content.
The disclosure verification tool you have to offer
§ 22757.2 is the requirement most often missed, because it is not about the content at all — it is a product you must offer. A covered provider must make available a disclosure verification tool (the “AI detection tool” before SB 1000) that:
- is available at no cost to the user;
- lets a user assess whether image, video or audio content was created or altered by the provider's system;
- outputs any system provenance data detected in the content;
- outputs no personal information unless the person it relates to expressly consents;
- is publicly accessible (reasonable limits against security risks or misuse are allowed), and lets a user upload content or provide a URL;
- supports an API, so a user can invoke it without visiting the provider's website;
- collects user feedback on its performance.
There is a strict privacy limit attached: the provider may not collect, use, retain or sell personal information beyond what is strictly necessary, though users can opt in to be contacted. A tool that logs everything submitted to it is its own compliance problem.
A third-party tool is allowed
SB 1000 lets a provider meet this duty by directing users to a third-party disclosure verification tool. The tool must comply with § 22757.2, be compatible with the latent disclosures in the provider's content, and be clearly and conspicuously accessible through the provider's generative AI user interface.
Licensees, and the 72-hour clock
Under § 22757.3(b), as amended by SB 1000, a covered provider that licenses its system to a third party must notify the licensee of its obligations under the Act.
If the provider knows an identifiable licensee has modified the system so that it no longer complies, the provider has 72 hours from discovery to either end the licence, or notify the licensee of the noncompliance and of its duty to report. The licensee then has 96 hours from that notice to fix the system or stop using it, and to report back. If it does not, the provider reports it to the Attorney General.
SB 1000 also says the provider has no duty to monitor or investigate its licensees. The clock starts when the provider knows. In practice this is an operational duty, not a legal one: once you know, you have three days to act, and most providers discover they have no mechanism for that.
What AB 853 added
AB 853 moved the provider duties to 2 August 2026 and extended the Act to three new parties. If you are not a covered provider, you may still be one of these.
| From | Duty | |
|---|---|---|
| Large online platforms | 1 Jan 2027 | As rewritten by AB 2713: detect provenance data in distributed content, show users whether it is present, and let them inspect it in the platform's own interface, through a link to a website or app (a third party's is allowed), or as a download. Must not knowingly strip provenance data or signatures, including on download. Over 2,000,000 unique monthly users in California; broadband and telephone services excluded |
| GenAI hosting platforms | 1 Jan 2027 | Must not knowingly make available a generative AI system that does not include the required latent disclosure |
| Capture device manufacturers | 1 Jan 2028 | Give users the option to include a latent disclosure in captured content, and provenance data reflecting the device's authenticity |
The platform duty is worth reading carefully: it is a multi-standard detection obligation, not a single-vendor one. Under AB 2713, a platform need not act on provenance that is not compliant or interoperable with widely adopted specifications from an established standards-setting body — C2PA first — and a watermark is the layer that survives when a manifest has been stripped. The detail is on our AB 853 page.
Dates
- SB 942 signed and chaptered. Source
- AB 853 signed. Provider duties moved from 1 January 2026 to 2 August 2026; platform, hosting and device duties added. Source
- Covered-provider duties operative: the latent disclosure, the free tool and the licensee duties.
- SB 1000 signed, in force immediately as an urgency statute: no user threshold, the disclosure verification tool (a third party's allowed), no visible-label option, a fifth latent-disclosure field, and the 72-hour licensee rule. AB 2713 signed the same day, rewriting the large online platform duties. Source
- Large online platform duties (as amended by AB 2713) and GenAI hosting platform duties operative.
- Capture device manufacturer duties operative.
- The assistive-technology exemption and the $50,000 penalty for falsely claiming it end; the latent disclosure must also say whether a system is designed primarily as assistive technology.
Penalties
Under § 22757.4, a covered provider that violates the chapter is liable for a civil penalty of $5,000 per violation, and each day a violation continues is a discrete violation. Actions may be brought by the Attorney General, a county counsel or a city attorney.
That daily multiplier is the part worth internalising. This is not a one-off fine — an unresolved gap accrues. A licensee's violation is treated separately from the provider's own duties.
SB 1000 adds a second penalty until 1 January 2029: $50,000 per violation, per day, for falsely representing a generative AI system as designed primarily as assistive technology, the category that is exempt until then.
SB 942 is not the EU AI Act
These two are routinely conflated, and the difference decides what your watermark has to carry.
| Requires | Does not require |
|---|---|
| SB 942: a payload carrying provider, system and version, timestamp, a unique identifier, and whether the system created or altered the content | Article 50: no specified fields — marking and detectability only |
| SB 942: a free disclosure verification tool with upload, URL input and an API (a compliant third-party tool is allowed) | Article 50: no detector duty in the article itself; the Code of Practice asks signatories for free detection |
| SB 942: licensee notice and a 72-hour duty to act on a noncompliant licensee | Article 50: no equivalent licensee mechanism |
A system built only for Article 50 — a bare “AI-generated” signal — does not satisfy SB 942, because it cannot name the provider or the version. A system built for SB 942 generally does satisfy Article 50(2). See our Article 50 page for the other side.
One more commonly-confused neighbour: AB 2013 is the training-data documentation law. Different subject, frequently searched alongside SB 942.
How Verda maps to the statute
SB 942 is the regime where Verda's payload design matters most, because the statute enumerates fields rather than leaving them open.
| The duty | Tier | How Verda meets it |
|---|---|---|
| Latent disclosure, permanent or extraordinarily difficult to remove or tamper with | Compliance | An imperceptible watermark embedded in the signal, which survives transformations that strip metadata |
| Provider name, system name and version, time and date, unique identifier | Provenance | The mark resolves through a registry to exactly these fields. SB 1000 expressly lets a latent disclosure convey its fields through a link to a permanent website |
| Whether the system created or altered the content | Provenance | The provider can record it in the metadata attached to the registry record |
| Free disclosure verification tool, upload and URL input, with an API | Compliance | Public verification at no cost and no account, plus a documented decode API. SB 1000 lets a provider direct its users to a compliant third-party tool |
| Outputs system provenance, no personal information without consent | Compliance | Public verification returns the provider record; it does not return personal identity |
| Not required since SB 1000: a visible label | Provenance | A visible badge is available and optional, alongside the invisible mark |
| Not required by the statute | Identity | The provider record can optionally be a KYC-verified organisation — for fraud and brand, not for compliance |
On the AB 853 platform side, as amended by AB 2713, the requirement is to read provenance that follows widely adopted specifications. Verda writes signed C2PA manifests as well as the watermark, and is registered on the C2PA soft-binding algorithm list for image, audio and video.
Common questions
Is California SB 942 in force?
Yes. Covered-provider duties have been operative since 2 August 2026, and SB 1000 amended them with immediate effect on 30 September 2026. AB 853 moved the start date from 1 January 2026; large online platform and GenAI hosting platform duties follow on 1 January 2027, and capture device duties on 1 January 2028.
What did SB 1000 change in SB 942?
SB 1000, signed on 30 September 2026 and in force immediately, removed the 1,000,000-user threshold, renamed the AI detection tool the disclosure verification tool and allowed a provider to direct users to a compliant third-party tool, deleted the optional visible disclosure, added a fifth field to the latent disclosure (whether the system created or altered the content), and gave providers 72 hours to act on a noncompliant licensee.
What counts as a covered provider under SB 942?
Any person that creates, codes or otherwise produces a generative AI system that is publicly accessible within California. SB 1000 removed the old 1,000,000-user threshold, so there is no size test, and the provider does not have to be a California company.
Is a watermark enough to comply with SB 942?
Only if it carries the five required fields, directly or through a link to a permanent website. A watermark that signals 'AI-generated' and nothing more does not meet section 22757.3, because it cannot convey the provider name, the system name and version, the time and date, or a unique identifier. The free disclosure verification tool in section 22757.2 is a separate duty.
Does SB 942 require me to build my own AI detection tool?
No. Since SB 1000 the tool is called the disclosure verification tool, and the statute says a provider may meet the duty by directing users to a third-party tool that complies with section 22757.2, is compatible with the latent disclosures in its content, and is clearly and conspicuously accessible through its generative AI user interface. Either way the tool must be free, accept an upload or a URL, and offer an API.
What is the penalty for breaching SB 942?
$5,000 per violation, and each day a violation continues counts as a discrete violation. Actions may be brought by the Attorney General, a county counsel or a city attorney. Until 1 January 2029, falsely representing a system as designed primarily as assistive technology carries $50,000 per violation, per day.
Does this affect me?
Tell us about your product and we'll walk you through what SB 942 requires and how Verda's watermark and verification tool cover it.