Retention & disposal
Regulators set minimum retention, privacy law demands deletion, and litigation freezes everything in between, which makes proving your position on all three genuinely difficult. This applies retention schedules by policy, executes disposal with proof, and freezes whatever a legal hold touches until it is released. Because the platform holds metadata only, disposal runs in your systems and the proof is about your systems.
Retention schedules are derived from record class and sensitivity label and applied across your systems through connectors.
Disposal produces a sealed certificate on the hash-chained ledger: what was deleted, when, and under which schedule.
Deletion is verified, never assumed. A disposal task closes only when evidence confirms the data is gone, and a missing confirmation counts as failure.
Legal holds land through one decision door, freeze disposal everywhere the hold reaches on the graph, and fail closed until released.
Conflicts surface as decisions: when a deletion request collides with a retention minimum or a hold, a human rules on it and the ruling is sealed.
The design is federated: disposal executes in your source systems, and the platform keeps the metadata and the proof, never the data.
Schedule
Retention rules bind to record classes and labels rather than to folders and file shares.
Hold
A legal hold is a sealed decision that freezes disposal across everything its scope touches.
Dispose
Disposal executes in the source system when the schedule expires and no hold applies.
Prove
Evidence of deletion is checked before the task closes, and the certificate seals on the ledger.
“Can you prove we deleted that customer's data?”
Yes. A disposal task closes only when evidence confirms the data is gone, and each completed disposal produces a sealed certificate on the hash-chained ledger showing what was deleted, when, and under which schedule.
“What are we still holding past its retention period?”
Retention schedules are derived from record class and sensitivity label, so anything held beyond its schedule surfaces as an open item rather than sitting unnoticed. Where a legal hold or a retention minimum explains the delay, that ruling is visible and sealed alongside it.
“Is anything under legal hold at risk of being disposed?”
No. A legal hold is a sealed decision that freezes disposal across everything its scope touches on the graph, and it fails closed until it is released.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.