Data Retention
Data retention defines how long an organization keeps different types of data and what happens when that period expires. It balances legal requirements, business needs, storage costs, and privacy obligations through policies that specify retention periods and disposal methods.
itStorage, backup, and data protection | OpenSkills.info
Intro
Data Retention
Data retention is the controlled keeping and disposal of data over time. It answers a deceptively practical question: When should this data stop existing here?
The answer is rarely one number. A customer invoice, security log, product metric, employee file, and database backup serve different purposes. Different rules may apply. Each copy may also have a different technical path to deletion.
A sound retention program turns those differences into explicit decisions. You identify a data category, explain why it exists, choose a retention trigger and period, define exceptions, and assign an owner. You then implement those decisions across every system that stores a copy.
The result is a retention schedule. The schedule connects governance to system behavior. A policy may say that the organization limits retention. The schedule says which data, for how long, starting from which event, under whose authority, and with what final action.
Why retention exists
Keeping data can preserve evidence, support operations, enable recovery, and satisfy legal or contractual duties. Deleting data can reduce privacy exposure, security impact, discovery burden, and storage cost.
These goals create tension:
- Delete too early, and you may lose records, recovery points, or evidence that you still need.
- Keep too long, and you carry data without a current purpose or authority.
- Apply one period to everything, and you ignore meaningful differences between data categories.
- Delete only the visible copy, and versions, replicas, exports, or backups may remain.
Retention is therefore a risk decision, not a storage cleanup project. It needs input from the data owner, records or legal specialists, privacy staff, security staff, and system operators.
Start with purpose and authority
A retention decision starts with the reason for keeping the data. Common reasons include an active business process, a records requirement, a contract, security monitoring, recovery, or an approved research purpose.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.nist.gov/privacy-framework
Supports
- Privacy risk management across the data life cycle
- Retention and disposal as data processing actions
- Governance as a connection between organizational decisions and system design
- https://csrc.nist.gov/Pubs/sp/800/53/r5/upd1/Final
Supports
- Information management and retention controls
- Audit record retention and media protection controls
- Defined responsibilities, documented actions, monitoring, and verification
- Retention requirements derived from mission, business, legal, policy, and risk needs
- https://csrc.nist.gov/pubs/sp/800/88/r2/final
Supports
- Media sanitization definition
- Sanitization program design based on information sensitivity
- Sanitization and disposal controls for storage media
- https://csrc.nist.gov/pubs/sp/800/188/final
Supports
- De-identification as removal of the association between identifying data and a data subject
- Governance and disclosure-risk considerations for de-identified datasets
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
Supports
- Storage limitation for identifiable personal data
- Accountability for demonstrating compliance
- Erasure, restriction, legal-claim, and protected-archiving considerations
- Safeguards for public-interest archiving, research, and statistical purposes
- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/
Supports
- Retention schedule fields for data categories, purposes, and periods
- Purpose-based justification and regular retention review
- Deletion or anonymization when personal data is no longer needed
- Offline, shared, and backup copies as part of retention scope
- Difference between anonymization and pseudonymization
- Absence of one universal retention period for personal data
- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/right-of-access/how-do-we-find-and-retrieve-the-relevant-information/
Supports
- Defined retention periods for archived and backed-up information
- Continued retrieval obligations for electronically archived or backed-up personal information
- Deletion as permanent discard without intent to access again
- https://www.archives.gov/records-mgmt/scheduling/sch-records
Supports
- Records schedule purpose, scope, descriptions, cutoffs, and disposition instructions
- Inventory and business-process analysis before scheduling
- Temporary destruction and permanent transfer as different dispositions
- Need to update schedules when formats, functions, or scope change
- U.S. federal records requirements as jurisdiction-specific examples
- https://www.uscourts.gov/forms-rules/current-rules-practice-procedure
Supports
- Current official source for U.S. federal procedural rules
- Preservation of electronically stored information as a litigation-specific consideration
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html
Supports
- Lifecycle expiration behavior for current objects
- Delete markers and retained noncurrent versions in versioned buckets
- Separate actions for noncurrent versions and incomplete multipart uploads
- Need to match lifecycle design to storage versioning state
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html
Supports
- Fixed retention periods and legal holds as distinct controls
- Legal hold duration until explicit release
- Write-once protection against overwrite or permanent deletion
- Delete-marker behavior for protected object versions
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html
Supports
- Locked versions blocking lifecycle deletion
- Retention and legal-hold metadata available for inventory
- Interaction among versioning, lifecycle rules, delete markers, and object locks
