How to respect users' data erasure requests with FlutterFire
summary
Prototype claims: a working Android app built in about five weeks that lets a user request full data erasure and actually removes Firestore records. Implementation uses Flutter + Firebase, FlutterFire auth libraries, two Firestore collections (users and reports), Firebase Cloud Storage for blobs and the Delete User extension (cloud functions packaged) configured in recursive mode. Demo shows the collection disappearing; extensions are beta and require the Blaze pay‑as‑you‑go plan so monitor function logs and billing.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:06Home ownership
- 2:20Unplanned cost
- 4:47Agenda
- 8:05Why we need to respect users
- 8:15What are you collecting
- 9:25Choice and control
- 15:06What is PII
- 16:12Why respect user requests
- 16:52Title
- 17:28Not a functional requirement
- 18:18Understand your risk
- 18:48My experience
- 19:49My configuration
- 21:01CLI installation
- 21:24Demo
- 26:21Firebase Extensions
- 27:25Welcome
- 28:55Overview
- 29:19Code
- 32:17Serverless
- 34:07Monitoring
- 35:50Summary
- 37:29Why does this matter
- 40:27Conclusion
- 41:11Slack
