Compliance
GDPR and Chatbots: What to Check Before Serving European Visitors
In this article
- Does GDPR Apply to My Chatbot?
- Which Lawful Basis for a Chatbot?
- Which Visitor Rights Does a Chatbot Have to Handle?
- Technical Measures: What ChatDirect Provides
- International Data Transfers
- Consent Implementation for Chatbots
- DPIA: Data Protection Impact Assessment
- Penalties, and Where to Check the Rules
- FAQ — GDPR and AI chatbots
If your website serves visitors in the European Union, the GDPR can apply to your chatbot even when your company is based in Canada or the United States. This guide stays general: it explains the questions to ask before deploying an AI agent for European visitors, shows which ChatDirect settings help, and sends you to the official sources for the exact rules. It is not legal advice.
Does GDPR Apply to My Chatbot?
The GDPR’s territorial scope is broader than many businesses expect. In broad terms, it applies when:
- Your organization is established in the EU (regardless of where data processing occurs)
- You offer goods or services to EU residents (even without a physical presence in Europe)
- You monitor the behaviour of EU residents (which includes chatbot conversation tracking)
A chatbot that collects personal data (names, emails, IP addresses, conversation content) from people in the EU you are targeting is therefore likely to fall under the GDPR. A site that is merely reachable from Europe, without targeting its residents, is a different case: when in doubt, ask a privacy professional.
Which Lawful Basis for a Chatbot?
Under the GDPR, every processing activity must rest on one of six lawful bases. For a chatbot, three come up most often:
- Consent: The visitor explicitly agrees to data collection. ChatDirect has a consent step that can be shown before the chat starts.
- Legitimate interest: Processing is necessary for your legitimate business interests, provided it doesn’t override the individual’s rights. This can apply to basic chatbot functionality but is harder to justify for lead capture.
- Contract performance: Processing is necessary to perform a contract. Relevant if the chatbot is part of a paid service.
Many small businesses that use a chatbot for lead generation choose consent, because it is the easiest to explain to a visitor. Which basis fits your case is your decision, ideally with a privacy professional.
Which Visitor Rights Does a Chatbot Have to Handle?
The GDPR gives the people whose data you hold (your visitors) a set of rights, and your organization must be able to answer their requests within the time the regulation sets. The table lists the main ones and what ChatDirect provides to help; answering the request remains your responsibility. For the exact wording and deadlines, read the regulation itself.
| Right | What the visitor can ask | What ChatDirect provides |
|---|---|---|
| Access | A copy of the personal data you hold about them | Export of a visitor’s data from the client portal; optional “My data” button in the chat widget |
| Rectification | Correction of inaccurate data | Contact records can be edited in the CRM |
| Erasure | Deletion of their data | Optional “Delete my data” button in the widget; deletion of a contact and its conversations from the portal |
| Portability | Their data in a commonly used, machine-readable format | CSV export of the CRM and visitor data export |
| Objection | That you stop a processing based on legitimate interest | No dedicated setting: handle the request by hand (stop contacting, delete if required) |
Technical Measures: What ChatDirect Provides
The GDPR also expects appropriate technical and organizational measures. Here is what ChatDirect provides on its side:
- Encryption: HTTPS for data in transit; API keys and credentials for your tools are encrypted with AES-256, and login passwords are hashed.
- Access controls: Two-factor authentication on the client portal; ChatDirect’s team has no access to your data unless you grant temporary support access (72 hours at most).
- Pseudonymization: IP anonymization option reduces identifying data.
- Data minimization: Configurable lead capture fields — collect only what you need.
- Retention limits: A configurable retention period, after which old conversations are deleted.
- Cookie control: A zero-cookie mode is available.
- Security: Rate limiting and security headers help prevent unauthorized access.
International Data Transfers
GDPR restricts the transfer of personal data outside the European Economic Area (EEA). The European Commission keeps a list of countries it recognizes as providing an adequate level of protection; Canada is on it for commercial organizations (adequacy decisions page, read on November 13, 2026). Under an adequacy decision, data can flow to the country without additional safeguards.
ChatDirect stores conversations and contacts in Canada. One point to document in every case: to generate replies, the content of the messages is sent to the AI provider you choose (Anthropic, OpenAI, Google or Mistral), which may process it outside Canada: in the United States for Anthropic, OpenAI and Google, in Europe for Mistral. Your privacy notice, and your impact assessment if you carry one out, should cover this transfer and the provider’s safeguards. See our 2026 AI chatbot comparison for a detailed look at how different platforms handle compliance.
Consent Implementation for Chatbots
In the GDPR’s own terms, consent must be:
- Freely given: Not bundled with other consents or required for basic service access.
- Specific: Clearly state what data you’re collecting and why.
- Informed: The visitor must understand the implications.
- Unambiguous: Requires a clear affirmative action (not pre-ticked boxes).
For conversational AI chatbots, this translates to a clear privacy notice in the chatbot greeting, an explicit opt-in before collecting personal data, and easy access to your privacy policy. ChatDirect lets you show a consent step before the chat and edit the greeting message. Read more in our guide to Law 25, GDPR and chatbots.
DPIA: Data Protection Impact Assessment
The GDPR requires a Data Protection Impact Assessment (DPIA) when a processing is likely to result in a high risk to people’s rights and freedoms. Whether a chatbot reaches that threshold depends on what it does: a simple FAQ bot is not in the same position as one that scores leads or handles sensitive data. Data protection authorities publish lists and criteria; check those of the countries you serve.
A DPIA for your chatbot should document:
- The nature, scope, context, and purposes of processing
- An assessment of necessity and proportionality
- An assessment of risks to data subjects
- Measures to address those risks (the settings listed above can be part of them)
Penalties, and Where to Check the Rules
The GDPR provides for administrative fines that can be very high, calculated on a company’s worldwide turnover for the most serious breaches, and European data protection authorities do enforce it. We deliberately quote no article number or amount here: read them at the source, and ask a privacy professional for anything that affects your situation. This article is general information, not legal advice.
- The text of the regulation: Regulation (EU) 2016/679 on EUR-Lex.
- Guidelines from the authorities: the European Data Protection Board and, for France, the CNIL.
- Transfers outside the EU: the European Commission’s adequacy decisions page (read on November 13, 2026).
Canadian businesses must also deal with Quebec’s Law 25 at the same time. On the ChatDirect side, the security page lists where data is stored and which providers process it. ChatDirect holds no SOC 2 report or ISO 27001 certificate.
FAQ — GDPR and AI chatbots
Does the GDPR apply to a chatbot run by a Canadian company?
It can. Being based in Canada or the United States does not exempt you if you offer goods or services to people in the EU or monitor their behaviour. Check your own case in the regulation or with a privacy professional.
What lawful basis should a chatbot use under the GDPR?
Many small businesses rely on consent for lead capture, shown before the chat starts. Legitimate interest can cover basic chatbot functionality but is harder to justify for lead capture. The choice is yours to document.
Do I need a DPIA for my chatbot?
It depends on the risk. A simple FAQ chatbot may not require one; a chatbot that scores leads, tracks behaviour or handles sensitive data may. Check the criteria published by the data protection authority of the countries you serve.
Can chatbot data be transferred from the EU to Canada?
The European Commission lists Canada (commercial organizations) among the countries offering an adequate level of protection. ChatDirect hosts conversations and contacts in Canada; however, message content is sent to the AI provider chosen to generate replies (United States or Europe, depending on the provider), which your privacy notice should cover.
Does ChatDirect make my chatbot GDPR compliant?
No tool can. ChatDirect, an AI chatbot and CRM for small businesses, provides settings designed to help you meet GDPR requirements: consent, IP anonymization, zero-cookie mode, retention period, data export and deletion. Compliance depends on how you configure and use them, and on your own notices and records.