Authorisation first
A processor shall not engage another processor without the controller’s prior specific or general written authorisation (Article 28(2)).
GDPR, Article 28What the GDPR says about subprocessors, why a model provider is often one, and what to check when a vendor adds another.
An AI subprocessor is a company that a vendor engages to process its customers’ data as part of delivering an AI feature, such as the model provider that receives prompts or the cloud that hosts the model.
The term comes from data protection law, where a processor needs the controller’s authorisation before engaging another processor.
The regulation says “another processor”. The market, and the European Data Protection Board, say sub‑processor.
A processor shall not engage another processor without the controller’s prior specific or general written authorisation (Article 28(2)).
GDPR, Article 28With general authorisation, the processor informs the controller of any intended addition or replacement, giving the controller the opportunity to object.
The same data protection obligations are imposed on the other processor by contract. If it fails, the initial processor remains fully liable to the controller (Article 28(4)).
EDPB Opinion 22/2024A model provider receives the prompt itself, which can hold personal data, contracts or source code, not only metadata.
The question is not only where data goes, but whether it is retained or used to train or tune a model. Ask per subprocessor.
A vendor can add or switch a model provider in a release. Under general authorisation, the notice of that change is your chance to object.
Subprocessor rules cover personal data. A model provider that sees only other business data can sit outside the list and still be a fourth party.
Fourth-party AI risk| AI subprocessor | Fourth party | ICT subcontractor | |
|---|---|---|---|
| Comes from | Data protection law (GDPR Article 28) | Third-party risk practice | Financial regulation (DORA Articles 29 and 30) |
| Defined by | Processing personal data for the controller, under a processor | Any supplier your vendor depends on | A provider to which ICT services are further subcontracted |
| Your lever | Authorisation and the right to object | Terms your vendor must pass down | A contract that says whether subcontracting is permitted, and how |
Straight answers, kept current. Last updated .
Ask us anything →When a vendor sends its customers’ personal data to a model provider to deliver the service, that provider processes the data on the customer’s behalf under the vendor, the position GDPR Article 28 describes as another processor. Whether a given arrangement qualifies depends on the facts and the contracts, so ask the vendor how it classifies each model provider, and have counsel confirm.
Under the GDPR, the processor needs the controller’s prior specific or general written authorisation. With general authorisation, the vendor must inform you of intended additions or replacements and give you the opportunity to object. How notice is delivered and how long you have to object come from the contract, so check both before you sign.
Ask for the current subprocessor list and, separately, the model providers and hosts behind each AI feature, because the two do not always match. Then ask for evidence. In Cranium AI, you can request an AI Card from the vendor, specifying a bill of materials and additional documentation with a due date, and review what comes back.
Primary sources for the figures and frameworks cited on this page. Last verified .
See how Cranium AI discovers, observes, governs, secures and proves every AI model, agent and vendor in your enterprise.
Cookie Policy · Privacy Policy
Global Privacy Control detected. Opt-out request honored: marketing tags stay off in this browser.