CLAIRIA RESOURCES
AI Act compliance: guides to act.
Article 50, chatbot notice, Crisp, WordPress. Scan, display, prove — without legal jargon.
FREE TEMPLATES
Notice, register and proof log templates
Copy a practical starting point, then scan your homepage.
Duties
AI Act Article 50 compliance: scan, notice, proof
Since 2 August 2026, a chatbot must be identifiable. The practical path: scan the homepage, show the notice, keep a log — no “compliant” stamp.
Read the guide ↗How to display an AI notice on a chatbot (Article 50)
The sentence to show, where to put it, and how to do it with Crisp, Intercom or Tidio — when the chat opens, not in the terms.
Read the guide ↗Article 50 checklist: AI chatbot in 15 minutes
Four boxes: homepage scan, notice next to the chat, Clairia re-scan, first load in the log. To act, not for an audit.
Read the guide ↗AI chatbot notice: a copy-ready template
The notice to show when the chat opens, with a practical mobile check.
Read the guide ↗AI system register: a free template
A simple inventory for chatbot, content generation, vendor, use and notice.
Read the guide ↗AI Act Article 50 proof journal example (2026)
Article 50(1) chatbot disclosure applies since 2 Aug 2026. Terms are not proof—log scans and widget checks over time. Start with a free homepage scan.
Read the guide ↗Shop chatbots: AI Act Article 50 disclosure (2026)
Store chatbot disclosure under Article 50(1) due since 2 Aug 2026. Apps, generated content—checklist + free scan. Checkout terms alone are not enough.
Read the guide ↗AI Act Article 50: chatbot disclosure due since 2026
Article 50(1) chatbot notice was due from 2 Aug 2026 (Dec 2026 is other rules). What to disclose, why terms fail, potential enforcement risk—free scan.
Read the guide ↗AI chatbot: the disclosure duty since 2 August 2026
A support widget is not “obvious”. Here is the notice to show, when to show it, and how to prove it.
Read the guide ↗AI Act fines: what you actually risk
Up to €15m or 3% of worldwide turnover. The real issue is inspection, formal notice, and proof.
Read the guide ↗Marking AI-generated content (C2PA, metadata)
Article 50(2) requires machine-readable marking. Transition until 2 December 2026 for systems already online.
Read the guide ↗2 December 2026: end of the AI marking transition
Last window before mandatory machine-readable marking of existing systems, then high-risk systems in 2027.
Read the guide ↗Proving AI transparency: what an inspector may ask for
A visible notice is not enough. The useful file is a register, a display log, and dated scans — not a legal opinion.
Read the guide ↗AI system register: what to record for your site
Chatbot, copy, images: a simple inventory (system, vendor, use) avoids a blank stare when someone asks what you run.
Read the guide ↗
Chat tools
Crisp and AI Act Article 50: who must show the notice?
Crisp provides the widget. The site must tell visitors they are talking to AI, at the first interaction.
Read the guide ↗Intercom (Fin) and Article 50: the AI notice to show
Fin and Intercom bots sound human. The site must say so when the chat opens, not only in the terms.
Read the guide ↗Tidio and Lyro: AI notice duty (Article 50)
Lyro answers on its own. On a French or EU site, the visitor must know from the first message.
Read the guide ↗Zendesk AI and Article 50: what the site must display
Answer Bot and Zendesk AI agents do not exempt the site from informing visitors. Notice at the first exchange.
Read the guide ↗HubSpot Chat and Breeze: is an AI notice required?
HubSpot chat, especially with a bot, is not “obviously human”. The site must show it when the widget opens.
Read the guide ↗Brevo Conversations and Article 50: who shows the AI notice?
Formerly Sendinblue: Brevo chat and bots are yours vis-à-vis the visitor. Notice when the widget opens, not only in the terms.
Read the guide ↗Tawk.to and Article 50: is an AI notice required?
A very common free chat. As soon as a bot or canned reply speaks, the visitor must know at once.
Read the guide ↗ChatGPT / OpenAI widget on a site: notice required
A ChatGPT embed is never “obviously human”. The notice must appear as soon as the visitor opens the assistant.
Read the guide ↗Gorgias and Article 50: AI notice on a store
The Gorgias agent answers ecommerce customers. The store must show it when the chat opens.
Read the guide ↗Drift and Article 50: AI notice on sales chat
Drift playbooks qualify leads on their own. The visitor must know when the conversation opens.
Read the guide ↗
CMS and stores
WordPress chatbot AI notice (Article 50): setup guide
WordPress chatbot AI notice under Article 50(1), in force since 2 August 2026. Step-by-step setup: paste near the widget. Free homepage scan.
Read the guide ↗Shopify store: AI notice for chat and content
Gorgias, Tidio, Shopify Inbox or a custom bot: the merchant must inform the customer at the first automated exchange.
Read the guide ↗PrestaShop: AI notice for chat and support
Tidio, Crisp or a custom module: the store informs the customer when the widget opens.
Read the guide ↗