Data Governance · Retention and deletion · Component
The conflicts
Where retention and deletion obligations collide, and how that was resolved — because leaving it undecided lets whichever system acts first decide.
The deliverable
What it is
One rule requires keeping records for seven years; another requires deleting personal data when it is no longer needed. Both apply to the same record.
The resolution is usually a legitimate one — the retention obligation prevails, with access restricted — and it has to be decided rather than left to whichever process runs.
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.
The conflict
Which obligations collide.
3 attributes: Retention obligation · Deletion obligation · Data affected
LearnThe holds
Data that must not be deleted for a specific reason.
3 attributes: Hold reason · Data covered · Enforced in mechanism
Learn
A legal hold the deletion job does not know about is a hold that will be breached on schedule.
The other components in retention and deletion
The schedule
How long each data type is kept, and why — derived from obligation and use rather than from storage cost.
LearnThe mechanism
What actually performs the deletion, and whether it runs — because a policy executed manually is a policy that is not executed.
Learn