Data retention is crucial for compliance with legal requirements and for managing data throughout its lifecycle. It involves policies for storing, backing up, and deleting data to ensure legal compliance and access to historical information.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Data retention defines how long data is stored and protected, and when it is deleted or anonymized.
The approach grew from records management, archives, and statutory record-keeping. Privacy law, especially the GDPR storage-limitation principle, connected that tradition with keeping personal data only as long as necessary.
A retention period is a three-stage schedule: use data actively, archive it with protection, then delete or anonymize it in a controlled way.
A defined period during which data is kept.
Protected storage for data with evidentiary or reference value.
Traceable removal or rendering of data unreadable.
Clear periods reduce privacy, operational, and storage risks. Legal duties may require different periods, so each data type needs a justified rule.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.