BroadRouter
Get started

Subprocessor

Updated

A subprocessor is a third party that a processor engages to carry out processing of personal data on behalf of the controller. For an LLM API, subprocessors can include GPU hosts, partner inference providers and backup capacity. Under GDPR Article 28 they need the controller's authorisation and the same data protection obligations.

Also called: sub-processor

Your contract is with one provider. Your prompt may still touch three companies. Subprocessors are the ones you do not see.

How it works

The GDPR sets up a chain. You are usually the controller, the LLM provider is your processor, and anyone the provider uses to handle your data is a subprocessor (the regulation says “another processor”). Article 28 sets two rules:

  • Authorisation (28(2)). “The processor shall not engage another processor without prior specific or general written authorisation of the controller.” With general authorisation, the processor must inform you of intended additions or replacements, “thereby giving the controller the opportunity to object”.
  • Same obligations (28(4)). The data protection obligations in your contract must be imposed on the subprocessor by contract. If the subprocessor fails, “the initial processor shall remain fully liable to the controller”.

In practice, providers publish a list and a way to follow changes. Mistral’s help center says its list “is available at all times on our Trust Center” and that customers can subscribe to email notices when a subprocessor is added or removed. Its DPA gives general authorisation and a ten-day window to object in writing.

A typical LLM API request path might look like this:

Step Who Subprocessor?
Your app You No, you are the controller
API gateway The provider No, the processor
GPU host or partner model Cloud or inference partner Yes, if it processes the prompt
Failover capacity Another host Yes

Why it matters

  • Location. Each subprocessor can be in a different country, which matters for data residency and transfer rules.
  • Retention. A provider’s zero data retention promise only holds if each subprocessor follows it.
  • Routers add layers. A hosted LLM router sits between you and the model provider, so check both.

The GDPR checklist lists the questions to ask: who the subprocessors are, including GPU hosts and backup capacity, and how you are told about changes.

On BroadNet Inference

BroadNet’s Terms (§7.3a) say: “Partner-hosted and backup processing involves other processors. A current subprocessor list is available to customers on request.” The privacy statement says the same. BroadNet does not publish the list on a public page, so ask for it through the contact page before you send regulated data.

What BroadNet does state publicly: its own and hosted open-weight models run on BroadNet-owned or leased hardware in the United States, with partner capacity as backup. Partner-served models, such as DeepSeek V4.1 Flash, run under zero-data-retention terms with US inference partners. This is a summary, not legal advice.

Questions

Is a cloud GPU host a subprocessor of an LLM API?

Usually, if it processes your prompts and those prompts contain personal data. Ask the provider for the full list, including partner inference providers and backup capacity, not only its main cloud.

Can I object to a new subprocessor?

Under GDPR Article 28(2), where you give general written authorisation the processor must tell you about intended changes and give you the opportunity to object. The notice period and process are set in the DPA; Mistral's DPA, for example, allows a written objection within ten days of notice.

Does BroadNet publish a subprocessor list?

Not publicly. Its Terms and privacy statement say a current subprocessor list is available to customers on request.

Read as MarkdownAsk ChatGPTAsk ClaudeAsk Perplexity