Demo: designing data deletion across 30 services
On This Lesson 3 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 right-to-erasure that reaches every store; prepares SRA-009-LAB1.
Draft outline details
Step by step
- Build the data inventory: which of the thirty services hold personal data, in primary, derived, cache, search, analytics, and backup stores.
- Choose the pattern: a deletion request event, each owner deletes or anonymizes and confirms, with a coordinator tracking completion.
- Handle exceptions: legal retention of invoices, fraud records, and backups (expire by schedule); confirm rules with legal.
- Define evidence: completion report and audit events, with deadlines.
- Planned mistake: delete only from primary databases. Fix: add derived stores, search indexes, analytics, and backup expiry, and test with a synthetic user.
- Add a fitness function that fails new services lacking a deletion handler.
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.