04 — Termination
IAIL Exit
What are you still carrying after termination?
When you end an AI vendor relationship, the standard deletion certificate covers what the contract calls “data.” It does not cover what AI systems created from your data. Embeddings, fine-tuning artefacts, model memorisation. Some of that does not go away. Exit documents exactly what stays and what the enterprise needs to govern permanently.
Applies
AI Data Persistence Taxonomy
Covers
Nine persistence categories
Produces
Inability-to-Cure Register
Detail
How Exit works
Nine categories. Most deletion clauses address only the first.
- P1 Stored Data
- P2 Vector Embeddings
- P3 Fine-Tuning Artefacts
- P4 Model Memorisation
- P5 Cached Inference Outputs
- P6 Prompt Logs
- P7 Prompt-Borne Artefacts
- P8 Backup and Disaster Recovery Copies
- P9 Derived Analytics and Profiles
Exit tests the vendor’s deletion certificate against all nine persistence categories. It identifies which categories the certificate actually covers and which it doesn’t. The gap between what the certificate says and what the vendor’s system retains is the residual liability.
For each persistence category that cannot be deleted: the technical reason, the data subjects affected, the ongoing regulatory exposure, any commercial sensitivity in the irremediable data, the compensating governance measures, the named executive approving the residual risk, and the review date.
This is not a document about failure. It is evidence of governance. The enterprise that can produce this for every terminated AI vendor relationship has proof it knew its position, assessed it, and made decisions about how to carry it.
At the end of any AI vendor relationship. During vendor transition planning. When a vendor is acquired. Any time you need to document what the enterprise carries permanently.
Next Step
Document what stays
If you are ending an AI vendor relationship, Exit tells you what you still carry and how to govern it.