ProvenanceGuard
← Go back

← All guides

New York's Synthetic Performer Law: Disclosure for AI People in Ads

By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read

The short answer

New York's synthetic performer law, GBL section 396-b, effective 9 June 2026, targets commercial advertising that features an AI-generated person. The disclosure wording in ProvenanceGuard's evidence packs states it plainly: this advertisement features a synthetic performer generated using artificial intelligence. Sealing the ad imagery gives that disclosure a dated, checkable record behind it.

Seal an image free → Recover a reposted image Pricing

An AI model in an ad is not a stock photo with extra steps; in New York it is a regulated representation, and the advertiser, not the tool, carries the disclosure.

The practical reading of these dates is about preparation rather than panic. Duties that have already applied cannot be met retroactively for assets published unmarked, but a workflow adopted now, applied consistently to everything published from here on, with records kept per asset, is a defensible position that improves with every week it runs. The grace deadline in December 2026 is specifically about marking for pre-existing systems, which makes conformance testing of the marking itself, not just the policy around it, the urgent piece of work.

What is a synthetic performer? a person appearing in content who does not exist as photographed, generated using artificial intelligence; in New York's law, effective 9 June 2026, commercial advertising featuring one carries a disclosure duty.

Why synthetic performers in New York advertising matters

The legal backdrop in the product's own evidence wording is specific. The EU AI Act's Article 50 transparency duties have applied since 2 August 2026, and the marking grace period for systems already on the market before that date ends 2 December 2026. California's AI Transparency Act, SB 942, is operative from 2 August 2026. New York's synthetic performer law, in GBL section 396-b and effective 9 June 2026, covers disclosure where commercial advertising features a synthetic performer. The evidence packs carry disclosure wording for exactly these three jurisdictions.

None of that makes a provenance record a legal verdict, and ProvenanceGuard's packs say so themselves: evidence aid, not legal advice. What a record does is give counsel, a compliance team or a regulator something concrete to work from: the file, its hashes, the tool that sealed it, the timestamps, the declared disclosure and the wording used. Organisations that can produce that pack in minutes answer questions very differently from organisations reconstructing a publication history from chat logs and memory.

How the record is built

There is also a tone question. A custody strip that looks like part of the work's presentation, clearly worded and consistently used, reads as professionalism rather than apology. Teams that label every AI asset the same way, from the first post rather than after a complaint, find the label becomes part of their brand's trust signal. The creators who struggle are usually the ones who labelled inconsistently, so that an unlabelled repost looks like concealment next to their labelled originals.

A visible label does the communicating that metadata cannot. Most people who see an image will never open its properties, and most platforms will never show them a credentials panel. A label in the pixels, naming the content as AI-generated, is read by exactly the audience the disclosure rules exist for, on exactly the surface where they encounter it. ProvenanceGuard's labelled copy carries that strip as part of the image, so the disclosure travels with the pixels instead of depending on a caption that can be separated from them.

Where it meets the real world

Labels have their own failure modes, and a serious workflow plans for them. A label placed along an edge can be cropped out; a label rendered too small becomes illegible after a platform resize; a screenshot of the centre of an image may exclude it entirely. That is why the visible label is one layer among several: the survival re-checks specifically test whether the label remains detectable after simulated platform transforms, and the registry fingerprint remains as the fallback when the label is gone.

An evidence pack is the record, packaged for a reader who was not there. For a sealed asset it contains the exhibit ID and verification URL, the original and sealed SHA-256 hashes, the perceptual fingerprint, the file's format and dimensions, the tool identification and version, the registration timestamp, the creator and disclosure as declared, the inspection results for the original bytes, and disclosure wording by jurisdiction for the EU, California and New York. Exporting the pack is a Pro and Team feature, because it is the point where a working record becomes a compliance artefact.

Putting it into practice

The pack's value is mostly about timing and completeness under pressure. A brand safety question, a platform appeal, a client audit or a regulator's letter all arrive with deadlines, and all of them ask the same underlying questions: which file, made how, declared as what, published when. A team that exports the pack and sends it the same day looks, and is, organised. A team assembling screenshots and recollections does not, however innocent its actual process was. Evidence does not create innocence, but it is how innocence is demonstrated.

Provenance is the record of where a piece of content came from and what has happened to it since: who or what created it, when it was registered, and which copies descend from the original. For an AI-generated image that record matters because the file itself is easy to copy, rename, crop and re-upload, and none of those actions leaves a reliable trace inside a filename. A provenance record kept outside the file, in a registry keyed to the file's fingerprints, survives exactly the handling that erases the signals embedded in the file.

Five actions to take

  1. Flag every ad concept that features a generated person before production, not after
  2. Seal the final frames and file the pack with the buy documentation
  3. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
  4. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  5. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned

A worked example: An agency producing a watch advertisement with an AI presenter

The team sealed the 8 campaign frames, used the New York wording in the evidence pack and the visible label on social cuts, and kept the pack with the media buy so the client's compliance sign-off referenced records, not recollections.

Notice what made the difference: not a better argument, but a record created before it was needed, carrying dates and hashes a stranger could check. That is the whole pattern this guide recommends, applied at the scale of one team and one deadline.

FAQ

Does the law cover AI backgrounds or products in ads?

As the product records it, the law is about synthetic performers in commercial advertising. The safe workflow is the same for the whole frame anyway: seal it, label it, and keep the pack, so the performer disclosure sits inside a complete record.

What does the free tier actually do?

The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.

What do Pro and Team cost?

Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.

Are my uploaded originals stored?

No. The registry keeps the sealed and labelled copies derived at sealing time and the registry record, so downloads and verification keep working, while the uploaded original bytes are not retained.

Seal an image free →