Make disclosure travel with the campaign

Disclosure is a distribution problem

A team can add a careful note to the hero film and still lose it in a vertical cutdown, creator repost, product page, carousel crop, press image or screen recording. This is why disclosure should be planned like a brand element: where it appears, what it says, when it needs an expanded explanation and how it survives export. A buried production note does not travel by goodwill.

First decide the audience question the note answers. Usually it is not ‘which model did we use?’ It is closer to ‘am I seeing a real person or event?’ or ‘what kind of interaction am I entering?’ Write the short answer in plain language, then design the longer context for anyone who wants it.

Know what Content Credentials can and cannot carry

C2PA Content Credentials are a technical standard for signed provenance information about media and its history. They can make an asset’s recorded origin and edits inspectable when the credential is retained and supported. The C2PA explainer is equally clear about the boundary: provenance information alone cannot determine whether content is true, accurate or factual. It also notes that edits through tools that are not credential-aware may leave a gap in the recorded history.

Use credentials where your approved toolchain supports them, preserve the original signed export and test the actual distribution path. Do not call the badge a truth certificate, a rights clearance or a promise that every repost will retain the data. It is one evidence layer, not the whole audience explanation.

Source context: C2PA — C2PA and Content Credentials Explainer · C2PA — Content Credentials Technical Specification 2.3

Platform labels are an extra surface, not your plan

Platforms can add their own treatment. Meta says ads created or significantly edited with its generative creative features receive a label in the ad context, and it has described expanding transparency work to third-party tools. Google’s July 2026 policy update permits advertisers to add text or visual labels to certain AI-generated or modified image and video ads and introduced an AI-label setting gradually across advertising products. Those are platform-specific product behaviors, subject to account, asset and distribution conditions.

The sensible release assumption is narrower: verify the current destination’s policy and preview, then keep your own audience-facing disclosure in the creative or its immediate context where clarity needs it. A platform label can reinforce the message; its absence should not silently become your disclosure strategy.

Source context: Meta — Expanding GenAI Transparency for Meta’s Ads Products · Google Ads Policy Help — Updates to AI labeling requirements

Build a disclosure pack, not one sentence

Our recommended pack has three levels. Level one is a short, readable disclosure placed close to the relevant media or interaction. Level two is an accessible landing-page note explaining the material synthetic or altered elements and the human creative role. Level three is the internal asset record: source files, versions, toolchain notes, credentials where available, approvals and approved language. It gives the team something accurate to draw from when a new placement arrives.

Before launch, render the pack in every planned form factor. Check mobile truncation, caption overlap, thumbnail crops, embedded players and paid-placement previews. Then archive screenshots and URLs. The goal is not to make a sweeping statement about legal compliance. It is to make the intended audience explanation survive ordinary campaign handling.