Attach a signed AI-assisted or AI-generated credential and a Do Not Train preference using the open C2PA standard, so your disclosure travels with the file, not in a caption someone can delete.
The pressure is arriving from two directions at once, and both favor open, machine-readable labels over a line of text in a description box.
Article 50 requires AI-generated and AI-manipulated media to carry machine-readable disclosure, with labeling obligations arriving in 2026. The text favors open standards like C2PA, the exact credential Reconize already writes.
Netflix asks production partners to disclose generative-AI use and keep records of the tools and outputs involved. A signed, per-file declaration is exactly the record that guidance asks partners to maintain.
Mark a file as AI-generated, AI-assisted, or captured, with an optional note on the tools used. Choices map to the IPTC digital-source vocabulary, so they stay interoperable everywhere C2PA is read.
Carry a machine-readable Do Not Train preference in both the signed manifest and the watermark payload, so your opt-out travels inside the file rather than in a robots.txt someone never reads.
Drop the file into Verify, or any C2PA-compatible tool, and the disclosure shows plainly: what was declared, by whom, and when. Free to check, forever.
Disclosure is a signed statement, not a detector or an enforcement mechanism. We're precise about that:
You work with AI in the loop and want to say so honestly, in a form that satisfies the EU AI Act and travels with your work wherever it's reposted.
See Reconize for Creators →You need per-file GenAI records to hand a studio contact, on the same C2PA standard the industry is converging on, generated as part of your normal signing workflow.
See Reconize for Studios →