Design account and local-data deletion as a verifiable workflow
Give users a clear deletion scope, confirmation, backup warning, outcome, and recovery boundary.
Name the exact deletion target
Users need to know whether they are deleting one project, local browser data, an online account, support records, or every copy. Avoid a single ambiguous Delete button for different scopes.
Prevent accidental loss
Show the project or account name, explain that the action is irreversible, and offer a backup before deletion. Confirmation should be meaningful without creating a dark pattern that traps the user.
Explain what the operator cannot delete
Browser-local data may be invisible to the operator. Third-party accounts, public issues, legal retention, and backups may follow different processes. State these boundaries before the user acts.
Test cancellation and completion
Verify that cancelling leaves all data unchanged and that completing the operation removes only the selected scope. Reload the application and inspect the result rather than trusting a success message.
Release-ready checklist
- Deletion scope is explicit
- Backup guidance appears first
- Cancellation preserves data
- Completion survives reload
- Third-party and retention limits are explained
This guide is written for planning and verification. Store rules and legal requirements can change; verify official requirements before submission.