Cetrix SA All articles
Cloud Infrastructure

Where the Model Actually Lives: Five Residency Questions to Ask Before You Sign an AI Contract

Cetrix SA
Where the Model Actually Lives: Five Residency Questions to Ask Before You Sign an AI Contract

Photo: Intel Free Press, CC BY 2.0, via Wikimedia Commons

The demo is always excellent. The model is fast, the interface is clean, the pilot results are encouraging, and the security questionnaire comes back with reassuring checkmarks. Then legal asks a simple question about where customer prompts are processed, and the sales engineer goes quiet.

This pattern has become routine. AI adoption in U.S. enterprises has outpaced the procurement vocabulary built to govern it, and data residency is where that gap shows first. Roughly two dozen state comprehensive privacy laws are now in force, several with enforcement regimes that have moved past the warning-letter stage, and the patchwork means a single AI deployment can sit inside four different regulatory theories at once.

None of this argues against adoption. It argues for asking better questions earlier, ideally before the security review becomes a negotiation and long before the invoice.

1. Where does the training corpus actually live, and who can reach it?

Most vendors answer this question about the model. Ask instead about the corpus.

Training data location determines your exposure far more than inference location does, because training data is durable and inference data can often be discarded. Ask for the hosting region of the corpus, the cloud provider, and the class of personnel with read access. Then ask the follow-up that matters: is any of that access provided through a shared administrative plane that also serves customers in other jurisdictions?

If the answer is a data processing agreement that describes processing generally without naming regions, treat it as an unanswered question. Generality in a DPA is not neutrality. It is optionality held by the vendor.

2. Which subprocessors touch the payload, and how current is the list?

The subprocessor list is where residency claims usually break. A vendor may host inference in Virginia while routing telemetry, logging, and abuse monitoring through services that terminate elsewhere. Those are not incidental. Logs frequently contain the most sensitive fragments of a prompt.

Request the current list, in writing, with the function each subprocessor performs and the regions it operates in. Then ask two procedural questions: how much notice is given before the list changes, and what right of objection the customer holds. A list that can be amended silently is a list that will be amended silently.

For U.S. buyers working with offshore engineering partners, this is often where the real complexity sits. A partner may assemble a composed solution from several model providers, each with its own subprocessor chain. The integration layer you are buying can therefore inherit three residency postures at once, and nobody will volunteer that unless asked directly.

3. How long are prompts and outputs retained, and can retention be disabled in contract?

Retention is the quietest risk in the stack, because it converts a transient disclosure into a standing archive.

Ask for specific durations by data type: prompts, completions, embeddings, fine-tuning artifacts, and derived telemetry. Distinguish between default retention and configurable retention, and confirm which applies to your tenant. Where abuse monitoring requires temporary retention, ask whether that window can be shortened and whether the monitoring corpus is human-reviewed.

The procurement point is that retention should be a contractual setting, not a dashboard toggle an administrator can reverse. If the answer is a product configuration, ask what prevents it from changing.

4. What legal mechanism supports the cross-border hop?

If any part of the pipeline crosses a border, the transfer needs a stated mechanism, and the mechanism needs to survive scrutiny. Standard contractual clauses remain the workhorse for many arrangements, supplemented by transfer impact assessments. The EU-U.S. Data Privacy Framework applies to certified organizations and to the specific scope of their certification, which is narrower than marketing materials often imply.

Ask which mechanism applies to your data, which entity is the exporter, and whether a transfer impact assessment has been completed for the destination. Ask also whether the vendor will notify you if the mechanism is invalidated or the certification lapses. A residency commitment without a transfer mechanism is an aspiration.

5. What does an audit right actually let you inspect?

Audit clauses are frequently long on language and short on access. A right to receive a summary of a third-party report is not the same as a right to inspect configurations.

Ask precisely what you may examine: the subprocessor register, the retention configuration for your tenant, the access logs for your environment, the results of penetration testing. Ask how much notice is required, whether audits can be conducted remotely, and whether the vendor may substitute a certification in place of an inspection. Substitution is common and not unreasonable, but you should know which you are buying.

The clauses that carry the weight

Four provisions do most of the protective work in an AI contract. A defined-data-location warranty naming regions rather than countries. A subprocessor change clause with notice and objection rights. A retention schedule expressed in days with a deletion certification on request. A regulatory-change clause obliging the vendor to notify you and cooperate on remediation if a transfer mechanism fails.

Add a service credit or termination right tied to residency breach. Without a consequence, a warranty is a preference.

A note on leverage

The uncomfortable reality is that most U.S. buyers are not the vendor's largest customer and will not negotiate a bespoke architecture. What they can do is buy selectively. Some workloads genuinely require the frontier model. Many do not. Classifying use cases by data sensitivity before the vendor shortlist is formed will do more for your residency posture than any clause negotiated in the final week.

Ask the five questions early, in writing, and compare answers across vendors using the same template. The vendors who answer precisely are usually the ones who built the system to be answered about.

All Articles

Related Articles

Rethinking the Center of Gravity: How Strategic Infrastructure Placement Across Africa Can Slash Costs and Latency for US Enterprises

Rethinking the Center of Gravity: How Strategic Infrastructure Placement Across Africa Can Slash Costs and Latency for US Enterprises

Cloud Migration Cost Overruns Are Avoidable: The Enterprise CTO's Due Diligence Checklist

Cloud Migration Cost Overruns Are Avoidable: The Enterprise CTO's Due Diligence Checklist

The Cheap Build Isn't Cheap: Scoring Maintainability Before You Sign

The Cheap Build Isn't Cheap: Scoring Maintainability Before You Sign