GDPR-Compliant AI Assistants: Claude, ChatGPT Enterprise, Gemini, and Mistral Compared (2026)

TL;DR: Claude Teams and ChatGPT Enterprise both score well on the six checks that DPOs care about most, but Mistral le Chat Enterprise is the strongest choice for teams that need data to stay within the EU by default. Microsoft Copilot for M365 covers the EU Data Boundary commitment but depends on your existing Microsoft licensing tier.

Every AI assistant vendor now describes itself as "GDPR compliant". The phrase appears in marketing copy, pricing pages, and security portals. But when your Data Protection Officer actually looks at the paperwork, the gaps appear quickly. Does the vendor have a signed Article 28 processor agreement? Does EU data residency apply to your specific plan, or only to enterprise contracts? Do Standard Contractual Clauses cover the data transfer, or is the vendor relying on an adequacy decision that may not hold?

This article cuts through the marketing language. It scores six widely used AI assistants against the six GDPR requirements that DPOs actually check before approving a tool. The goal is not to declare a single winner, but to give your team the right questions and the right table to take into a vendor review.

The 6 GDPR checks that matter for AI assistants

Before looking at the table, here is what each check means in practice.

EU/EEA data residency option. Your data is processed and stored on servers located within the European Economic Area. This removes the need for a transfer mechanism entirely. Some vendors offer this only on enterprise tiers; others make it default.

Data Processing Agreement (GDPR Article 28) available. Article 28 requires that any organisation using a processor to handle personal data must have a written contract covering specific obligations: purpose limitation, confidentiality, security measures, sub-processor disclosure, assistance with data subject rights, and deletion on termination. If a vendor cannot provide a DPA, you cannot lawfully use it to process personal data under GDPR.

Does not train on your data by default. Using customer prompts and outputs to improve a model is a secondary processing purpose that requires a lawful basis. For business data this is almost never possible without explicit consent, which employees rarely give. The safe default is a vendor contractual commitment that your data is not used for training.

SOC 2 Type II certified. SOC 2 Type II is not a GDPR requirement, but it is the most common proxy your DPO will use to assess whether a vendor's security controls actually work over time. Type II means an independent auditor tested controls over a 6-to-12 month period, not just reviewed documentation.

