Q59: How do you design for privacy and data deletion?
Classify personal data, minimize collection, define retention, and enforce access controls and audit trails. Track where data is copied into caches, search indexes, analytics, logs, backups, and downstream services. A deletion workflow should remove or anonymize eligible copies and record completion; backup expiry and legal retention may require separate handling. Avoid putting sensitive personal data into immutable events or logs unless the design supports appropriate redaction or cryptographic erasure.
Key Takeaways
- Map data lineage, not just the primary database.
- Deletion and retention requirements must include derived systems and backups.