Article 50: AI notice required since 2 August 2026 · Compliance checklist
clairia

AI ACT GUIDE

Updated 5 October 2026 · 6 min read

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.

When someone searches “AI Act checklist” or “chatbot compliance”, they want boxes to tick, not a legal memo. This list is for a site with a support widget, not for a high-risk system.

Box 1 — Know what runs. A homepage scan detects known scripts (Crisp, Intercom, Tidio, HubSpot, Zendesk, Brevo, Tawk, Gorgias, ChatGPT embeds…). It will not see a custom agent loaded after login. Also write down the tools you know, one line per system in a register.

Box 2 — Notice visible when it opens. Short sentence, next to the chat. Not in the terms. On Crisp, a one-time reminder in the conversation as well as the banner.

Box 3 — Re-scan. The Clairia script must be detected on the homepage. Otherwise the notice is not where visitors arrive first.

Box 4 — Log. A dated script load. That is not “the visitor read it”. It is “the script was served that day”. Better than a PDF left in a Drive.

What this checklist does not cover: machine-readable marking of generated images (transition until 2 December 2026 for some systems already online), deepfakes, high-risk systems in 2027. Do not mix everything. For site chat, these four boxes are the first kilometre.

A weekly crawl or a PDF is not proof on every chat open

Article 50(1) has applied since 2 August 2026. A one-off PDF or a weekly external homepage crawl captures one moment: it does not show what a visitor saw each time they opened the chat, on another URL, or with a second widget. Potential risk in an inspection if your file is only that snapshot.

Clairia logs each real chat open, works across Crisp, Intercom or custom widgets on the same site, shows a clear notice at the first interaction, and offers a free homepage scan — help documenting, not guaranteed compliance. Start with the free scan before relying on a PDF or weekly rescan alone.

The path, in order

  1. 1

    Scan

    Analyse https://your-site.com. Read the findings, not only the number.

  2. 2

    Notice

    Enable the widget, paste w.js before </body>, open the chat on mobile.

  3. 3

    Re-scan

    Clairia should appear in the homepage findings.

  4. 4

    Log

    One page visit is enough to record the first day.

Frequent questions

How long to get a chat “in order”?
The visible gesture (notice when it opens) can be done the same day. The log fills as soon as the script is in production. It is still not a certification.
What if the scan does not find my chatbot?
It may load after JavaScript, on another page, or after login. Check with your eyes. The scanner only sees homepage HTML and ~30 signatures.
Does the €49 PDF replace the widget?
No. The PDF documents a state. The widget shows the notice and feeds the log. For a live chatbot, the widget is what the visitor sees.

General information, not legal advice.

Official reference: European Commission Article 50 guidelines ↗

More guides