AI ACT GUIDE
Updated 28 August 2026 · 6 min read
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.
Since 2 August 2026, Article 50 of Regulation (EU) 2024/1689 is in force. There is no size threshold: a freelancer with a support widget is in scope. For a website, the useful duty is to tell people they are talking to an automated system, at the latest at the first interaction.
Searches like “AI Act compliance” or “AI chatbot notice” often come from this fear: a chatbot with a human name, fluent replies, and nothing visible when it opens. A sentence in the terms does not fix that. Too late, too hard to see.
There is no “compliance stamp”. Nobody can sell an Article 50 certificate for a widget. What actually helps is a visible gesture (the notice next to the chat) and a simple file if someone asks: which tool, which notice, which dated script loads.
The Clairia path is short, like a cookie banner. 1) Scan the homepage. 2) See whether a known chatbot is there, and whether a notice already exists. 3) Paste one script line. 4) Scan again. 5) The log counts script loads, not each time the chat is opened.
The scanner reads homepage HTML and linked legal pages. An agent loaded only after JavaScript, after login, or on another URL can be missed. With no chatbot detected, there is no /100 score: a 100 without chat would be a lie.
Crisp, Intercom, Tidio, HubSpot, Zendesk, Brevo, Tawk, Gorgias: the site informs the visitor, not the tool vendor. Even if the vendor later ships a native banner, the register and the log stay on your side.
General information, not legal advice. If the use is high-risk (recruitment, credit, health), a lawyer still matters. For support chat on a brochure site or a store, the useful minimum is: a notice when the chat opens, an inventory of the tool, a load history of the script.
The path, in order
- 1
Scan the homepage, for free
Enter the domain. You get findings (widget, notice, legal pages), not a certification. Under a minute, no account.
- 2
Attach the notice to the chat
Essential enables w.js. The banner sits next to the widget. On Crisp, the sentence is also shown once in the conversation.
- 3
Re-scan the homepage
The “Clairia in place” finding should appear. If the script is only on an inner page, the homepage scan can miss it.
- 4
Check the log
Open a page on the site. The log should show at least one load. That is a history of script loads, not proof that someone opened the chat.
Frequent questions
- Do I need to be “certified compliant” under Article 50?
- No. Article 50 requires information, not a label. A /100 score is not compliance. What matters: a visible notice at the first interaction, and being able to show what was in place.
- Where do I start if I have a chatbot today?
- Scan the homepage. If a widget is detected without a notice, show a line such as “You are chatting with an automated assistant” when it opens. Then keep a register and, if you can, a log.
- Are the terms enough?
- No. The information must be clear and given at the latest at the first interaction. A legal paragraph in the footer is not that first interaction.
- What if I have no chatbot?
- The scan will say so, without inventing a score. Other duties (marking generated content, deepfakes) may still exist. The Clairia widget is for when a chat is present.
General information, not legal advice.