Retention and deletion
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design retention and deletion that actually reaches every copy.
Planned topics
- Each data set has a retention period driven by law, finance, and business need (get the periods from legal; do not invent them).
- Deletion must reach primary stores, search indexes, caches, analytics copies, exports, and backups.
- Backups: expire on schedule or use a documented "beyond use" approach agreed with legal; verify with the data protection officer.
- Prefer deleting or anonymizing automatically by a scheduled, logged job.
Draft outline details
Demonstration
a lifecycle table for order data: kept 7 years for finance (verify with legal), personal fields anonymized after that, backups expire after 35 days.
Check your understanding
Where do deletion designs usually fail?
Show answer
Backups and analytics copies that nobody listed.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.