Article 50 is not one generic notice requirement. It separates provider duties for AI systems that interact with people or generate synthetic content from deployer duties for emotion recognition, biometric categorisation, deepfakes, and certain public-interest text.
Use this page to decide which disclosure belongs in the product interface, content workflow, model-output pipeline, workplace or public-facing notice, and which high-risk AI instructions for use must still be handled separately.
Structured answer sets in this page tree.
Cited legal and guidance references.
The EU AI Act's transparency rules for labeling and user disclosures are concentrated in Article 50, with related high-risk AI transparency requirements in Article 13 and deployer operating duties in Article 26. A useful implementation record should identify the exact AI system, the actor with the duty, the exposed audience, the timing of the notice, the channel where the notice appears, and the evidence that the notice or marking was actually delivered.
Article 50 creates several distinct transparency duties. Providers must design direct-interaction AI systems so natural persons are informed that they are interacting with an AI system, unless that is obvious in context. Providers of AI systems, including general-purpose AI systems, that generate synthetic audio, image, video, or text content must ensure outputs are machine-readable and detectable as artificially generated or manipulated, subject to the Article 50 exceptions.
Deployers carry separate duties where their use exposes people to emotion recognition or biometric categorisation systems, creates or manipulates image, audio, or video content constituting a deepfake, or publishes AI-generated or manipulated text to inform the public on matters of public interest. Article 50 also requires the information in paragraphs 1 to 4 to be clear, distinguishable, accessible, and given no later than the first interaction or exposure.
For a chatbot, voice assistant, agent, embedded support flow, or similar interface, the first question is whether the AI system is intended to interact directly with natural persons. If yes, the provider should treat the disclosure as a product design requirement, not a policy document hidden away from the user journey.
The notice can be unnecessary only when the AI nature is obvious from the viewpoint and context described in Article 50. That exception should be used narrowly in product review: record the interface, the user group, the context of use, and why the AI interaction would be obvious before relying on it.
Article 50 separates provider-side technical marking from deployer-side public disclosure. Providers of systems that generate synthetic audio, image, video, or text content must ensure outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, as far as technically feasible and taking account of content type, implementation cost, and the state of the art.
Deployers have a different obligation when they generate or manipulate image, audio, or video content constituting a deepfake: disclose that the content has been artificially generated or manipulated. For evidently artistic, creative, satirical, fictional, or analogous works, the obligation is limited to disclosure of the existence of generated or manipulated content in an appropriate way that does not hamper the display or enjoyment of the work. For AI-generated or manipulated text published to inform the public on matters of public interest, deployers must disclose the AI generation or manipulation unless Article 50's law-enforcement or human-review/editorial-responsibility exceptions apply.
Deployers of emotion recognition systems or biometric categorisation systems must inform the natural persons exposed to the operation of the system. That disclosure duty is separate from data-protection duties: Article 50 expressly states that personal data must be processed under the applicable EU data-protection instruments.
The notice record should therefore answer two questions at once. First, did the exposed person receive clear information about the operation of the system by the time of exposure? Second, did the privacy team assess the lawful basis, data categories, safeguards, and documentation required by the applicable data-protection regime?
Article 50 transparency duties do not replace Chapter III high-risk AI requirements. Article 50(6) says paragraphs 1 to 4 do not affect Chapter III obligations, while Article 13 requires high-risk AI systems to be sufficiently transparent for deployers and accompanied by concise, complete, correct, clear, relevant, accessible, and comprehensible instructions for use.
That means the same AI product can need two different transparency artifacts: a user-facing Article 50 notice or label, and a deployer-facing Article 13 instruction set. Article 26 then requires deployers of high-risk AI systems to use the system in accordance with the instructions for use, assign competent human oversight, monitor operation based on those instructions, and keep logs where the logs are under their control.
Use this checklist for product release, content publication, procurement onboarding, or deployment approval when Article 50 may apply. The goal is to prove that the correct actor delivered the correct notice, label, or technical marking to the correct audience at the correct moment.
Do not use this checklist as a substitute for high-risk classification, prohibited-practice screening, privacy review, or sector-specific disclosure rules. Article 50 transparency can sit beside those duties, and Article 50(6) preserves other transparency obligations under Union or national law.
No. Article 50 covers user-facing transparency for direct interaction with an AI system. If the system is high-risk, Article 13 instructions for use and Article 26 deployer operating duties still need their own evidence and controls.
The deployer of the AI system that generates or manipulates image, audio, or video content constituting a deepfake must disclose that the content was artificially generated or manipulated, subject to the Article 50 exceptions and special treatment for evidently artistic, creative, satirical, fictional, or analogous works.
Providers should keep the marking design, machine-readable format decision, detectability testing, content-type limitations, robustness and interoperability assumptions, release approvals, and records showing why any Article 50 exception was or was not used.
Deployers should inform the natural persons exposed to the operation of the emotion recognition or biometric categorisation system by the time of exposure, and keep the Article 50 notice aligned with applicable EU personal-data compliance records.
Sorena can help separate provider marking duties, deployer disclosure duties, high-risk instructions for use, and privacy evidence into a practical Article 50 review record.
Ask source-linked questions about Article 50 notices, AI-generated content labels, deepfake disclosures, and high-risk AI instruction handoffs.
Review your Article 50 trigger analysis, notice wording, labeling evidence, and high-risk AI transparency handoffs with Sorena.