EU Standard Contractual Clauses (SCCs) included in DPA. If data leaves the EEA (for example, to a US-headquartered vendor's US servers), a transfer mechanism is required. SCCs are the standard choice. They should be included automatically in the vendor's DPA, not require a separate negotiation.

Self-hosting / on-premises option. Some organisations, particularly those in regulated sectors, need the model to run on their own infrastructure. This eliminates third-party processor risk entirely.

Comparison table

A few clarifications on the "Partial" ratings. For Claude Teams, EU data residency is available on the Claude Enterprise tier via Anthropic's AWS EU region infrastructure, but is not the default for standard Teams subscribers. For ChatGPT Enterprise, EU data residency is delivered through Azure OpenAI Service EU regions rather than OpenAI's own US infrastructure, and requires explicit configuration. For Cohere, region availability depends on your deployment choice; the default API endpoint processes data in the US.

Tool-by-tool notes

Claude Teams and Claude Enterprise (Anthropic). Claude Teams includes a DPA with SCCs and a no-training commitment. The step up to Claude Enterprise adds zero data retention (sessions are not stored after completion) and EU data residency on AWS EU regions. If your team handles personal data regularly, the Enterprise tier is the defensible choice. The standard Claude.ai Free and Pro plans have neither a DPA nor training opt-out and should not be used for personal data. See the Anthropic vs OpenAI GDPR compliance compared article for a deeper look at Anthropic's processor terms.

ChatGPT Enterprise (OpenAI). OpenAI's enterprise offering has a strong GDPR posture: no training on your data, a downloadable Data Processing Addendum, SCCs, and SOC 2 Type II certification. EU data residency is available through Azure OpenAI Service EU regions, but you need to confirm this is active in your deployment. Do not conflate ChatGPT Enterprise with ChatGPT Team, which is the lighter plan for small teams; the Team plan includes a DPA but may not have the same EU residency options.

Gemini for Google Workspace. Google's offering benefits from the company's existing EU data region infrastructure. Business and Enterprise Workspace subscribers can select an EU data region, meaning data is stored and processed in EU data centres. The DPA is incorporated into the Google Workspace agreement, which most organisations already have in place. SOC 2 Type II is covered under Google's broader cloud certifications. The main watch-out is that Gemini in Workspace and Gemini via Google AI Studio (consumer product) are entirely different offerings, each with different privacy terms.

Mistral le Chat Enterprise. Mistral is a French company, which means its default infrastructure is EU-based. This is the only major AI assistant on this list where EU data residency is the default rather than an add-on. Mistral holds ISO 27001 certification; its SOC 2 Type II status should be confirmed with the vendor as this is in progress at time of writing. Self-hosting is available via the Mistral API deployed to your own infrastructure, which removes third-party processor risk entirely. For EU-headquartered organisations with strict data sovereignty requirements, Mistral is the most straightforward choice.

Microsoft Copilot for M365. Microsoft's EU Data Boundary commitment covers Copilot for M365, meaning EU customer data is stored and processed within the EU and EFTA. The DPA is part of the Microsoft Products and Services Agreement (MPSA) or Enterprise Agreement, which most organisations already hold. SCCs are standard. The main caveat is that Copilot capability depends on your M365 licensing tier; not all plans include the full Copilot feature set.

Cohere Command (enterprise). Cohere is a Canadian company with deployments on Azure and AWS, including EU regions. Self-hosting is available via private deployment, which is a genuine differentiator for organisations in regulated sectors. SOC 2 Type II is in place. Check the current DPA for EU data residency terms, as region availability can change with infrastructure updates.

What your DPO will ask before approving any AI assistant

Before your DPO signs off on any AI assistant for use with personal data, expect these six questions. Having the answers ready will cut approval time significantly.

1. Is there a signed DPA in place? Not "available on request" but actually signed and filed. For most vendors this is a click-through acceptance in the admin portal; for others it requires a countersigned document.

2. Where is data processed and stored? If outside the EEA, what is the transfer mechanism? SCCs must be in the DPA, not a separate document.

3. Does the vendor train on our data? Get this in writing in the DPA. "We don't train on customer data" in a blog post is not a contractual commitment.

4. Who are the sub-processors? GDPR Article 28(4) requires that sub-processors are subject to the same data protection obligations. Vendors must publish a sub-processor list and notify you of changes.

5. What is the data retention period? Default retention periods for prompts and outputs vary by vendor and plan. Shorter or zero-retention configurations are available on higher tiers.

6. How does the vendor assist with data subject rights? If an individual asks to delete their data, how does your organisation action that request given that data may be cached in the vendor's system?

For a ready-to-use template to document the answers, see the GDPR Article 30 AI tools record of processing template. For a broader vendor assessment framework, the AI vendor evaluation checklist covers security, contractual, and operational dimensions beyond GDPR.

What DPOs actually check (and where each tool fails)

The comparison table above covers documented policy. What follows is what happens when a DPO actually opens the vendor agreements and runs them against real procurement scenarios. These are the four situations that most commonly stall or kill AI tool approvals in practice.

Scenario 1: Vendor switches subprocessors without adequate notice

GDPR Article 28(4) requires vendors to inform controllers before adding or replacing subprocessors and to give them an opportunity to object. In practice, most vendors bury this in a "we will post a notice to our website" clause, which is legally questionable and practically useless.

Mistral le Chat Enterprise currently provides 30-day advance notice for subprocessor changes and lists subprocessors explicitly in its DPA. DPOs reviewing Mistral can set a calendar reminder to check the list each month.

Microsoft Copilot for M365 routes through Microsoft's standard subprocessor list, which covers Azure cognitive services and third-party subcontractors. Changes are notified through the Service Trust Portal with a 30-day window. The process is mature; most DPOs accept it without pushback.

ChatGPT Enterprise routes some features through Azure OpenAI, which introduces Microsoft as a subprocessor alongside OpenAI. The DPA covers this, but the nested subprocessor relationship (OpenAI subprocesses to Microsoft for compute, Microsoft subprocesses to regional Azure providers) means the actual list is longer than it looks at first read. DPOs running a full Article 28(4) check will need the Microsoft Azure subprocessor list, not just OpenAI's.

Claude Enterprise has a published subprocessor list available on Anthropic's privacy page. Changes are communicated via the list update with typically 30-day notice. The list is shorter than Microsoft's by a wide margin, which makes auditing it faster.

Gemini for Google Workspace runs within Google's infrastructure. The subprocessor notice is part of Google Workspace's standard terms, and Google's subprocessor list is comprehensive but long. The practical risk here is not inadequate notice; it is DPO fatigue from reviewing a multi-page list across a very large platform.

Scenario 2: Training opt-out exists — but only at enterprise tier, and only if you ask

Every vendor on this list claims it does not train on your data. What the marketing pages do not always say clearly: the opt-out is sometimes a default (applied automatically), sometimes a toggle (you must switch it off), and sometimes a tier gate (available only if you pay for enterprise).

For ChatGPT Enterprise, the no-training commitment is contractual and covers the enterprise plan by default. You do not need to configure anything. ChatGPT Team (the lower tier) also includes no-training by default, but the DPA terms at Team tier may not have the same negotiation flexibility as Enterprise.

For Otter.ai and other third-party tools not on this list but commonly used alongside the assistants here, training opt-outs typically require a signed DPA at the Business or Enterprise tier. Free and Pro plan users are subject to standard privacy policy terms, which are materially weaker. This is a common problem in mixed-tier teams: the account owner bought Business, but five team members added personal Otter Pro accounts, and those personal accounts are processing the same meetings without the DPA in place.

For Gemini for Google Workspace, training opt-out is included in the Workspace agreement, but the scope depends on whether you have Google's Workspace AI features enabled or are using Gemini via a standalone Google One subscription. The assistant and the Workspace integration are different products with different terms. A DPO reviewing "Gemini" without specifying which product is reviewing the wrong thing.

Scenario 3: EU data residency claimed but US support teams can access data

This scenario comes up frequently with US-headquartered vendors that offer EU data residency as a technical control while preserving support access from US-based staff. Data residency means the data sits in an EU data centre. It does not, by itself, mean only EU-based personnel access it.

Microsoft Copilot for M365 is the clearest positive case here. Microsoft's EU Data Boundary commitment explicitly covers support access: EU data is not accessed by support staff outside the EU except in specific escalation scenarios with customer consent. This is documented in the EU Data Boundary documentation and is a genuine differentiator.

ChatGPT Enterprise does not make equivalent commitments in its standard DPA regarding support access geography. Data processing occurs in Azure EU regions when configured, but the DPA does not restrict which OpenAI employees can access data for support purposes. For organisations in regulated sectors, this is worth negotiating before signing.

Claude Enterprise processes data in AWS EU regions when EU residency is enabled. Anthropic's DPA limits processing to necessary purposes, but access geography for support personnel is not specified at the same level of detail as Microsoft's EU Data Boundary documentation. This is a gap worth noting in a DPIA.

Mistral le Chat Enterprise, being an EU company with EU infrastructure and EU-based staff, has the cleanest answer here by design. There is no US parent entity with a legal basis to compel data access. For DPOs who need to sign off on cross-border access risk, Mistral removes the question entirely.

Scenario 4: DPA terms allow training opt-out, but the lawful basis for processing is not named

GDPR Article 13 requires that the legal basis for processing be communicated to data subjects. When your organisation uses an AI vendor as a processor, the vendor's DPA should specify the legal basis on which they process data on your behalf. Many vendor DPAs are silent on this, or name the legal basis as "contractual necessity" without explaining the specifics.

A DPO reviewing Anthropic's, OpenAI's, or Google's DPA for the first time will often find Article 28 compliance (instructions from controller, technical measures, return/deletion on termination) without a clear statement of which Article 6 legal basis covers the processing. The expectation is that the controller (your organisation) determines the legal basis, and the processor follows instructions. But the DPA should still confirm that the processor has not identified any basis for using data beyond what the controller instructs.

This sounds procedural, but it matters when you are documenting your Article 30 record. If the DPA does not help you identify the legal basis, you need to determine it yourself based on your use case, and you need the vendor's DPA to not contradict your chosen basis.

Minimum viable GDPR check: 3 questions before your DPO signs off

If any of the three answers is "no" or "it depends on your tier," resolve that before the DPO signs. Every tool on this list can get to "yes" on all three, but most require either a higher tier, a configuration step, or a direct negotiation with the vendor's legal team.

Related Reading

• Privacy-first AI APIs, GDPR and CCPA guide 2026: for teams using AI via API rather than SaaS assistants
• Anthropic vs OpenAI GDPR compliance compared: deeper analysis of the two leading US vendors
• GDPR Article 30 AI tools record of processing template: paste-ready template for your Article 30 register
• AI vendor DPA tracker 2026: live tracker of DPA versions and last-updated dates across major AI vendors