For healthcare, finance, and government buyers, one sentence in a security review — 'your data never leaves your VPC' — often decides whether a deal closes at all. It's also one of the most loosely used claims in AI vendor marketing, because making it actually true requires specific architectural commitments most point solutions were never built for.
What the claim actually requires
- Private model endpoints — inference must run inside your cloud boundary or through a private connection, not a public API call that transits the vendor's infrastructure regardless of encryption in transit.
- No prompt logging by the model provider — many API terms permit the provider to log and potentially retain requests for abuse monitoring or model improvement unless you've explicitly opted out or negotiated a data processing agreement that forbids it.
- Data processing agreements matching your compliance framework — HIPAA business associate agreements, SOC 2 vendor assessments, or GDPR data processing addenda need to name the specific AI vendor and specific data flows, not a generic cloud provider agreement that predates the AI feature.
- Weights versus API calls — a genuinely private deployment (open-weight model in your own infrastructure) makes a stronger residency claim than any third-party API, because there's no external network call to secure at all.
The checklist for verifying a vendor's claim
Ask for the specific data processing agreement naming AI data flows, not a general terms-of-service link. Ask whether prompts and outputs are logged by the model provider and for how long. Ask whether the deployment can run in a private endpoint or VPC peering configuration, or whether it's a public API regardless of how the sales deck phrases it. A vendor who can't answer these specifically hasn't built for residency — they've written a sentence that sounds like it.
This isn't a compliance checkbox — it's frequently the deal-closing detail. A healthcare or fintech buyer's security team will ask these exact questions, and the difference between a real answer and a marketing answer is the difference between a signed contract and a stalled procurement review.