What an AI vendor's DPA must put in writing
What a DPA for AI vendors must contain under GDPR Article 28, how ten European providers differ, and which claims a contract cannot back.
In this article6

What a DPA must contain for an AI vendor
Article 28(3) of the GDPR requires that processing by a processor be governed by a contract or other legal act that sets out the subject-matter and duration of the processing, the nature and purpose of the processing, the type of personal data and categories of data subjects, and the obligations and rights of the controller.[1] The contract must be in writing, including electronic form.[1] The requirement scales with cloud use: 45.2% of businesses in the EU used cloud services in 2023, up 4.2 percentage points from 2021, according to Eurostat data published by the European Commission.[2]
- Process the personal data only on documented instructions from the controller, including regarding transfers to third countries.
- Ensure that persons authorised to process the data are committed to confidentiality.
- Take all measures required under Article 32 (security of processing).
- Engage another processor only with prior specific or general written authorisation, and inform the controller of intended changes so the controller can object.
- Assist the controller in responding to data subjects' rights requests under Chapter III.
- Assist the controller in meeting the obligations in Articles 32 to 36, including impact assessments.
- At the controller's choice, delete or return all personal data at the end of the service, and delete existing copies.
- Make available all information necessary to demonstrate compliance, and allow for and contribute to audits, including inspections.[1]
Two points matter specifically for AI vendors. First, sub-processor authorisation and transfer safeguards are contractual, not optional: the European Data Protection Board's guidance for SMEs[3] lists standard contractual clauses and binding corporate rules as the safeguards for transfers of personal data outside the EU.[4] Second, the AI Act, published in the Official Journal on 12 July 2024 as Regulation (EU) 2024/1689, adds obligations for AI systems but does not replace the Article 28 contract.[5] A vendor's DPA remains the instrument that governs its processing of personal data on a customer's behalf.
Four of those clauses carry the weight in an AI vendor's DPA: sub-processor authorisation, transfer safeguards, deletion and audit. They are the four the sections below return to, first in how providers' published terms differ and then in the clauses to insist on.
Sub-processors, transfers, deletion and audit
Sub-processor authorisation means a named list plus a change notice with an objection right, as Article 28(2) requires.[1] A transfer safeguard must name its instrument, standard contractual clauses or binding corporate rules, as the European Data Protection Board's SME guidance sets out.[4] Deletion must cover existing copies at the end of the service, and audit must extend to inspections, both listed among the processor's obligations in Article 28(3).[1] What none of the four can do is substitute for a certification scheme: a clause cannot put a provider in the EU Cloud CoC public register, and a C5 attestation is evidenced by the provider's own dated audit report, not by a contract clause.[6]
How named providers' DPAs actually differ
As retrieved on 23 September 2026, none of the ten providers appears in the EU Cloud CoC public register. The adherents listed there include Microsoft Corporation (Level 2, adherence ID 2021LVL02SCOPE116), Google LLC (Level 2, 2020LVL02SCOPE015) and Oracle Cloud Infrastructure (Level 2, 2022LVL02SCOPE4214), each with a dated latest assessment.[9] The Code received official approval from the Belgian Data Protection Authority on 20 May 2021, with SCOPE Europe as its owner and monitoring body.[7][8]
| Provider | EU Cloud CoC adherence (level) | BSI C5 attestation | Transfer mechanism in published terms | Published sub-processor list |
|---|---|---|---|---|
| Bleu | Not listed | – | – | – |
| Delos Cloud | Not listed | – | – | – |
| Hetzner | Not listed | – | – | – |
| IONOS | Not listed | – | – | – |
| Nebius | Not listed | – | – | – |
| Open Telekom Cloud | Not listed | – | – | – |
| OVHcloud | Not listed | – | – | – |
| Scaleway | Not listed | – | – | – |
| STACKIT | Not listed | – | – | – |
| T-Systems | Not listed | – | – | – |
A dash means the page lists no value for that cell. For C5 this is structural: the BSI publishes no per-provider register on its C5 page, so an attestation claim has to be evidenced by the provider's own dated audit report.[6]
What a DPA cannot promise
The recurring error on this topic is a marketing claim of sovereignty with no scheme behind it. A contract binds the provider, not a foreign authority: no clause displaces another jurisdiction's lawful access demand, which is why residency alone does not settle data sovereignty for AI inference. A certification claim has to resolve to a scheme that exists: EUCS remains a draft candidate scheme,[10] and BSI C5 attests information security, not data-protection compliance.
The clauses to insist on
- A dated sub-processor change notice with an objection right, as Article 28(2) requires.[1]
- A named transfer mechanism, standard contractual clauses or binding corporate rules, stated in the DPA itself.[4]
- Deletion or return of all personal data, including existing copies, on termination.[1]
- Audit and inspection rights, or access to dated third-party audit reports.[1]
- Key control: with BYOK inference the customer holds the keys, and what BYOK covers should be stated in the contract, not the brochure.
The decision test before signature is traceability. Each claim in a vendor's DPA should resolve to an instrument with a date: the GDPR article it implements, the register entry with its adherence ID and level, or the certification scheme and its publication status. A clause the vendor cannot trace to a dated instrument is a claim, not a safeguard.
Sources
Rankings and scores on Optinest cannot be bought — no commercial relationship changes how a provider is assessed. How we score
Related reading
All Sovereignty →GPU billing per second vs per hour: what short jobs pay for
GPU billing per second, per minute or per hour: what each unit adds to a short job, worked out, and which European providers publish their billing unit.

GLM-5.3 API in Europe: which providers list it, and at what price
Which European providers list the GLM-5.3 API, their input, cached and output rates per 1M tokens, context window and stated region, read 26 October 2026.

Long-context models you can call from a European provider
Which European providers list 1M-token and 256K-token models, where their context figures disagree, and what a long prompt costs. Read 26 October 2026.
