AI Disclosure Notice Template

When to use

Use when natural persons interact with an AI system (chatbot, agent, voice UI) or when you need clear product UI disclosure. Article 50 transparency obligations apply from 2 August 2026 where relevant (Commission guidelines 20 July 2026). This template is a draft for product teams, not legal advice.

Relevant Act provisions (map with counsel): Article 50(1) interaction; Article 50(2) machine-readable marking; Article 50(3) emotion / biometric notice; Article 50(4) deepfake / certain public-interest text. This page focuses on human-facing interaction notices. It does not by itself satisfy Art. 50(2) or 50(4). See the Commission-guidelines summary and chatbot disclosure guide.

Last reviewed: 16 August 2026 · Written by ActBrief Editorial · External legal review pending — methodology.

How to fill

1. Replace bracketed fields with your product facts.
2. Place the notice at the point of interaction, not only in a footer or privacy policy.
3. If you promise human escalation, ship the path.
4. Save screenshot + product/version + owner as evidence.
5. Record which Article 50 paragraph and role (provider / deployer) you mapped.

Short UI notice (chat / support)

You are interacting with an AI assistant. Responses may be inaccurate. A human can review escalations on request.

Agent / outbound assistant

This message was generated by an AI system operated by [Company]. It may be incomplete or wrong. Reply [HUMAN] or contact [email] for a person.

Product page / settings

AI features. [Product] uses artificial intelligence to [intended purpose]. AI outputs may be wrong or incomplete. For decisions that affect you, [describe human review / contact path].

Privacy policy blurb (supporting — not a substitute for UI notice)

We use AI systems to [purpose]. Categories of data processed include [list]. AI providers/subprocessors include [vendor list]. You may contact us at [email] about AI-related requests.

Example filled (illustrative)

You are interacting with SupportBot, an AI assistant from Acme SaaS. Answers may be wrong. Request a human via Talk to a person in the chat menu.

Placement checklist

• [ ] Notice visible before or at first interaction
• [ ] Persistent in chat chrome (not only a one-time toast)
• [ ] Readable by assistive tech; not colour-only
• [ ] Same story on web and mobile if both exist
• [ ] Footer / privacy alone is not the only disclosure

Evidence checklist (keep with counsel / buyer file)

• [ ] Screenshot of live disclosure (desktop + mobile if different)
• [ ] Product name / version / release date
• [ ] Owner and approval date
• [ ] Mapped Article 50 paragraph + provider/deployer role
• [ ] Link to Commission guidelines version used
• [ ] Intended purpose statement matches the notice

Before publish

• [ ] Intended purpose is accurate
• [ ] Escalation / human path exists if you promise it
• [ ] Vendor named if required by your counsel
• [ ] Matches actual product behaviour
• [ ] Article 50 paragraph, actor, exceptions, and any transition rule recorded

Next

Chatbot disclosure guide · Where to place disclosure · Evidence log · Article 50 hub · Article 50 checklist · Free readiness scan · Article 50 Evidence Pack