A retention period is active
Data remains preserved until its applicable retention period ends.
EXPIREON™ RETENTION & DISPOSITION
Stop keeping data longer than you have to
Apply different retention treatment to different populations, suspend expiration while a legal hold or another requirement applies, and dispose of eligible data through an approved process, with audit history you can explain years later.
Put your retention schedule to work
The schedule already exists
Most organizations have an approved records schedule. The challenge is applying it to legacy data when the context needed to distinguish what must be retained from what can proceed to disposition is missing.
A default nobody chose
Without the context, the result is a single long retention period applied to everything, or no expiration at all. It is a consequence of Legal Data Lock-In™: data the organization is entitled to delete and cannot safely delete.
Apply the right rule to each population
Expireon™ preserves the context needed to apply the appropriate retention category, duration, and trigger to each population. Information follows the organization’s approved schedule instead of a blanket default.
Govern retention across source systems
Expireon applies the organization’s retention framework consistently across information from different source systems. When a requirement ends, the information can proceed through governed expiration and disposition.
A legal hold stops scheduled expiration
CaseFusion® manages the legal hold; Expireon™ governs the information preserved under it. While a hold remains active, scheduled expiration is suspended. Releasing the hold does not authorize disposition if another retention or governance requirement still applies.
Retention ends while a hold remains
Scheduled expiration stays suspended while the legal hold remains active.
Multiple holds apply
Scheduled expiration remains suspended until every applicable hold has been released.
A hold is released
Releasing one hold removes that restriction. Any other hold, retention period, or governance requirement must also have ended before disposition.
No requirement remains
Eligible data enters the organization’s approved disposition process when no applicable requirement remains.
Retained data should get smaller over time
Retention and disposition decisions get questioned long after the people who made them have moved on, and often after the data itself is gone. Audit history has to survive both.
A system is being retired
Gives the preserved historical population an end date rather than an indefinite new home.
An organization is changing
Applies the acquiring organization's own retention framework to inherited populations.
A platform is changing
Keeps preservation-only populations governed and reducing outside the new production environment.
A person is leaving
Retains departing-attorney and departed-user data for the period the firm's obligations require, and no longer.
Audit history remains after disposition
Retention and disposition decisions may need to be explained after the people who made them have moved on and the data has been disposed of. The audit history must remain available to show what happened and why.
Ingestion and source
The source population, preserved metadata, ingestion activity, and recorded exceptions.
Category and classification
The retention category applied, any AI-assisted classification used to inform it, and later changes to either.
Retention timing
The policy, start date, duration, expected expiration, and any approved change to the schedule.
Preservation and matter context
Preservation dates, the associated matter, and the hold status governing the data. CaseFusion remains the system of record for legal hold.
Administrative changes
User, policy, configuration, access, and override changes that affect governance.
Disposition result
The population disposed of, the date, the outcome, and any exceptions or failures.
What happens before data is deleted
Disposition is a governed outcome rather than a storage event. Every step below produces something the organization can point to later.
-
Identify data whose approved retention period has ended or whose expected expiration date has passed.
- Confirm that no active legal hold or other applicable requirement prevents disposition.
- Apply any required review or approval step.
- Execute deletion against the eligible population, without affecting production systems.
- Record successful disposition and any exceptions.
- Retain the audit history needed to explain the governance path afterward.
Use classification to assign retention categories
Understand the population before assigning retention
Assigning retention treatment to a large historical population requires knowing what is in it. AI Studio classifies email using models trained on the organization's own examples, as one input alongside metadata, source, and review.
Approved policy determines retention
Classification categories are separate from retention categories and do not replace a records schedule. Approved governance policy determines the categories, durations, triggers, and whether anything is disposed of, with human review for exceptions.
Use classification to focus review effort without giving the model authority over the legal decision.
Retention & Disposition FAQs
What is data disposition?
Data disposition is the governed removal of information whose approved retention period has ended, after confirming that no legal hold or other continuing requirement applies, executed through an approved process and recorded so the decision can be explained afterward.
What happens to a legal hold when the retention period ends?
The hold takes precedence. Held data continues to be preserved even though its ordinary retention period has passed, and expiration stays suspended until the hold is released.
Does releasing a legal hold mean the data can be deleted?
No. The population is re-evaluated against its retention category and any other continuing requirement. Regulatory, client, contractual, and records requirements can outlast the hold.
Can AI decide what data to delete?
No. AI-assisted classification informs which retention category a population belongs in. Approved governance policy determines durations, triggers, and whether anything is disposed of, and a ROT classification never authorizes deletion on its own.
What audit history should a disposition leave behind?
Enough to reconstruct the governance path without the data: how the population entered, what category it was assigned and on what basis, when it was due to expire, what holds applied and when they were released, which administrative changes affected it, and what the disposition produced, including exceptions.
Give your data an expiration date
We will walk through how retention categories would map to your governance framework, how holds would interact with your schedules, and what audit history would show about a disposition years later.