6 tips to follow in a post-GDPR world
summary
Six concrete practices: minimize stored fields and keep only derived flags rather than full birthdays, run scheduled deletions for stale data such as old highscore histories, call the delete API on Firebase Auth and trigger a Cloud Function cleanup, or use the published account deletion function and export data Cloud Function for portability. Test and enforce rules with security rules simulators and the local security rules emulators added to CI, and remember backups and caches mean deletions may persist briefly.
AI-written summary · about
chapters (8)
- 0:00Not giving legal advice
- 0:17Reduce the data you store
- 0:48Remove data you no longer need
- 1:19Implement user account deletion
- 1:58Keep user data portability in mind
- 2:27Configure security rules correctly
- 3:28Take into account
- 3:52Storing Privacy Settings with Firebase
related talks
01h 00mPrivacy and GDPR: What all developers should know
39mdev.privacy: GDPR in a nutshell
35mReasons to (Not) Use Firebase
50mPrivacy by design
46mDeveloping for Privacy
19mData etiquette in a regulated world
48mGDPR Design for Websites, Apps and (Ro)Bots
40mGDPR in practise - Developing models with transparency and privacy in mind