Article 50 chatbot disclosure examples for the EU AI Act
A chatbot disclosure is not a legal footer. It should be visible when the user interacts with the system, written in plain language, and retained as evidence with screenshots and version history.
What a good chatbot notice needs to do
Article 50 transparency duties are scheduled to apply from 2 August 2026 under current law. For chatbot teams, the practical design question is simple: when a person starts interacting with the assistant, can they tell they are dealing with AI and understand the limits of the interaction?
- Say plainly that the assistant is AI.
- Place the notice where interaction starts, not only in legal terms.
- Include limits and a route to human help where relevant.
- Keep screenshots and copy versions as evidence.
Disclosure examples
Use these as starting language, not as final legal approval. The right wording depends on the system, sector, user journey, and whether a human escalation path exists.
| Surface | Good disclosure pattern | Evidence to keep |
|---|---|---|
| Chat header | You are chatting with an AI assistant. It can make mistakes; a human can help with complex issues. | Screenshot of the persistent header and release version. |
| First message | I am an AI assistant for account and product questions. Please verify important information. | Conversation transcript sample and timestamped copy version. |
| Fallback state | I may not have enough information. I can route you to a human support channel. | Escalation rule, UI copy, and support handoff log. |
| Settings/about page | How this AI assistant works, what it can do, and when humans review issues. | Public help page, limitations copy, and owner approval. |
Common weak patterns
The weakest pattern is hiding the disclosure in the footer or privacy policy. Another weak pattern is saying only “powered by AI” without making the interaction clear to the user. Good implementation is a product-design and evidence problem, not just a copywriting task.
- Tiny footer-only notice.
- Generic “AI-powered” badge with no limits or context.
- Notice shown only once and never retained in release evidence.
- Disclosure missing in mobile or embedded widget states.
FAQ
Does a chatbot always need an Article 50 notice?
Article 50 includes an exception where the AI nature is obvious from context, but teams should document why they rely on that exception.
Is this only a provider obligation?
Provider and deployer responsibilities can differ. The tool provider may design notices and technical controls, while the deploying company still needs to ensure the user-facing experience is clear.
Turn this reading into an actionable report
Use the free scanner to map your likely role, detect likely obligations, and see which evidence is missing.