Disclose AI interaction and label synthetic content
Download: JSON · MarkdownUnder EU AI Act, Article 50
What this label means
- Verified
- — a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
- Pending review
- — linked to the official source and in the queue for a reviewer to confirm.
- Source-linked
- — linked to the official source, not yet confirmed by a reviewer.
On this page 9 sections
In brief
Disclose AI interaction and label synthetic content is a legal requirement under the EU AI Act in the European Union (Article 50). It applies from 2 August 2026. The record carries 1 evidence example and mappings to 2 frameworks. In practice: Implement provenance marking (for example content credentials) and user-facing AI disclosures in product UX.
- Instrument
- EU AI Act
- Jurisdiction
- European Union
- Nature
- Legal requirement
- Source reference
- Article 50
- Applies from
- 2 August 2026
- Who it binds
- Provider / developer, Deployer / user organisation
- Evidence examples
- 1
- Framework mappings
- ISO/IEC 42001:2023, NIST AI Risk Management Framework 1.0
- Controls that meet it
- 2
- Official source
- Open official text
- Verification
- Pending review · source-linked
What does it require?
Providers must ensure AI systems intended to interact with people inform them they are dealing with AI unless obvious; providers of systems generating synthetic audio, image, video or text must mark output in a machine-readable, detectable format; deployers of emotion-recognition or biometric-categorisation systems must inform exposed persons; deployers must disclose deepfakes and AI-generated text published to inform the public on matters of public interest, subject to exceptions.
Practical action
Implement provenance marking (for example content credentials) and user-facing AI disclosures in product UX.
Who does it apply to?
Providers and deployers of chatbots, generative systems, emotion recognition and biometric categorisation, whatever the risk tier.
Applies from:
Which controls meet this duty?
Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.
-
satisfiesProcessProduct owner · at launch and on material changeAI interaction and use disclosure notices
Serves 18 recorded duties · evidence: AI interaction or use notice, Notice catalogue, Notice wording approval
User-facing AI interaction notices.
-
satisfiesTechnical measureEngineering lead · continuousSynthetic content labelling and provenance marking
Serves 5 recorded duties · evidence: Content labelling and provenance standard, Watermark and provenance robustness test, Visible AI-generated content label
Machine-readable marking of synthetic output and deepfake labels.
Templates that cover this duty
Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.
- EU AI Act Role and Risk Classifier
Checklist · XLSX · v4
- AI Agent Registry and Permission Matrix
Register · XLSX and DOCX · v6
- EU AI Act Article 50 Transparency Kit
Kit · DOCX and XLSX · v32
- ISO/IEC 42001 Gap Assessment and Statement of Applicability
Assessment · XLSX · v3
What evidence would a reviewer expect?
| Evidence | Type | Notes |
|---|---|---|
| Disclosure and watermarking design record | document |
Framework mappings
Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.
See every European Union duty mapped this way →
| Framework | Reference | Note | Confidence |
|---|---|---|---|
| ISO/IEC 42001:2023 | Annex A control on communication with interested parties | Original editorial mapping. | medium |
| NIST AI RMF 1.0 | GOVERN 4.x; NIST AI 600-1 content provenance suggestions | Generative AI profile guidance on provenance. | medium |
Frequently asked questions
Is this a legal requirement?
Yes. It is a legal requirement under EU AI Act (Article 50).
Who must comply with this obligation?
Providers and deployers of chatbots, generative systems, emotion recognition and biometric categorisation, whatever the risk tier.
When does this obligation apply?
It applies from 2 August 2026.
What evidence shows compliance?
A reviewer would expect: Disclosure and watermarking design record.
Which frameworks map to this obligation?
It is mapped to ISO/IEC 42001:2023 Annex A control on communication with interested parties, NIST AI Risk Management Framework 1.0 GOVERN 4.x; NIST AI 600-1 content provenance suggestions. These are editorial crosswalks with a stated confidence, not official mappings.
Which controls satisfy this obligation?
AI interaction and use disclosure notices; Synthetic content labelling and provenance marking.
What should an organisation do in practice?
Implement provenance marking (for example content credentials) and user-facing AI disclosures in product UX.
Cite this record
AIPolicyTracker (2026). “Disclose AI interaction and label synthetic content (EU AI Act)” [AIPT-OBL-0017, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0017 (accessed 27 October 2026). Data licensed CC BY 4.0.
Permanent id AIPT-OBL-0017: it never changes or gets reused, and its address keeps working if this page moves.
Cite the official text alongside it: Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, https://eur-lex.europa.eu/eli/reg/2024/1689/oj.
BibTeX
@misc{aipolicytracker2026_discloseaiinteractionand,
author = {{AIPolicyTracker}},
title = {{Disclose AI interaction and label synthetic content (EU AI Act)}},
year = {2026},
howpublished = {\url{https://aipolicytracker.org/obligations/eu-ai-act-transparency-article-50}},
url = {https://aipolicytracker.org/obligations/eu-ai-act-transparency-article-50},
urldate = {2026-10-27},
note = {Data licensed CC BY 4.0. Accessed 27 October 2026}
}
Change history
No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.
Similar obligations in other instruments
- Providers of generative AI must mark synthetic output as artificially generated in a machine-readable way — EU AI Act, European Union
- Employers must inform workers and their representatives before using high-risk AI at work — EU AI Act, European Union
- Deployers of emotion recognition or biometric categorisation must inform exposed persons — EU AI Act, European Union
- Deployers must disclose deepfakes and AI-generated text published on matters of public interest — EU AI Act, European Union
- Deployers must tell natural persons that a high-risk AI system is used in decisions about them — EU AI Act, European Union
- Deployers must explain individual decisions taken with high-risk AI on request — EU AI Act, European Union
- Frontier developers must publish a transparency report before deploying a new frontier model — California SB 53, California (United States)
- Provide deployers with clear instructions for use — EU AI Act, European Union
Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.