Before personal data goes to an LLM API, you need a signed data processing agreement (Article 28), the provider’s subprocessor list, written answers on retention and training, the processing location and a transfer basis for anywhere outside the EEA (Articles 44 to 49). Then send as little personal data as possible. You are usually the controller, the provider your processor.
This checklist turns the relevant GDPR articles into questions you can send to any provider. It is not legal advice. Your data protection officer or counsel decides what is enough for your case.
Is an LLM API provider a processor under GDPR?
In the common case, yes. You decide why the data is processed (to summarise a ticket, to answer a customer), and the provider processes it for you. Article 28 then requires a written contract with specific terms. If a provider also uses your prompts for its own purposes, such as training its models, it may be acting as a controller for that part. That is one reason the training question matters so much.
The EDPB’s Opinion 28/2024 deals with personal data in AI models themselves. The LLM risk report from the EDPB’s Support Pool of Experts (10 April 2025) works through privacy risks and mitigations for LLM systems, with three use cases: a customer-query chatbot, a student-progress monitor and a travel assistant. It was written by external experts and states that it does not necessarily reflect the EDPB’s official position, but it is a practical starting point.
What 15 questions should you ask an LLM provider under GDPR?
| # | Ask the provider | Why (GDPR) |
|---|---|---|
| 1 | Will you sign a DPA, and is it part of the terms or a separate document? | Art. 28(3) |
| 2 | Do you process personal data only on our documented instructions? | Art. 28(3)(a) |
| 3 | Who are your subprocessors, including GPU hosts and backup capacity? | Art. 28(2), 28(4) |
| 4 | How are we told about new subprocessors, and can we object? | Art. 28(2) |
| 5 | Are prompts, files, audio or outputs stored after the request? Where and for how long? | Art. 5(1)(e) |
| 6 | Is any of our content used to train, fine-tune or evaluate models? Is that off by default? | Art. 5(1)(b), Art. 28(10) |
| 7 | Which records do you keep without content (IP, token counts, cost), and for how long? | Art. 5(1)(c) |
| 8 | In which countries is data processed, including failover? | Art. 44 |
| 9 | What is the transfer basis: adequacy, DPF certification or SCCs? | Art. 45, 46 |
| 10 | Can we pin processing to a region? | Art. 44 |
| 11 | What security measures apply to requests and keys? | Art. 32 |
| 12 | How fast will you tell us about a personal data breach? | Art. 33(2) |
| 13 | How do you help with access and erasure requests? | Art. 28(3)(e) |
| 14 | Do staff ever see request content, for example on a support ticket? | Art. 28(3)(b), 32 |
| 15 | Will you give us the information we need for a DPIA and allow audits? | Art. 28(3)(f), 28(3)(h), Art. 35 |
Ask for answers in writing and keep them with your records of processing (Article 30).
Why are retention and training separate questions?
Providers often answer one and imply the other. Get both:
- Retention: is content stored after the request, in logs, abuse-monitoring stores, caches, batch files or conversation state?
- Training: is content used to improve models, and is the default on or off for your account type?
Policies differ a lot between providers and between free and paid tiers. We compared the official wording of five providers in LLM API data retention compared. A zero data retention arrangement answers the retention question well, but you still need a contract and a transfer basis. Our ZDR checklist covers the technical side.
International transfers: where do prompts go?
If the provider processes prompts outside the EEA, Chapter V of the GDPR applies. In practice:
- Adequacy. The Commission keeps a list of adequacy decisions. For the US, the EU-US Data Privacy Framework decision (10 July 2023) covers only companies on the Data Privacy Framework List. Check the exact legal entity you contract with.
- Standard Contractual Clauses. If the company is not on the list, the usual basis is the Commission’s SCCs, with a transfer impact assessment.
- Onward transfers. Ask where subprocessors process data. A provider in one country can fail over to capacity in another.
Other regimes work differently. Egypt, for example, requires a licence or permit from its data protection regulator for most transfers abroad; see Egypt’s data protection law and LLM APIs. For Saudi Arabia and the UAE, see the PDPL checklist.
How do you minimise personal data before sending it?
The strongest control is the one you run yourself. Article 5(1)(c) requires data minimisation, and it also shrinks your exposure to every answer above:
- Strip names, emails, phone numbers and IDs the model does not need.
- Replace them with placeholders and map them back after the response.
- Never send special-category data (Article 9) unless you have a basis and a clear need.
- Keep your own logs free of prompt content.
We cover redaction, placeholders and logging in detail in sending sensitive data to an LLM API.
What are the red flags in a provider’s GDPR answers?
- “We are GDPR compliant” with no DPA to sign.
- No subprocessor list, or one that leaves out the GPU host.
- Training “may” happen, with no clear default for API customers.
- Retention described only as “a limited period”.
- No answer on where failover traffic runs.
Where BroadNet Inference fits
BroadNet’s privacy statement (effective September 2026) answers several of the questions directly. It says the gateway “keeps no prompts, messages, images, audio, responses or transcripts”, and that “We do not use your inference data to train, fine-tune or evaluate models.” It keeps content-free usage records “for as long as billing, tax, security and legal obligations require”. Details are on our zero data retention page.
On location, the statement says BroadNet’s own and hosted open-weight models run “on BroadNet-owned or leased hardware in the United States, with partner capacity as backup”, and that a current subprocessor list “is available to customers on request”. For residency needs it asks customers to agree processing locations before sending data.
What it does not cover: the privacy statement does not mention a DPA or the GDPR by name. If you process EU personal data, ask BroadNet for its DPA, its subprocessor list and its transfer basis before you go live, exactly as you would with any provider on this list. You can also lock keys to your servers with IP allow-lists. For the wider provider decision, see the 20-point LLM API checklist.
