Skip to content

Law and data protection

Data processing agreements with AI providers: a checklist

This article was created with AI.

Last updated 10 min read

A guide by sicherAI. We offer an AI service for Heilpraktiker practices. How we write these guides

Deutsche Fassung

In short

You need a data processing agreement whenever an AI provider processes personal data on your behalf. Article 28(3) GDPR lists eight duties for the provider. They include acting only on your documented instructions and deleting or returning the data when the service ends. For AI tools, also check whether training on your inputs is contractually excluded, how long inputs are stored and where sub-processors are located.

Contents

When does an AI tool need a data processing agreement?

An AI tool needs a data processing agreement as soon as its provider processes personal data on your behalf. Under the General Data Protection Regulation (GDPR), your practice is then the controller, which “determines the purposes and means of the processing” (Article 4(7)). The provider is the processor, acting “on behalf of the controller” (Article 4(8)). A data processing agreement is the contract that governs this processing; in Germany, it is often called Auftragsverarbeitungsvertrag, or AVV for short.

Article 28 GDPR applies directly in Germany, as in every Member State of the European Union. It makes no exception for practices of Heilpraktiker, whatever their size. Heilpraktiker are non-medical practitioners licensed under the German Heilpraktikergesetz.

If no personal data reach the provider, Article 28 does not apply. The Hamburg Commissioner for Data Protection and Freedom of Information warns that removing names and addresses is not enough (checklist for LLM-based chatbots, point 7).

How do you check an AI provider’s agreement?

Before anyone enters personal data into a new AI tool, check the provider’s terms and agreement, and your own list of AI services, against these eleven points.

  • The terms do not reserve your inputs for the provider’s own purposes.
  • A data processing agreement exists for your plan, in writing (electronic form counts).
  • The agreement describes the processing and your obligations and rights as controller, and covers points (a) to (h) of Article 28(3) with concrete details.
  • Training on your inputs is contractually excluded.
  • Storage periods for prompts and files are stated.
  • Data are deleted or returned at your choice when the service ends.
  • The sub-processor list shows each company’s task and location.
  • You are informed directly about new sub-processors and can object.
  • Each transfer to a third country has a basis under Chapter V of the GDPR.
  • Breach notifications have a timeframe and a contact point.
  • Your list of AI services shows the agreement’s date and your last check.

What must the agreement contain under Article 28?

Under Article 28(3) GDPR, a data processing agreement must describe the processing, set out your obligations and rights as controller and bind the provider to at least eight duties. These cover instructions, confidentiality, security, sub-processors, help with requests from data subjects (the people concerned), further assistance, deletion or return, and proof of compliance. The description covers subject-matter and duration, nature and purpose, the type of personal data and categories of data subjects.

An agreement that only repeats Article 28 is not enough: it should give “more specific, concrete information” on how the requirements will be met (European Data Protection Board, or EDPB, Guidelines 07/2020, paragraph 112). Types of personal data should be specified “in the most detailed manner as possible” (paragraph 114).

DutyWhat to look for
(a) InstructionsOnly on your documented instructions, including on third-country transfers, unless Union or Member State law requires otherwise.
(b) ConfidentialityEveryone who processes your data is bound to confidentiality, by commitment or by law.
(c) SecurityThe Article 32 measures, described or referenced in enough detail for you to judge them (EDPB Guidelines 07/2020, paragraph 126).
(d) Sub-processorsYour prior written authorisation, and the same data protection obligations for each sub-processor.
(e) Data subject rightsHelp with requests, such as access or erasure.
(f) Further assistanceHelp with your duties under Articles 32 to 36, such as breach notification.
(g) End of serviceDeletion or return of all data at your choice, and deletion of existing copies unless Union or Member State law requires storage.
(h) ProofAll information needed to demonstrate compliance, and your right to audits, including inspections.

Which AI-specific points should you check?

For AI services, check four points in particular: own purposes such as training, retention, sub-processors and third-country transfers.

Own purposes and training

Check first whether the provider may use your inputs for its own purposes, such as training its models, and look for a clause that contractually excludes this. If the terms allow such use, the Hamburg data protection commissioner advises against entering any personal data (checklist for LLM-based chatbots, point 5).

