Standard Contractual Clauses for AI Vendors: Select the Contract by Route
The European Commission modernized its standard contractual clauses on 4 June 2021. AI procurement teams still need to match the contract to the parties and roles, plus the data route and destination involved in each vendor service. This guide organizes SCC selection around an evidence pack for LLM vendors, including access locations, subprocessors, data classes, approved endpoints, supplementary measures, suspension, change control, and retention.

The European Commission modernized its standard contractual clauses on 4 June 2021. For an AI vendor, the signature page is the last visible layer of a much larger selection problem. The buyer has to identify the parties and their roles, trace the service's data route, select the clauses that match that arrangement, and collect enough technical evidence to operate the contract after signing.
TL;DR
- Select SCC terms against the actual exporter and importer, processing roles, plus the LLM data route and destination.
- Attach destinations and access locations, subprocessors and data classes, plus retention and supplementary measures to the procurement record.
- Define suspension and deletion, plus audit evidence and change-notification paths before approval.
- Use runtime request records to verify approved routes. Keep legal module selection and clause effectiveness with counsel.
Clause selection starts with roles and routes
The Commission's 2021 SCCs use a modular structure intended to cover different transfer arrangements. Counsel should select the applicable module after the buyer identifies the exporter and importer, plus the processing roles for the service in question.
For an LLM service, name the contracting entity and the entity receiving personal data. Record who determines the purpose of the processing, who acts on instructions, where another processor enters the chain, and how each role applies. Then link those roles to the deployed route. A direct API service and a vendor application with an embedded model can differ from a processor using another model provider, producing different party maps.
My opinion is blunt: a generic data processing addendum with no route diagram deserves a procurement hold. The AI vendor risk assessment template gives the wider diligence questions. The SCC file needs the narrower facts that determine which contractual arrangement covers each transfer.
The procurement file needs a service-level data map
A vendor name is too coarse for SCC selection. Build the record at the service and route level. Identify the product and model service, the API endpoint and hosting location, plus every country where vendor personnel or subprocessors can access transferred personal data. Include remote support access because the EDPB treats remote access from a third country as a possible transfer.
Add the data classes the service may receive and the business purpose, plus data-subject groups and expected frequency, followed by the deletion or return path. Keep prompts and retrieved context, uploaded files and responses, telemetry and support records, plus abuse-monitoring records separate when the vendor handles them differently. The contract owner should be able to point at each category and show the recipient and destination, plus the purpose and control set.
On the table in front of the reviewer should be one redlined addendum, one route diagram, one page listing access countries, and the service record. If those four artifacts describe different services, approval has outrun the evidence.
Schrems II keeps effectiveness in scope
Standard contractual clauses survived the Schrems II judgment, while Privacy Shield was invalidated. The Court required essentially equivalent protection and made suspension necessary when the clauses lack effective implementation and other measures fail to secure the required protection.
After counsel selects the module, the buyer still needs an assessment of destination law and practice for the circumstances of the transfer, followed by supplementary measures where needed. The EDPB's Recommendations 01/2020 place those tasks inside a six-step process that starts with mapping and ends with reevaluation.
The transfer-impact workflow owns that legal and contextual analysis. Procurement should carry its result into the vendor file: the approved route and data classes, supplementary measures and residual conditions, procedural steps and suspension trigger, plus the reevaluation owner. The SCC record then points to a live decision rather than a detached PDF.
AI vendor evidence should make promises testable
Translate the approved transfer conditions into evidence requests. Ask the vendor where it hosts data and which teams can reach it. The response should name relevant subprocessors, explain government requests, document encryption and key control, and set terms for retention, deletion, incidents, and material changes. Connect each contract promise to an artifact the buyer can inspect or a behavior the buyer can test.
The AI MSA addendum guide explains how to turn vendor statements into duties. For SCC procurement, use that discipline to define the exact service and transfer. Require notice before a new subprocessor or access country changes the assessed route. Define who supplies updated information and the period allowed for review. Record what happens to new transfers during that review.
Cleartext processing deserves explicit treatment. The EDPB identifies cloud scenarios where a recipient needs data in cleartext and problematic law applies, with no effective technical measure found for that scenario. Ask where the LLM service can read submitted content and who can access it, then identify which supplementary measures apply there. A statement that data is encrypted in transit answers a different question.
Contract operation needs stop and change paths
A usable SCC package includes an operational response when facts change. The vendor may add a subprocessor, move a service, change support access, alter retention, introduce another model provider, or modify the route. Each event can affect the transfer map and the assessment attached to it.
Define a change register with a named procurement owner and privacy reviewer, plus a technical owner and legal owner. The entry should identify the affected service and the old route facts, the new route facts and assessment status, plus the decision and implementation date. Connect high-impact changes to a route hold until the designated legal owner approves continued transfer.
Suspension also needs an executable control. The contract can state when transfer must stop. Platform teams need the endpoint and account, plus the data class and policy that should deny access. A tested suspension path reduces the gap between counsel's decision and the next live request. Preserve the test result beside the contract record.
Runtime evidence supports contract oversight
Procurement evidence describes what the vendor and buyer agreed. Runtime evidence shows what happened on a managed request. For each deliberately routed LLM call, a useful record can identify the caller and application or agent, the data classification and destination endpoint, the region and minimization action, plus the policy version and outcome.
Those fields support periodic checks against the approved service record. Reviewers can sample requests and confirm that covered data reached only approved endpoints under the expected policy. The record can also reveal drift, such as a new destination or a route missing the data classification required by the approval.
The AI vendor due diligence questionnaire belongs earlier in the buying process. Runtime sampling follows approval and continues through the contract term. Together they connect diligence and contracting with operation and reevaluation, without pretending that a gateway log proves every vendor-side fact.
The approval packet
A concise SCC approval packet should let a new reviewer reconstruct the decision without searching email. Include these artifacts:
- contracting entities and processing roles, plus counsel's selected SCC module and decision date
- service-level route map with hosting and remote access, subprocessors, and service identifiers
- data categories and purposes, minimization rules and retention, plus return and deletion
- destination-law assessment, approved supplementary measures, residual conditions, and review date
- completed procedural steps and signed contract version
- approved endpoints and regions, accounts, plus the technical policy owner
- change-notification and reevaluation, escalation and suspension procedures
- vendor evidence and the most recent route-control test
Assign an owner and review trigger to each artifact. The packet should preserve legal analysis as legal analysis and vendor assertions as vendor assertions, while keeping observed request evidence as observed request evidence and route-control tests as route-control tests.
DeepInspect
DeepInspect can enforce approved routing facts for authenticated HTTP LLM calls deliberately sent through it. Policy can evaluate the supplied identity and data class, apply minimization rules, and permit only an approved endpoint or region. The resulting per-decision record can support procurement sampling and change reviews.
DeepInspect cannot select an SCC module, perform the legal assessment, verify every vendor-side promise, or make the clauses effective. It provides a narrow technical control and evidence surface after counsel and procurement, plus privacy owners, define the approved transfer. Book a technical deep dive at deepinspect.ai.
Frequently asked questions
- Are the 2021 SCCs enough by themselves for an AI vendor transfer?
The Commission's SCCs provide a transfer tool. Schrems II requires effective protection in the circumstances of the transfer. The buyer and recipient need to assess destination law and practice, adopt supplementary measures where needed, complete required procedures, reevaluate the arrangement, and document the result. Counsel should decide whether the complete package supports the transfer.
- Who selects the SCC module for an AI vendor?
Qualified legal counsel should make the legal selection. Procurement and technical teams supply the underlying facts: contracting entities and controller or processor roles, recipients and subprocessors, service routes and destinations, plus data categories and access patterns. Counsel needs those facts before selecting the module.
- Should every vendor product share one SCC record?
A single vendor can operate several products with different entities and subprocessors, endpoints and hosting regions, plus support paths and access countries. Build the evidence at the service and route level, then let counsel decide how the contract package groups those services.
- Can request logs prove SCC compliance?
Request logs can prove facts about managed traffic, such as supplied identity and data class, endpoint and region, minimization action and policy, plus outcome and timestamp. They cannot prove vendor-side behavior outside the route, complete the destination-law assessment, select the SCC module, or establish that the clauses remain effective.