Schrems II for LLM Transfers: Build the Assessment Around the Route
Schrems II preserved standard contractual clauses while requiring protection that remains essentially equivalent after personal data leaves the EEA. For LLM deployments, the work starts with the actual request route, including cloud processing and remote access outside the EEA. This guide applies the EDPB six-step method to model traffic and separates legal assessment from the technical evidence an authenticated HTTP route can produce.

A prompt can cross a border before the first token returns. The route may involve a model endpoint or cloud infrastructure outside the EEA. Support personnel may also access hosted data remotely. The Court of Justice of the European Union's Schrems II decision invalidated the EU-US Privacy Shield and preserved standard contractual clauses. It also required essentially equivalent protection for transferred personal data. That puts the real data route at the center of the assessment.
TL;DR
- Map each LLM data route, including cloud processing and remote access outside the EEA.
- Identify the transfer tool, then assess the destination country's law and practice against the protection required in the EU.
- Select supplementary measures and complete required procedures. Schedule reevaluation.
- Keep legal conclusions with privacy counsel. Use routed HTTP evidence to prove identity and data class. The same evidence can prove destination and minimization while recording the policy outcome.
Schrems II changed the transfer test
Schrems II invalidated Privacy Shield because that mechanism failed the required level of protection. The Court upheld standard contractual clauses as a transfer tool, with a condition that matters operationally: the clauses must work in the destination context. Protection for transferred data has to remain essentially equivalent to the protection guaranteed inside the EU.
That test reaches beyond a signed document. Exporters and recipients need to consider the destination country's law and practice. They also need to consider the safeguards attached to the transfer and retain the ability to stop the transfer when effective protection breaks down. The Court's press release states that a supervisory authority must suspend or prohibit a transfer when the clauses receive no effective implementation and the required protection cannot be secured by other means.
I think an assessment that starts with the vendor's logo instead of the data route is paperwork wearing a security badge. The AI DPIA guide covers a related assessment, but the transfer analysis has its own question: what happens to this personal data after it leaves the EEA?
The EDPB six-step workflow
The European Data Protection Board's Recommendations 01/2020 turn the Schrems II requirement into six operating steps.
- Map transfers. Identify personal data leaving the EEA and verify that the data sent remains adequate and relevant to the task. Limit it to what the task needs.
- Identify the transfer tool. Record the legal mechanism used for each route.
- Assess destination law and practice. Examine anything that could undermine the chosen tool's effectiveness in the circumstances of the transfer.
- Adopt supplementary measures. Select technical measures that close the identified gap. Add contractual or organizational measures where needed.
- Complete procedural steps. Carry out any formal procedure required by the selected transfer tool and supplementary measures.
- Reevaluate. Monitor changes and revisit the assessment at appropriate intervals.
The six-step sequence matters because a team that chooses controls before mapping the transfer can protect the wrong route. A team that stops after signing clauses misses the destination assessment and reevaluation that give the clauses operational meaning.
LLM routes expand the transfer inventory
An LLM transfer inventory should follow the prompt and retrieved context through the response and operational access path. The EDPB treats remote access from a third country and cloud infrastructure outside the EEA as possible transfers. That means a region label on the application screen answers only part of the question.
Start with the controller or processor sending the request. Record the model service and exact endpoint. Add the destination and hosting region, the data categories in the prompt, and any retrieved context added by the application. Then identify parties that can access the data after transmission, including subprocessors and support teams in third countries. The GDPR AI compliance requirements guide places that inventory beside controls for purpose and minimization. It also covers security controls.
Picture a review meeting with one request diagram taped to the wall. A blue arrow leaves the EEA endpoint, crosses into a hosted model region, and branches toward a support console. That branch is where a tidy vendor questionnaire often stops matching the deployed system.
Destination assessment comes before control selection
Step three asks whether the destination country's law and practice can interfere with the transfer tool. This is a legal assessment tied to the circumstances of the transfer. Security architecture can supply facts about encryption and access, plus identity and data exposure, but it cannot decide whether a country's protections meet the legal standard.
The EDPB recommendations make a hard technical point for cloud use. When a recipient needs data in cleartext to provide the service and problematic law reaches that recipient, the EDPB identifies scenarios where no effective technical measure has been found. LLM inference commonly requires the provider's processing environment to handle the submitted content. Encryption in transit protects data before it reaches the endpoint. It leaves the processing question open once the service needs readable input.
That finding should shape the assessment without turning into a blanket ban on cloud models. Counsel needs the actual destination and recipient, the access pattern and legal environment, plus the proposed supplementary measures. The AI data residency controls guide explains how route policy can enforce an approved region after that legal decision has been made.
The evidence packet should mirror the route
A transfer impact assessment stays reviewable when its evidence follows the six steps. Keep the selected tool beside the transfer map, which should include the data categories. Attach the destination analysis and the supplementary measures chosen for that route. Record the procedural owner and approval date. Record the change triggers and next reevaluation point as well.
For an LLM request path, the technical packet can include the authenticated caller, application or agent, data classification, model endpoint, destination region, minimization action, policy version, and decision outcome. Vendor documentation should cover hosting and access locations, plus subprocessors and the controls the recipient actually operates. Contract records belong beside those technical facts, not inside a network log.
A change trigger should fire when the model endpoint, hosting region, subprocessor list, support-access pattern, data category, or relevant law and practice changes. The reevaluation then starts with the altered fact instead of rebuilding the whole assessment from memory.
Suspension needs an operational path
Schrems II makes suspension more than contract language. If the chosen tool loses effectiveness and supplementary measures fail to restore the required protection, the transfer needs a stop path. The legal owner decides when that threshold has been reached. Engineering needs a way to carry out the decision on the approved route.
For managed LLM traffic, that can mean removing an endpoint from the approved destination set or denying requests with covered data classes. An allowed workload can instead be routed to an approved regional service. The control owner should test the block before a legal escalation occurs. Preserve the test result with the policy version and the endpoint involved.
Privacy counsel owns the legal assessment, transfer tool, and suspension decision. Procurement owns recipient and contract evidence. Platform and security teams implement approved route policy. The request record shows whether the technical decision ran as designed.
DeepInspect
DeepInspect can enforce the route decision after the responsible teams approve it. For authenticated HTTP calls deliberately routed through DeepInspect, policy can evaluate the supplied identity, data class, destination, approved endpoint, and minimization action before forwarding the request. A per-decision record can preserve those same fields with the policy outcome.
That record supports the transfer map and proves how an approved technical rule operated on a specific request. DeepInspect cannot perform the legal assessment, select a transfer tool, judge foreign law, or make standard contractual clauses effective. It supplies evidence and route enforcement for one defined part of the wider transfer program. Book a technical deep dive at deepinspect.ai.
Frequently asked questions
- Does every call to an LLM create an international transfer?
The answer depends on the data and parties, plus the infrastructure, access, and destination involved. A model call containing personal data can enter transfer scope when the data goes to a recipient outside the EEA or becomes remotely accessible there. Map the deployed route and access pattern instead of assuming that every LLM call has the same status.
- Did Schrems II invalidate standard contractual clauses?
The Court invalidated Privacy Shield and upheld standard contractual clauses. Their use depends on effective protection in the circumstances of the transfer. The exporter and recipient need to assess destination law and practice. They must add supplementary measures where needed and suspend the transfer when the required protection cannot be secured.
- Can encryption solve the LLM transfer issue?
Encryption can protect data in transit and at rest. The EDPB also describes cloud-processing scenarios where the recipient needs cleartext and problematic law applies, leaving no effective technical measure identified for that scenario. The assessment has to examine when and where the provider can read the content, along with contractual and organizational measures.
- Can an AI gateway complete the transfer impact assessment?
A gateway can produce facts about deliberately routed HTTP requests. The legal assessment of destination law and selection of a transfer tool remain separate. So do the evaluation of supplementary measures and the decision to continue or suspend the transfer. Those responsibilities belong to the controller and its designated legal or operational owners.