How to go serverless in a post-GDPR world
summary
Shows concrete patterns: periodic Cloud Functions run as cron jobs to Friendly Pix deletes data after 30 days, account-deletion triggers that read a UserPrivacy.JSON and remove Firestore/RTDB/Storage paths, and an HTTP-triggered Export Data function that writes per-UID JSON to Cloud Storage guarded by Security Rules Emulator for CI and simulator-tested rules. Includes admin SDK APIs to delete Firebase Instance IDs, an activity-log pattern that appends privacy changes via functions, and links to retention terms and a Google Cloud whitepaper explaining backend deletion behavior.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:42General Data Protection Regulations
- 1:45Key Steps
- 9:08General-Purpose Account Deletion Function
- 10:46Data Portability
- 11:01Export Data
- 12:03Firebase Security Rules
- 13:31Data Security
- 15:08Security Rules Simulator
- 16:47Data Retention
- 17:50Instance Ids Firebase
related talks
21mServerless security modeling in Firebase
49mGet silly with serverless
39mdev.privacy: GDPR in a nutshell
51mServerless with Firebase in the wild
35mGoogle Cloud Functions and Firebase
58mEasy, scalable serverless backend for mobile/web app
35mConvergence of Serverless APIs & Compute
34mAdd Serverless Functionality to Android Apps with Firebase
