← Free risk checker
Home → Chatbot Compliance → Drift EU AI Act
LIMITED RISK — Article 50 transparency required
Deadline: 2 August 2026. Article 50 has NOT been deferred by the Digital Omnibus. You need a disclosure on your Drift chatbot before this date. Fine for non-compliance: up to €15M or 3% of turnover.

Drift EU AI Act Compliance: What to Add to Your Playbooks by 2 August 2026

Using Drift AI Conversations or Drift chatbot playbooks on your site? Article 50 of the EU AI Act requires a clear disclosure that visitors are talking to an AI — not a sales rep. Here is exactly what to add.

Good news: Drift is limited risk — not high-risk. You do not need conformity assessment or Annex IV documentation. You need one thing: a disclosure at the start of each bot interaction that the visitor is talking to an AI. It takes under an hour to add to any Drift playbook.

What you need to do — step by step

  1. Open each Drift playbook and add a "Send a message" step as the very first action — before any qualifying question
  2. Paste your disclosure text into this opening step (use the examples below)
  3. If your Drift bot uses a human name and avatar, either update the name to reflect AI (e.g. "Drift AI", "Sales Bot") or ensure the disclosure is explicit enough to overcome the human persona
  4. Update your website privacy policy to mention that an AI chatbot is used for visitor interactions
  5. If Drift generates any written content users will re-publish (e.g. AI-drafted outreach), mark it as AI-generated under Article 50(2)
  6. Brief your sales team on the AI literacy requirement — they should understand what Drift AI can and cannot do (Article 4)

Ready-to-use disclosure text for Drift

Copy one of these into your Drift bot's opening message:

Hi! I'm an AI assistant — I'll ask you a few quick questions to connect you with the right person. Type human at any time to skip ahead.
Welcome! You're chatting with an automated AI. A team member will follow up personally. What brings you here today?
Hey there! This is an AI-powered chat. I'll do my best to help — or connect you with our team directly if you'd prefer.

Need this in French, German, Spanish, Dutch, Polish, Italian?

The Chatbot Compliance Pack includes 7 language variants, a T&C clause template, a privacy policy AI section, and the Article 50(2) machine-readable marking guide.

Get Chatbot Compliance Pack — €49 →
Or use the free disclosure generator →

Drift and the EU AI Act: full analysis

Why Drift falls under Article 50

Article 50(1) of the EU AI Act covers AI systems "intended to interact directly with natural persons." Drift's AI Conversations product — which uses large language models to qualify leads, answer questions, and route visitors — clearly qualifies. The limited risk classification applies because standard B2B lead qualification does not make high-stakes decisions about individuals' rights or safety. Drift becomes high-risk only if configured to assist with employment decisions or credit assessments, which is atypical.

The obligation falls on you as the deployer — the company using Drift on your website. Drift as the provider has its own documentation and transparency obligations, but the Article 50 disclosure to your website visitors is your responsibility to implement.

Where exactly to add the disclosure in Drift

In Drift's playbook builder, every playbook has a conversation flow starting with an opening message. The compliance approach is straightforward: add a "Bot sends message" step at position one, before any routing question or data capture. This ensures 100% of visitors who interact with your bot see the disclosure before providing any information.

If you use multiple playbooks (different ones for homepage, pricing page, returning visitors), each one needs the disclosure step. A global opening message in Drift's settings, if available in your tier, is the most efficient approach.

The human persona problem

Many Drift deployments use a named bot persona — often with a first name, photo, and job title that appear human. Article 50 explicitly prohibits operators from designing AI systems intended to pass as human when a user sincerely asks. If your Drift bot is named "Alex" with a photo, a disclosure like "You're chatting with Alex, our AI assistant" satisfies both the human persona and the Article 50 requirement simultaneously.

The 2 August 2026 deadline is firm for Article 50

The Digital Omnibus proposal (provisionally agreed May 2026) defers high-risk AI obligations to December 2027 for many systems. Article 50 transparency obligations are not part of that deferral. They apply to all chatbot operators serving EU users from 2 August 2026 — regardless of company size, location, or whether you consider Drift a "simple" chatbot.

Frequently asked questions

Does Drift need to comply with the EU AI Act?
Yes. Drift's AI Conversations and chatbot playbooks fall under Article 50 transparency obligations from 2 August 2026. Any business using Drift to interact with visitors located in EU member states must add a clear AI disclosure at the start of each bot interaction.
Is Drift classified as high-risk under the EU AI Act?
Standard Drift deployments for B2B lead qualification are classified as limited risk (Article 50 transparency only). Drift becomes high-risk only if configured for employment decisions, credit assessments, or similar Annex III use cases — which is not typical for sales/marketing chatbots.
We are a US company. Does the EU AI Act apply to our Drift chatbot?
Yes. The EU AI Act has extraterritorial scope. If your Drift chatbot is accessible to visitors located in EU member states — even if your company is based in the US — Article 50 applies. The determining factor is where your visitors are, not where you are incorporated.
Does every Drift playbook need its own disclosure?
Yes, every playbook that a user can enter needs a disclosure at the first interaction step. If you have 10 playbooks, each one needs the opening disclosure message. Some Drift tiers allow a global welcome message — using that setting is the most efficient way to cover all playbooks at once.