Termination & Exit

Standard paper defines Customer Data as 'data uploaded by Customer.' Derivatives, generated by the service rather than uploaded by the customer, fall outside the return obligation. The vendor hands back your PDFs but not the retrieval index. You have the ingredients without the recipe. Switching costs become prohibitive. That lock-in is what the exit clause is supposed to prevent.

The data return scope problem is foundational. Standard vendor language offers a 30-day export in the vendor's standard format. Two gaps: 'Customer Data' does not include derivatives, and 'standard format' usually means a CSV dump. The enterprise counter requires: a complete export of all Customer Data including all derivatives, structured indices, and logs in a platform-agnostic, machine-readable format; reasonable transition assistance at no additional cost for 90 days; and permanent deletion of all copies with a certificate of deletion within 30 days of export completion. This covers scope (derivatives included), format (platform-agnostic), timing (90 days with assistance), and deletion verification.

Four AI-specific termination triggers go beyond the standard 30-day cure period for material breach. Model deprecation: the vendor swaps the underlying model, output quality degrades on your use case, the service is technically 'available' but the AI feature is unfit for purpose. Regulatory shift: a regulator rules that the model architecture violates local law — the vendor cannot cure that in 30 days. Safety incident: the AI generates harmful outputs — biased results, fabricated sources — requiring immediate pause, not a 30-day wait. Model provider terms change: the vendor's underlying model provider changes its API terms in a way that undermines the vendor's contractual commitments on zero data retention, training restrictions, or security obligations.

The Substantial Modification trigger is the most frequently negotiated AI-specific termination right. The vendor must provide at least 30 days' notice before a material model change. If the change materially degrades the documented use case and the vendor cannot restore performance within 30 days, the buyer may terminate the affected Service Order without penalty. The 'documented use case in the Order Form' anchors the trigger — preventing vendor claims that any update is not a modification while protecting the buyer's actual workflow.

Suspension rights require balancing. Vendors reserve broad suspension rights — for non-payment, suspected misuse, 'threats to the service.' Buyers need to narrow those rights and add mutual suspension for AI-specific safety or compliance risks. The compromise: vendor retains the right to suspend immediately for security reasons but must provide notice and the grounds; if suspension exceeds 30 days, the customer may terminate without penalty. The vendor's operational risk justifies unilateral security suspension; the termination backstop prevents indefinite suspension being used as leverage.

Red Flags

• A data return clause that defines Customer Data by reference to what was 'uploaded' — derivatives not included
• Export offered in 'vendor's standard format' with no commitment to platform-agnostic, machine-readable output
• A termination section with no AI-specific triggers — only standard material breach and 30-day cure
• A suspension right the vendor can exercise for 'any reason' with no notice requirement
• An exit window shorter than 60 days — insufficient time to migrate AI-specific data structures
• No deletion certificate — the buyer has no verification that derivatives have actually been deleted

Sample Clause (Illustrative)

"Upon termination, Provider shall, within 60 days, make available to Customer a complete export of all Customer Data (including all derivatives, structured indices, and logs as defined in Section X) in a platform-agnostic, machine-readable format. Provider shall provide reasonable transition assistance at no additional cost for a period of 90 days following termination. Provider shall, within 30 days of export completion, permanently delete all copies of Customer Data from its systems and provide a written certification of deletion signed by an authorized officer. Customer may terminate the affected Service Order without penalty if: (a) Provider makes a Substantial Modification to the AI Services that materially and adversely impacts Customer's use case as documented in the Order Form and Provider cannot restore performance within 30 days of notice, (b) an AI Safety Incident occurs and Provider fails to remediate within 15 days, (c) a change in applicable law renders continued use of the AI Services unlawful or commercially unreasonable, or (d) a material change to the terms of service of any Third-Party AI Provider undermines Provider's compliance with its data protection, training restriction, or security obligations under this Agreement and Provider cannot restore compliance within 30 days."

Covers the four components that standard termination clauses omit in AI deals. Data return scope: derivatives and structured indices are explicitly included, the export format is platform-agnostic rather than the vendor's proprietary format, and a deletion certificate is required. Transition assistance: 90 days of migration support at no cost gives the buyer a realistic window to stand up a replacement system. AI-specific termination triggers: the Substantial Modification right is pinned to the documented use case in the Order Form, preventing abuse while protecting real degradation. The deletion certification by an authorized officer creates personal accountability for the verification.

Illustrative only. Clause language requires adaptation to your jurisdiction, deal context, and risk profile. Not legal advice.