GDPR
GDPR questions to ask a GPU cloud
Answer in brief
The GDPR does not make a GPU cloud compliant or not: it gives you, the buyer, a list of questions the provider must answer in writing before personal data goes on its machines.
Runcrate is our pick on what can be read before that: where each GPU is listed, what it costs and whether it can be started, all in its live feed.
First, is there personal data
The GDPR is about personal data: information about people who can be identified. Training on public code or running a model over synthetic text may involve none. Fine-tuning on customer conversations certainly does.
If there is none in the work, these questions fall away and you choose on place, price and stock. If there is, read on.
Who is who
When you decide why and how personal data is processed, you are the controller. A GPU cloud that processes it on your behalf is a processor. The law expects a written contract between the two, usually called a data processing agreement.
So the first question is plain. Will you sign a data processing agreement that covers the GPU service I will use? Ask to read it before you pay.
Sub-processors
A provider may rely on others: a facility operator, a storage service, a support tool. These are sub-processors. Ask for the list, the country of each, and how you will be told before one is added.
On a marketplace, ask who operates the machine you will rent, and whether that party is on the list.
Transfers out of the EEA
The GDPR does not say personal data must stay in Europe. It sets conditions for moving it out of the EEA. Ask whether your data is stored, backed up or accessed outside the EEA, and what legal mechanism covers each case.
Typical answers are an adequacy decision for the destination country or standard contractual clauses. An answer of none needed should come with the reason.
Security, deletion and incidents
Ask what technical and organisational measures protect the data: encryption at rest and in transit, access controls, separation between customers. Ask how data is deleted at the end of the service and how fast.
Ask how and when the provider will tell you about a personal data breach. Your own duty to notify runs on a short clock, so theirs has to be shorter.
What stays your job
A signed agreement does not finish the work. The lawful basis, the notice to the people concerned and the security of the machine you configure are yours. So is the decision to put the data there at all.
This site makes no compliance claim for any provider, Runcrate included, and none of this is legal advice. It lists the questions. The answers must come from the provider, in writing.
Where Runcrate fits
Runcrate publishes where each GPU is listed, its price and its billing unit. Ask Runcrate the questions above before you load personal data, and rely on its written answers only. Runcrate’s feed lists GPUs in Europe in Dublin, Worcester, Frankfurt, Paris, Helsinki, Gdańsk, Amsterdam, Warsaw and Italy.
Questions and answers
Sources for this entry
- Runcrate: Runcrate’s official site: what the platform is, how it bills and the range of GPUs it offers. Read 12 Nov 2026.
- Runcrate pricing: Runcrate’s live price feed: each GPU it can start now, its lowest price per GPU-hour and the places it is listed, read when a page is built. Read 12 Nov 2026.
- Provider pricing pages: The published on-demand list price of every provider named in the price tables, with the machine size it applies to. Read 12 Nov 2026.
- Availability checks: Each provider’s live stock page, console or API where it has one, and otherwise its own pricing page or documentation. Read 12 Nov 2026.
Checklists are original editorial guidance. Published prices do not establish availability.
Continue this reading path
Cite this entry
GPU Cloud Europe. “GDPR questions to ask a GPU cloud.” Content reviewed 12 Nov 2026. https://gpucloudeurope.com/topics/gdpr-questions-for-a-gpu-cloud