Definition
A data retention schedule documents how long each type of data is kept before deletion. It limits liability and satisfies privacy expectations.
Automating deletion where possible turns policy into practice.
A retention schedule limits liability and satisfies privacy expectations by defining how long data is kept. Automating deletion turns policy into practice. Reviewing periods as laws and practices change keeps it current.
Building a Schedule
Set clear retention periods per data type.
Automate deletion where possible.
Why It Matters
A retention schedule limits liability and satisfies privacy expectations. Understanding it prevents the risk of holding data too long.
Best Practices
- Set clear retention periods per data type.
- Automate deletion where possible.
- Document the schedule and its rationale.
- Review periods when laws or practices change.
- Ensure deletion is verifiable.
Was this useful?
Related Glossary Terms
Anonymized Data
Anonymized data is email subscriber or interaction data that has been stripped of personally identifiable information so individuals cannot be re-identified.
Consent Banner
A consent banner is an on-site notice that informs visitors about data collection and allows them to agree to or manage email marketing preferences.
Cookieless Tracking in Email
Cookieless tracking in email is the measurement of email-driven behavior using methods that do not rely on third-party browser cookies.
Email Account Health Score
A composite metric that evaluates the overall health of an email sending programme based on deliverability, engagement, list quality, and compliance factors.
AI Email Privacy
AI email privacy covers how AI assistants process email data, raising questions about data use, retention, and consent.
Email Anti-Spam Laws
Overview of global anti-spam regulations including CAN-SPAM, CASL, GDPR, the Australian Spam Act, and POPIA with compliance requirements for each jurisdiction.
Frequently Asked Questions
A policy specifying how long each type of data is kept. A retention schedule limits liability and satisfies privacy expectations by defining how long data is kept.
To limit liability and meet privacy expectations. Automating deletion turns policy into practice.
Based on legal, business, and purpose needs. Reviewing periods as laws and practices change keeps it current.
Data should be securely deleted. A retention schedule limits liability and satisfies privacy expectations by defining how long data is kept.
Automate deletion where possible. Automating deletion turns policy into practice.