EU AI Act update: the Council adopted the Digital Omnibus on AI on 29 June 2026. Official Journal publication is still pending; review the official Council update before relying on older high-risk deadline references. Council update EU AI Act update: Council adopted the Digital Omnibus; OJ publication pending. Council update
Starter wording

Article 50 Transparency Notice Templates

Use these Article 50 transparency notice templates as starter wording before the notice gets buried in a policy page. They cover AI interaction notices, AI-generated content labels, synthetic media disclosures, and sensitive-use warnings that need proper review before publication.

Free · No login · Local download

10 June 2026 Article 50 Code update

The Code is voluntary. Article 50 is not. The European Commission published the Code of Practice on Transparency of AI-Generated Content on 10 June 2026. The Code's operational sections address Article 50(2) provider marking and Article 50(4) deployer labelling. Article 50(5) supplies the cross-cutting requirements for clear, distinguishable and accessible information at the latest at first interaction or exposure. The Code remains voluntary implementation support; Article 50 obligations remain legal obligations where they apply.

Deployers should now record whether Code measures, EU icons, provider marking dependencies, label wording, first-interaction or first-exposure timing, accessibility, and public-interest text review were considered. Do not treat the Code, an icon, or a checklist as legal approval.

Article 50 timing watch

Under the current AI Act, Article 50 transparency obligations remain route-specific and are generally scheduled around 2 August 2026 for in-scope duties, with a specific adopted-pending-OJ Article 50(2) provider transition to 2 December 2026 for certain synthetic-content systems already placed on the market before 2 August 2026. PE-CONS 30/26 describes a specific adopted-pending-OJ transition until 2 December 2026 for providers of AI systems generating synthetic audio, image, video or text content placed on the market before 2 August 2026 to comply with Article 50(2). It is not a blanket transition for every Article 50 deployer disclosure route. The Council adopted the Digital Omnibus on AI on 29 June 2026, but Official Journal publication and the exact entry-into-force date remain pending. Treat the adopted text as an adopted-pending-OJ planning baseline, not as a blanket delay for all Article 50 duties.

EU AI Act Article 50 Transparency Notice Template XLSX

Professional Excel worksheet with Start Here, Dashboard, transparency notice template, lookups, sources, and review notes.

Download XLSX worksheet →

Article 50 notice templates Markdown

Copyable notice wording for internal review and adaptation.

Download Markdown →

Starter notice library

These notices are deliberately conservative. They are not final legal wording. Review them against the exact AI system, interface, jurisdiction, language, sector, and user group before anything goes live.

AI interaction notice

You are interacting with an AI system. It may generate responses based on your input and available context. Do not enter confidential information or sensitive personal data unless this use has been approved.

AI-assisted decision support notice

This process uses AI-supported analysis to assist human review. A human reviewer remains responsible for the final decision where internal policy or applicable law requires it.

AI-generated content notice

This content was generated or materially modified using AI. Review it before relying on it for a legal, financial, employment, health, or safety-related decision.

Deepfake or synthetic media notice

This image, audio, or video contains AI-generated or AI-manipulated content. It may not represent a real event, statement, or person acting in real time.

Emotion recognition notice

This process may involve AI-based interpretation of emotional state or behavioural signals. Use is restricted to the approved purpose and requires legal and privacy review before deployment.

Biometric categorisation notice

This process may involve AI-based categorisation using biometric data or biometric-derived signals. Use is restricted to the approved purpose and requires legal and privacy review before deployment.

Implementation checks before publishing a notice

FAQ

Are these legally sufficient notices?

No. They are starting points for internal review. Public notices should be reviewed by qualified counsel.

Should the notice be buried in a privacy policy?

No. For user-facing transparency, the notice should generally be visible at the relevant interaction point, not only inside a policy page.

Continue the Article 50 journey

1. Disclosure decision tree
Use this first if the route or exception question remains unclear.2. Transparency evidence validator
Check the provider, deployer, and evidence-dependency record.3. Article 50 evidence file
Retain the approved notice, placement, publication proof, and vendor evidence.4. Article 50 implementation pack
Use the full hub when several routes or teams are involved.

Source and review note

This page is an educational evidence starter. It is not legal advice and does not confirm compliance. Review the official text of Regulation (EU) 2024/1689 and obtain qualified legal review before relying on any template for a formal compliance decision.

Article 50 evidence fields to add after the Code update

Article 50 Code update FAQ

Is the Article 50 Code of Practice mandatory?

No. The Code is voluntary implementation support. Article 50 transparency obligations remain legal obligations where they apply. Use the Code to structure marking, labelling, evidence, and review workflows. Do not treat Code participation as a substitute for the AI Act, Commission guidelines, or legal review.

What changed on 10 June 2026?

The Commission published the Code of Practice on Transparency of AI-Generated Content. The practical change for deployers is not a new standalone law. It is a clearer implementation reference for labelling deepfakes and certain AI-generated or manipulated public-interest text, plus evidence fields such as label wording, placement, icon consideration, and accessibility.

What is the difference between provider marking and deployer labelling?

Provider marking concerns machine-readable marking and detection for AI-generated or manipulated outputs. Deployer labelling concerns public-facing disclosure for deepfakes and certain AI-generated or manipulated text published to inform the public on matters of public interest. A deployer evidence file should show which side of that split was reviewed.

Do EU icons prove Article 50 compliance?

No. EU icons can support clearer labelling, but the deployer still needs a disclosure process. Record where the label appears, when the person sees it, whether it is accessible, what text accompanies it, and who approved the notice. Icon use alone should not be described as compliance proof.

Related Article 50 route

After adapting the notice, use the Transparency Evidence Validator and Article 50 Evidence File to retain the decision basis, approved wording, placement, accessibility, publication proof, and vendor evidence.

Source and review note

Last reviewed: 23 June 2026. Source basis: Regulation (EU) 2024/1689 Article 50, the European Commission Code of Practice on Transparency of AI-Generated Content published on 10 June 2026, European Commission signing instructions for the Code, and the European Commission EU icons page for labelling AI-generated content. The Code is voluntary implementation support. Article 50 transparency obligations remain legal obligations where they apply. EU icons are optional labelling aids and do not establish legal compliance by themselves. This page provides operational planning guidance, not legal advice, certification advice, audit assurance, or a compliance guarantee.