Use cases / Compliance officers

Article 50 disclosures live before 2 August 2026

Templates for all four EU AI Act transparency tracks: interaction notice, generated-content marking, deep-fake disclosure, public-interest content. Plus machine-readable provenance metadata in JSON-LD that aligns with the European Commission's Code of Practice draft. Publish in the same workflow as your security and privacy statements — one tool, one page, one URL.

The problem

EU AI Act Article 50 transparency obligations become enforceable on 2 August 2026. Providers and deployers of certain AI systems must give end users a visible disclosure when interacting with AI, mark AI-generated content in a machine-readable way, and disclose deep-fake or public-interest content. The Code of Practice draft ( December 2025; final June 2026) outlines what compliant implementations look like.

Most teams handling this spread the work across legal, product, and compliance — disclosure copy goes in one tool, model documentation in another, the machine-readable mark gets forgotten entirely. By the time a buyer (or a regulator) asks where the disclosure lives, nobody can answer with a single URL.

How Provenance helps

Four Article 50 templates. Pre-filled per transparency track: (1) AI interaction notice for chat / assistant features, (2) generated-content marking for text/image/video output, (3) deep-fake disclosure for synthetic media, (4) public-interest content disclosure for news / political /civic. Edit the copy; we ship the structural skeleton aligned to the Code of Practice draft.
Machine-readable provenance. Each disclosure publishes alongside a JSON-LD payload, a stable URL, and a content hash — the machine-readable mark Article 50 contemplates. Procurement systems and provenance tools (C2PA-compatible signing, watermarking pipelines) can pull the metadata directly.
One workflow with security + privacy statements. AI disclosures live in the same trust-page system as your SOC 2, ISO, GDPR, and DPA statements. Legal, product, and security all edit one source of truth — not three.
Versioned, change-tracked. Every edit creates a versioned decision row. Auditors and buyers see exactly what changed, when, and by whom — useful for the documentation Article 50 expects.
Public verifiability. Disclosures are indexed in our public directory. Buyers, journalists, regulators all verify against the same canonical URL — not a screenshot their counterpart sent in an email.

Live example

Walkthrough of the four templates, the machine-readable mark, and the Code of Practice references. Updated as the spec evolves.

Read the Article 50 implementation guide

Start free Read the AI Act guide

Informational only — not legal advice. Article 50 obligations vary by AI system type and deployment role; consult counsel for your specific obligations.

Article 50 disclosures live before 2 August 2026

The problem

How Provenance helps

Four Article 50 templates. Pre-filled per transparency track: (1) AI interaction notice for chat / assistant features, (2) generated-content marking for text/image/video output, (3) deep-fake disclosure for synthetic media, (4) public-interest content disclosure for news / political /civic. Edit the copy; we ship the structural skeleton aligned to the Code of Practice draft.

Machine-readable provenance. Each disclosure publishes alongside a JSON-LD payload, a stable URL, and a content hash — the machine-readable mark Article 50 contemplates. Procurement systems and provenance tools (C2PA-compatible signing, watermarking pipelines) can pull the metadata directly.

One workflow with security + privacy statements. AI disclosures live in the same trust-page system as your SOC 2, ISO, GDPR, and DPA statements. Legal, product, and security all edit one source of truth — not three.

Versioned, change-tracked. Every edit creates a versioned decision row. Auditors and buyers see exactly what changed, when, and by whom — useful for the documentation Article 50 expects.

Public verifiability. Disclosures are indexed in our public directory. Buyers, journalists, regulators all verify against the same canonical URL — not a screenshot their counterpart sent in an email.

Live example

Walkthrough of the four templates, the machine-readable mark, and the Code of Practice references. Updated as the spec evolves.

Read the Article 50 implementation guide

Informational only — not legal advice. Article 50 obligations vary by AI system type and deployment role; consult counsel for your specific obligations.