Every AI vendor sales pitch references data residency. Almost none of the standard contracts actually deliver it. The default OpenAI, Anthropic, Microsoft Copilot and Google Gemini enterprise terms grant region-of-processing commitments that are heavily caveated — training datasets, model fine-tuning, telemetry, and incident-response data each have their own residency footprint, and the standard contract papers them over. The clauses that hold are not in the default template.
An AI service does not have a single data residency posture; it has five. Each one needs to be mapped, contractualised and audited. The vendor's default residency commitment usually covers only the first one.
The prompt the user sends and the completion the model returns. This is the data the vendor will commit to residency on. The clauses are mature and the technical controls (region-pinning, in-region key management) are typically deliverable.
Whether customer prompts are used for model training. The default enterprise position from frontier-model vendors is "no training" for enterprise tenants — but the clause is sometimes scoped to a specific deployment and not to all interactions. Read the scope carefully.
If the customer fine-tunes a model, where the fine-tuned weights are stored. Some vendors store fine-tuned weights in a region different from the inference region. The fine-tune residency clause needs to be explicit.
Vendors typically retain interaction logs for abuse monitoring (usually 30 days, sometimes longer). The retention region is frequently not the customer's region of processing. The standard contract usually allows it; explicit residency clauses can constrain it.
When an incident occurs — content violation, suspected jailbreak, security event — the vendor pulls a snapshot of the affected data into a security-response environment that may sit outside the standard residency boundary. This is the footprint regulators care about most and contracts cover least.
We map all five residency footprints and pre-negotiate the clause language for each.
The standard residency clause in most AI vendor contracts reads "data will be processed in the [region] region." This is too thin. The clauses that hold under regulator scrutiny — Schrems II, FedRAMP, GDPR Article 28, the EU AI Act conformity provisions — are specific in three dimensions.
The clause should enumerate the residency commitment for each of the five footprints separately. A blanket "data" commitment is rarely sufficient under regulator review.
What happens if the vendor needs to move the residency footprint — for capacity, for a region launch, for an acquisition. The clause should require advance notice (90 days is typical), a customer right of objection, and a remediation path that does not require the customer to bear migration cost.
AI vendors routinely subcontract to hyperscalers, GPU providers, model-host operators. Each sub-processor inherits a residency posture. The contract should require a sub-processor list, a residency commitment that flows through the supply chain, and a customer notification right for new sub-processors.
Includes the five-footprint residency template and the sub-processor mapping checklist.
Enterprise tenants get a "no training" default and a US-by-default residency footprint, with EU residency available on request as of 2024. Fine-tune storage and telemetry residency are typically aligned with the inference region but should be confirmed in the order form. Sub-processor list available under NDA.
Azure OpenAI inherits the broader Azure residency model — explicit region pinning, in-region key management options, and the Azure DPA flowing through. Training is opt-out by default for enterprise tenants. The incident-response footprint follows Azure's standard model.
Enterprise tenants receive a "no training" default. Inference residency is configurable by region. Sub-processor disclosure is typical for enterprise contracts.
Inherits the Google Cloud residency model with explicit region selection, customer-managed encryption keys, and a sub-processor list. Training defaults to opt-out for enterprise.
Across all four, the standard contract gets the inference footprint right and gets the other four footprints incomplete. The negotiation is in the order form, not the master agreement. Our SaaS procurement advisory team maps the clause language for each footprint and pre-negotiates it into the order form before signature.
Data Protection Officers and external auditors increasingly scrutinise AI vendor contracts for the residency posture under specific compliance regimes. The questions cluster around five themes.
We pre-package the residency posture in the format DPOs and auditors actually accept.
Our AI procurement practice maps the full five-footprint residency posture and pre-negotiates the clauses that hold.
Weekly compliance intelligence for IT leaders.