Fill in these first
- Product: [e.g. a fitness app with paid plans and shared group challenges]
- Data held about a user: [list: profile, activity history, photos, messages, payment records]
- Linked items: [e.g. active subscription, team workspaces they own, shared posts]
- Records the business must keep after deletion: [e.g. invoices for tax, as advised by the business's own legal team]
- Grace period wanted: [e.g. 14 days to change their mind, or none]
- Export format possible: [e.g. a zip with JSON and photos]
- Where users look for it today: [e.g. profile, settings, help centre]
Task
Design a deletion and export flow that is easy to find, honest about what happens, and hard to trigger by accident.
Output format
- Entry points: where the option appears, no more than two taps from settings.
- Export flow: steps, wait time message, the ready email, and how long the download link works.
- Deletion flow as numbered screens, each with title, body copy and button labels.
- | Data type | Deleted, kept, or anonymised | When | Why |
- Handling of linked items: active subscriptions, owned workspaces, shared content.
- Emails: request received, reminder before the grace period ends, deletion complete.
- A short help centre answer that explains the whole process.
Rules
- No guilt wording, hidden links or extra surveys that block the path; one optional reason question at most.
- The confirmation step names exactly what will be lost, for example "Your 214 workouts and 38 photos will be deleted."
- Never say "all your data is deleted" while some records are kept; state what is kept and why.
- Mark retention periods as [confirm with legal team] unless given.






