Key takeaway
Expiration stops only what the actual agreement says it stops. Decide the permitted life of each artifact and the closeout work before delivery begins.
Name the event and the artifact
Expiration, termination for breach and cancellation of a future refresh can have different consequences. A raw archive, a recipient-created annotation layer and a trained model also have different roles. A sentence saying delete the data at termination leaves those combinations unexplained. Build an event-by-artifact schedule that delivery, product and legal teams can use.
The UK Model Services Contract is a public procurement example of deliberately planned exit. Its core terms distinguish surviving provisions, accrued rights and exit management; buyer guidance describes transition work. Those government terms are not defaults for a private dataset license. Their useful lesson is to read the end of the arrangement as an operating event requiring explicit choices.
Keep the commercial exit schedule separate from a privacy-request response. A statutory request, legal retention question or regulator requirement needs its own applicable review. This article concerns the rights and tasks the parties propose to agree for commercial expiration or termination; it does not prescribe a universal deletion period.
Worked example: a one-year snapshot license
In this hypothetical negotiation, package S-8 is a fixed service-event snapshot. The draft permits a defined internal retrieval tool for one year and discusses a separately specified internal model. The parties have not yet agreed whether model use may continue after expiry. There is no ongoing feed, and the owner does not treat a hypothetical surviving right as already granted.
The completed proposed schedule below gives the negotiating team specific positions to accept, reject or amend. Its deadlines and survival choices are fictional commercial terms. They are not legal requirements, and none permits access beyond the agreement that is actually executed.
| Artifact or duty | Proposed ordinary-expiry position | Breach-termination question still to resolve |
|---|---|---|
| Raw snapshot and searchable raw cache | Stop ordinary use; revoke product access and complete agreed return/deletion process | Is a restricted dispute-evidence copy permitted, by whom and for what purpose? |
| Annotations linked to source excerpts | Treat copied source text separately; stop using it with expired raw-access rights | Which original annotations can remain without preserving restricted content? |
| Internal model identified as M-8 | Post-expiry use held pending an express survival decision | Does the specified breach require disabling or replacing M-8? |
| Backup copies | Restrict restoration and use during the agreed purge process; record completion evidence | How is a later restoration prevented from reviving expired access? |
| Accrued invoice and audit record | Retain agreed accounting/evidence workflow without reopening raw product use | What dispute process and record scope continue? |
Turn each row into an accountable closeout task
For the hypothetical raw snapshot, the recipient's product owner identifies three active environments and a search cache. The security owner revokes access in those environments. The data owner reconciles the artifact register to the agreed closeout evidence. The buyer cannot complete this task by deleting a download while leaving the searchable cache in service.
For annotations, the hypothetical inspection finds original fault tags beside copied narrative excerpts. The team separates those components in the closeout proposal and asks counsel to resolve the permitted use of each. Calling the combined file derived does not establish a right to keep the embedded source text.
For backups, identify actual restore paths and responsibilities. A proposed purge interval should explain what is restricted while copies remain, what happens if restoration is required and how completion will be evidenced. A backup's technical lifespan is not automatically a commercial use right. If the process is impractical, resolve that before agreeing to a deadline.
Define survival without granting an accidental product
The unresolved M-8 row is the important hypothetical negotiating decision. The recipient wants to keep running an internal model after expiration. The owner asks for a specific model identifier, permitted purpose, output audience and treatment of source-reproducing behavior. A generic provision allowing all derivatives would be substantially broader than the proposal being examined.
The hypothetical parties decide to leave M-8 use held rather than infer permission from silence. A later agreement could make a different explicit choice. What matters operationally is that the training run, retained artifact and downstream use are all traceable to that choice, including what would happen after the relevant breach event.
Also distinguish money already due from future commercial activity. A surviving invoice-dispute process does not authorize another data delivery. Evidence retained for that dispute should have an identified custodian, purpose and access limit. The closeout schedule should not leave a delivery engineer to guess whether a surviving audit clause means ordinary product access continues.
Rehearse the exit before agreeing to it
In the hypothetical rehearsal, the recipient can close the primary store but cannot identify who owns the search cache. The parties hold the exit schedule until that owner and a feasible removal process are named. They also separate the unresolved model-survival term from the otherwise defined raw-copy closeout. The finished artifact tells both sides what remains undecided.
Use offer comparison to record those term differences and due diligence to verify recipient closeout capability. The refresh-cost guide addresses ongoing delivery work; this schedule addresses the continuing rights and artifacts after a commercial end event. The privacy-request guide handles a separate workflow that may intersect with these artifacts.
VOID can coordinate the discussion after a permissioned introduction, but the owner and recipient make the sample and license decisions. There is no upfront seller referral fee. If the proposed exit cannot be explained to the actual system owners, the license is not ready simply because the commercial amount is agreed.