AI ACT GUIDE
Updated 27 August 2026 · 6 min read
Drift and Article 50: AI notice on sales chat
Drift playbooks qualify leads on their own. The visitor must know when the conversation opens.
Drift automates sales chat. A playbook that answers and qualifies is not obviously human. Article 50(1) requires a clear notice at the first interaction.
Drift’s terms or a vendor privacy page do not replace a sentence on your site, next to the widget, in the page language.
Drift provides the tool. The site remains the deployer: register (Drift, leads use), display log, legal pages.
Clairia detects js.driftt.com on the homepage. Help with compliance, not a Drift certification or legal advice.
The path, in order
- 1
Scan the homepage
Paste the URL. In under a minute you see whether a known chatbot is present, and whether a notice is visible. With no chatbot there is no /100 score.
- 2
Show the notice next to the chat
One script line (w.js) sits on Crisp, Intercom, Tidio and known widgets. On Crisp, the sentence is also shown once in the conversation.
- 3
Re-scan the homepage
Clairia should appear in the findings. This is not a certification: it confirms the script is on the page.
- 4
Let the log run
Each page load with the script is dated. It is not proof that the chat was opened.
Frequent questions
- Who must show the notice: the site or the chat vendor?
- The visitor is talking to your site. The vendor (Crisp, Intercom, Tidio…) provides the tool. The site must inform, at the first interaction.
- Is a notice in the terms or legal notice enough?
- No. Too late and too easy to miss during the chat. Article 50 requires clear information at the latest at the first interaction.
- How do you prove the notice was shown?
- A useful file: a register (tool, vendor, use), a dated log of script loads, homepage scans. A /100 score is not proof.
General information, not legal advice.
Official reference: European Commission Article 50 guidelines ↗