What happens when your AI generator is compliant but your website is not
What California's AI Transparency Act and Article 50 actually mean for a marketing team
California's AI transparency act and the EU AI act's article 50 transparency rules both became operative yesterday. Both of these have similar roots - if your system generates synthetic image/video/audio, the output has to carry a machine-readable mark that survives distribution + can be detected later (and in Europe the same applies to text as well).
From an enterprise POV, this is especially relevant for a marketing team where the marking duty sits upstream with whoever supplies your generation tools.
The first (and the most common) place it would show up is the content pipeline. If your designer generates a hero in Firefly, it would come out of the tool with a C2pa manifest sitting in the metadata. But then it'd get resized into 3 ad ratios in Canva, exported as a jpeg, uploaded to Bynder, resized again into responsive variants by the CMS, and converted to .webP by Cloudflare on the way to the browser, and by the time it renders on your microsite the manifest would be gone (because most transformation steps drop metadata they do not recognise). So the generator did meet its obligation but the file your customer sees carries nothing --> putting the work in auditing every handoff between creation and publication
The second is the deployer side in Europe, where disclosure falls on the team running the experience even though the model came from somewhere else. E.g. if you have an OpenAI-backed email assistant drafting and sending replies from your Growth inbox to EU customers, that inbox needs to tell people they are dealing with an AI (and yeah, it can't be a light grey font label buried in a P.S.). Same again for a campaign built on a synthetic voice-over or an AI-generated spokesperson (which counts as a deepfake for these purposes and needs a label). OpenAI carries the marking duty for the model, but enterprises carry the disclosure duty for the experience they built with it
The third is 2027, when California would require large online platforms to detect provenance data and display it to users through an interface. So you may generate a set of Linkedin/Meta ad creatives in Firefly, the provenance data would survive your pipeline this time, and the platform would read it and put an "AI info" style panel next to your ad. The platform would write the copy in that panel and you may have no say in what it says (what you definitely don't want is for your CMO to see it for the first time as a screenshot forwarded by someone in sales or as a tag on linkedin)
For anyone running content at scale w/ AI, the next few months could be pretty unglamorous work: an inventory of which tools generate what, test of whether metadata survives your publishing path (jpeg export settings/DAM renditions /CDN transforms are where it usually breaks today), disclosure language for every AI-facing surface in EU markets etc.