Important: A setting that switches off training in a personal account is not a data processing agreement. In some cases, “a specific contract model must be booked” to object to training (Hamburg checklist, point 8).

Retention and deletion

Article 28(3)(g) covers deletion when the service ends, but not how long prompts and files are kept during use. The information the provider gives you should include “how the data retention requirements are met” (EDPB Guidelines 07/2020, paragraph 143). Check how many days chats and uploaded files are stored, and whether logs are kept separately.

Sub-processors and changes

A sub-processor is another company that your provider engages to process your data, such as a cloud host; the GDPR calls it “another processor”. Your provider needs your prior written authorisation to engage one (Article 28(2)). If that authorisation is general, the provider must inform you of intended changes so that you can object. Access to a list updated from time to time is not enough (EDPB Guidelines 07/2020, footnote 54). Before you authorise sub-processors, the provider has to give you a list showing, for each, “their locations, what they will be doing and proof of what safeguards have been implemented” (paragraph 152).

Transfers to third countries

A third country is a country outside the European Economic Area (EEA). If personal data are transferred to a provider or sub-processor in a third country, Chapter V of the GDPR applies (Article 44). Possible bases include a European Commission adequacy decision (Article 45) and standard data protection clauses adopted by the Commission (Article 46(2)(c)).

Fictional example: The sub-processor list of an AI writing tool names a cloud host but no country. Before anyone enters personal data, the practice manager asks the provider in writing for the host’s location and transfer basis. The reply names a country outside the EEA and standard data protection clauses; the manager files it with the agreement.

Do chat apps offer a data processing agreement?

In their published terms, OpenAI and Anthropic offer a data processing agreement that covers chat content only for their business offerings (as of 6 November 2026). For personal accounts, OpenAI’s privacy policy for Europe (updated 24 August 2026) and Anthropic’s privacy policy (effective 10 September 2026) name the provider itself as controller. Both policies exclude “content that we process on behalf of customers of our business offerings”. Both providers call the agreement a data processing addendum:

  • OpenAI offers it for ChatGPT Business, ChatGPT Enterprise and the API through an online form (enterprise privacy page, updated 8 January 2026; addendum effective 1 January 2026). A separate addendum for ChatGPT Sites (published 9 July 2026) applies to individual plans only where a published site collects personal data; it does not cover prompts or conversations.
  • Anthropic’s addendum (effective 24 February 2025) “is incorporated into and forms part of” its Commercial Terms of Service. For the Team and Enterprise plans of Claude, Anthropic names the customer as controller (privacy centre, updated 30 October 2026).

Terms change, so check your plan’s terms.

How do you keep track of your agreements?

A one-page list of your AI services and their contractual basis helps you “demonstrate compliance”, as Article 5(2) GDPR requires. The record of processing activities under Article 30 lists categories of recipients, such as AI providers, and transfers to third countries. As of 6 November 2026, the exemption in Article 30(5) for organisations with fewer than 250 persons does not apply if the processing includes special categories of data, such as data concerning health. A provisional agreement on an amendment (text of 26 June 2026) would widen this exemption to organisations with fewer than 1,000 persons, except, in particular, for processing likely to result in a high risk. On 6 November 2026, it still awaited the European Parliament’s vote (procedure 2025/0130(COD)), so check the wording in force.

Fictional example: A practice with two Heilpraktiker lists its AI services on one page. Each line shows the plan, the agreement’s date and filing place, the sub-processor countries and the last check. When a provider announces a new sub-processor, the practice manager checks its country and transfer basis before the objection period ends and updates the line.

What does a data processing agreement not replace?

A data processing agreement governs your relationship with the provider. It is not a legal basis for the processing itself. Processing data concerning health is prohibited unless an exception in Article 9(2) GDPR applies, and the agreement does not create one.

Your own duties as controller continue, including appropriate technical and organisational measures (Article 32) and data minimisation (Article 5(1)(c)): enter only what the task needs.

Frequently asked questions

Can a data processing agreement be concluded online?

Yes: Article 28(9) GDPR requires the agreement to be in writing, which includes electronic form, so an addendum accepted online can meet this requirement. A verbal assurance from the provider cannot: non-written agreements are not sufficient (EDPB Guidelines 07/2020, paragraph 101). Keep a copy of the version you accepted.

Who is liable to you if a sub-processor breaks its obligations?

