Screenata
All SOC 2 Policy Templates
AICPA CC6.5AICPA C1.2AICPA P4.2AICPA A1.2SOC 2ISO 27001GDPRHIPAA

Data Retention Policy Template for SOC 2

Quick Summary

A SOC 2 data retention policy defines how long your company keeps customer data, logs, backups, and HR records, and how you securely delete them when the retention period ends or a customer leaves. Auditors test this policy under AICPA CC6.5, C1.2, and P4.2 by checking actual database lifecycle rules, backup expiration configs, and completed deletion tickets.

Free Markdown Template

Copy or download the data retention policy

Replace bracketed [PLACEHOLDERS] with your actual stack

soc-2-data-retention-policy.mdMarkdown
# Data Retention and Disposal Policy

**Document Owner:** [Security / Engineering Lead]  
**Approved By:** [CEO / CTO]  
**Effective Date:** [YYYY-MM-DD]  
**Review Cadence:** Annual  
**Applies To:** All production data stores, backups, logs, SaaS subprocessors, and employee endpoints

---

## 1. Purpose
This policy defines how long [Company Name] retains business, security, and customer data, and the approved methods for secure disposal once retention periods expire or customer agreements terminate.

## 2. Scope
This policy covers all structured and unstructured data owned or processed by [Company Name], including:
- Customer application data and file uploads
- Automated database snapshots and disaster recovery backups
- Security, access, and application audit logs
- Employee, contractor, and candidate records
- Contracts, invoices, and financial records

## 3. Data Retention Schedule

| Data Category | Primary Systems | Standard Retention Period | Disposal Method |
|---|---|---|---|
| Customer production data | [AWS RDS / Postgres / S3] | Duration of active subscription + [30 / 60] days after written termination | Automated soft-delete followed by cryptographic erasure / hard delete |
| Production database backups | [AWS RDS Snapshots / S3 Glacier] | [30 / 35] days rolling retention | Automated lifecycle expiration policy |
| Security & infrastructure audit logs | [CloudTrail / Datadog / SIEM] | [365] days online (minimum 1 year for SOC 2 Type II lookback) | Automated index / bucket lifecycle expiration |
| Application error & debug logs | [Sentry / CloudWatch] | [30 / 90] days (must not store raw PII or secrets) | Automated log group expiration |
| Employee & contractor HR records | [Gusto / Rippling / HRIS] | Employment duration + [7] years (or statutory minimum) | Secure deletion from HRIS and archive |
| Customer contracts & billing records | [Stripe / Accounting] | [7] years for tax and legal compliance | Archival purge upon legal expiration |

## 4. Customer Offboarding and Deletion Requests
1. Customers may request data deletion in writing via [support@company.com / security@company.com] or upon contract termination.
2. [Company Name] verifies the requester's identity and authorization before executing deletion.
3. Active customer production records are purged within [30] calendar days of verified request, unless a legal hold applies.
4. Residual copies in immutable point-in-time backups expire automatically on the standard [30 / 35]-day backup rotation schedule and are not restored for active processing.
5. Completion of each customer deletion request is logged in [Jira / Linear / Ticketing System] with ticket ID, timestamp, and operator confirmation.

## 5. Secure Disposal of Assets and Media
- **Cloud Storage:** Deletion uses cloud-provider APIs and cryptographic erasure (key destruction or KMS rotation where applicable).
- **Physical Devices:** Company-issued laptops and removable media are encrypted with full-disk encryption (FileVault / BitLocker) and factory-wiped via MDM ([Kandji / Jamf / Intune]) prior to reassignment or certified recycling.

## 6. Legal Holds
When [Company Name] receives notice of litigation, regulatory inquiry, or government investigation, [Legal / Executive Leadership] may issue a written legal hold suspending automated deletion for the scoped records until the hold is formally lifted.

## 7. Policy Compliance and Review
[Security Owner] reviews this policy at least annually and whenever retention schedules, backup configurations, or statutory obligations change. Exceptions require written approval from [CTO / Security Lead].

Evidence Mapping

What auditors test beyond this policy

A signed policy document only satisfies design intent. During SOC 2 fieldwork, your CPA auditor samples operating evidence against each clause below:

Policy RequirementControlEvidence Your Auditor Requests
Automated backup & log retention windowsCC6.5 / A1.2Cloud configuration showing exact S3 lifecycle rules, RDS backup retention days, and CloudTrail/SIEM log retention matching the table in Section 3.
Customer offboarding & deletion SLAC1.2 / P4.2A sample of customer termination or deletion tickets from the Type II period showing request date, verification, and deletion completion within your stated SLA.
Device wipe on employee offboardingCC6.5MDM remote-wipe or device-decommission logs for terminated employees, plus full-disk encryption verification across active endpoints.
Annual policy review & acknowledgmentCC1.1 / CC2.2Dated management approval of the current policy version and employee acknowledgment records.
Common Audit Exceptions to Avoid
  • Copying a 90-day log retention line from a generic template when your SOC 2 Type II observation period is 12 months and auditors need a full year of audit logs.
  • Promising immediate deletion from backups when immutable RDS snapshots actually roll off after 35 days. Always state the backup rotation window explicitly.
  • Listing systems you do not use (or forgetting analytics tools and staging databases that hold copied production data).

Related guide: Why auditors reject generic SOC 2 policy templates

Frequently Asked Questions

Data Retention Policy FAQ

Does SOC 2 require a specific data retention period?
No. SOC 2 does not mandate fixed retention lengths. Instead, your auditor tests whether you define clear retention and disposal rules in your policy and actually enforce those exact periods in your cloud storage, logs, backups, and offboarding tickets.
How long should startups retain security logs for SOC 2?
Most startup auditors expect at least 365 days of security, identity, and cloud audit logs (such as AWS CloudTrail, Okta, and GitHub audit logs) so the logs cover a full 12-month Type II observation period.
What happens if customer data stays in backups after deletion?
Auditors accept backup roll-off periods as long as your policy states the exact backup retention window (commonly 30 to 35 days), backups are encrypted, and you have a procedure to prevent deleted records from reappearing if a backup is restored.

Skip manual fill-in-the-blank edits

Draft this policy directly from your real infrastructure.

Screenata scans your AWS, GCP, GitHub, and identity provider read-only, writes auditor-ready policies tied to real controls, and collects signed evidence automatically.