Procurement
Contractual Language That Binds Vendors to Zero Training on Enterprise Prompt Data
Vendor commitments must cover subprocessors, survive termination, and resist policy changes.
Sujata Krishnamurthy
· 9 min read
Vendor commitments must cover subprocessors, survive termination, and resist policy changes.
Enterprises need technical proof, not promises, that vendors cannot access proprietary AI data.
Distinguish between contractual promises and architectural safeguards when evaluating AI vendors.
Combining contracts and architecture closes the gaps each alone leaves open.
Sensitive data leaks across tenant boundaries through cache timing, orchestration, compute.
TEEs encrypt AI prompts during processing, not just in transit.
Security patches won't stop prompt injections; enterprises must limit AI assistant access instead.
Architectural controls matter more than contractual promises when assessing AI vendor data risks.