Data Governance · Retention and deletion · Component
The schedule
How long each data type is kept, and why — derived from obligation and use rather than from storage cost.
The deliverable
What it is
Storage cost stopped being the constraint years ago, which removed the only force that used to cause deletion to happen.
The periods should come from obligation where one exists and from use where none does, and the second is the harder question because the honest answer is often that nobody uses it at all.
One level in
What it is made of
Each element is a constituent part of the component. Follow one to see the attributes it carries.
Data with no schedule is kept indefinitely by default, which is a decision nobody made.
The other components in retention and deletion
The mechanism
What actually performs the deletion, and whether it runs — because a policy executed manually is a policy that is not executed.
LearnThe conflicts
Where retention and deletion obligations collide, and how that was resolved — because leaving it undecided lets whichever system acts first decide.
Learn