Data Governance · Retention and deletion · Component
The mechanism
What actually performs the deletion, and whether it runs — because a policy executed manually is a policy that is not executed.
The deliverable
What it is
A retention policy with no automated mechanism is a document. Deletion requires someone to do something on a schedule, and it is always the thing that is postponed.
The harder problem is copies: backups, exports, analytical extracts and the spreadsheet someone downloaded. Deletion from the primary system is not deletion.
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 copies
Where else the data exists.
3 attributes: Copy location · Covered by deletion · Treatment
LearnThe verification
Evidence that the deletion happened.
3 attributes: Log · Last verified · Records deleted
Learn
Deletion from the primary system is not deletion. Backups, extracts and local copies survive it.
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 conflicts
Where retention and deletion obligations collide, and how that was resolved — because leaving it undecided lets whichever system acts first decide.
Learn