Your provider. Under Article 28(4) GDPR, the provider must impose the same data protection obligations on the sub-processor by contract or other legal act. If the sub-processor fails to fulfil them, the provider remains fully liable to you for the sub-processor’s performance.

Is a privacy policy the same as a data processing agreement?

No: a privacy policy gives people the information that Articles 13 and 14 GDPR require about the processing of their data, while a data processing agreement is a contract between controller and processor with the content listed in Article 28(3). If the privacy policy that covers your account names the provider as controller, the provider is not offering to act as your processor for those data. In principle, the actual activities decide the role, not the label (EDPB Guidelines 07/2020, paragraph 12): a processor that determines purposes and means in breach of the GDPR counts as a controller for that processing (Article 28(10)).

Can you accept a provider’s standard terms as they are?

Only if they meet data protection law: Article 28(1) GDPR requires you to choose a processor that can show it will take appropriate technical and organisational measures. A contract prepared by the provider is not a problem in itself, but a small controller’s weaker bargaining position does not justify accepting terms that fall short of that law. If you accept the terms and use the service, you take full responsibility for compliance with the GDPR (EDPB Guidelines 07/2020, paragraph 110).

How often should a data processing agreement be checked?

The GDPR sets no fixed interval, but the EDPB treats the choice of a suitable processor as a continuous obligation and recommends checks at appropriate intervals, including audits and inspections where appropriate (Guidelines 07/2020, paragraph 99). Changes that a provider proposes to an addendum in its standard terms should be notified to you directly for your approval; publishing them on the provider’s website is not enough under Article 28 (Guidelines 07/2020, paragraph 110). Each such notice is a reason to check again.

Sources

  1. Publications Office of the European Union: Regulation (EU) 2016/679 (General Data Protection Regulation) (eur-lex.europa.eu), accessed
  2. Federal Ministry of Justice and Consumer Protection and Federal Office of Justice (gesetze-im-internet.de): Gesetz über die berufsmäßige Ausübung der Heilkunde ohne Bestallung (Heilpraktikergesetz), § 1 (www.gesetze-im-internet.de), accessed
  3. European Parliament, Legislative Observatory: Procedure file 2025/0130(COD): Omnibus IV (small mid-cap enterprises) (oeil.europarl.europa.eu), accessed
  4. European Data Protection Board: Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.1 (www.edpb.europa.eu), accessed
  5. European Commission: Data protection adequacy for non-EU countries (commission.europa.eu), accessed
  6. The Hamburg Commissioner for Data Protection and Freedom of Information: Checklist for the use of LLM-based chatbots (13 November 2023) (datenschutz-hamburg.de), accessed
  7. City of Munich: Heilpraktiker licence in the field of psychotherapy (stadt.muenchen.de), accessed
  8. OpenAI: Europe privacy policy, updated 24 August 2026 (openai.com), accessed
  9. OpenAI: Enterprise privacy at OpenAI, updated 8 January 2026 (openai.com), accessed
  10. OpenAI: OpenAI Data Processing Addendum, effective 1 January 2026 (openai.com), accessed
  11. OpenAI: ChatGPT Sites Data Processing Addendum, published 9 July 2026 (openai.com), accessed
  12. Anthropic: Privacy Policy, effective 10 September 2026 (www.anthropic.com), accessed
  13. Anthropic: Data Processing Addendum, effective 24 February 2025 (www.anthropic.com), accessed
  14. Anthropic: Does Anthropic act as a data processor or controller? (updated 30 October 2026) (privacy.claude.com), accessed
  15. European Parliament (Committees ECON, ENVI and LIBE): Provisional agreement resulting from interinstitutional negotiations, 2025/0130(COD), PE790.249, 26 June 2026 (www.europarl.europa.eu), accessed

ChatGPT is a trademark of OpenAI. Claude is a trademark of Anthropic.

About this guide

Publisher
sicherAI (see imprint)
Our interest
We offer an AI service for Heilpraktiker practices and use models from several makers, including some named in our guides. The guide contains no rankings. Statements about other providers rest on the sources listed.
How it was made
This article was created with AI.
Sources as of
Legal position as of
Limits
This guide provides general information. It is not legal advice for your individual case.
Report an error
Contact us using the details in our imprint.