Both big stores have rules for apps that let people create an account. Apple's App Review Guideline 5.1.1(v) says that if your app supports account creation, you must offer account deletion within the app. Google Play asks apps with account creation to provide an in-app path to delete the account and associated data, plus a web link where users can request deletion. Policies change, so read the current pages listed in the sources. Privacy laws may add their own rules about what must be deleted; this page does not cover them and is not legal advice, so ask a qualified person.
Deleting an account is a one-way action users take rarely and care about a lot. Test with a throwaway account that has real-looking data: profile, content, a subscription and a connected sign-in method.
The checklist
- The entry point is findable. - Why: hiding it frustrates users and invites support requests. - How to check: find deletion from a fresh start without help. Note the taps and where you looked first.
- The consequences are explained before the final step. - Why: users decide on what they read. - How to check: read the screens. They say what is deleted, that it cannot be undone (or how long a grace period lasts), and what happens to an active subscription.
- Confirmation is deliberate but not hostile. - Why: accidents are costly, so is a maze. - How to check: a tap on the wrong button must not delete. Count the steps; each has a reason.
- Re-authentication where needed. - Why: a stolen unlocked phone should not be able to delete an account. - How to check: if your app asks for password or biometrics, check it works for email, social sign-in and expired sessions, and that errors are clear.
- Cancel at every step. - Why: users change their mind. - How to check: back out at each screen. Nothing is deleted and the account works.
- Subscriptions are handled honestly. - Why: deleting an account does not always cancel a store subscription. - How to check: delete an account with an active test subscription. The app states what the user must still do in the store. See the subscription cancellation checklist.
- Progress and result are shown. - Why: a spinner that ends nowhere is alarming. - How to check: after confirming, a clear success message appears; the user is signed out and lands on a sensible screen.
- Local data is cleared. - Why: cached profile, tokens and files should not remain on the device. - How to check: after deletion, reopen the app: no old name, photo, token or cached content shows. Check the app's local storage if you can.
- Signing in afterwards fails clearly. - Why: a confusing login error after deletion generates support mail. - How to check: try the old credentials. The message does not leak whether other accounts exist and does not suggest the account is still there.
- Registering again with the same email.
- Why: users come back.
- How to check: sign up again with the same address. It works as a new account with no old data, or your stated rule (such as a waiting period) is explained.
- Other devices and sessions.
- Why: a second phone must not keep a live session.
- How to check: stay signed in on device B, delete on device A. B is signed out at the next request and shows a clear message.
- Server side: what is deleted and what remains.
- Why: the promise on screen must match reality.
- How to check: compare the backend with your written list of what is deleted, anonymized or kept and why. Check content other users saw (comments, messages). Confirm what the user was told.
- Confirmation by email, if you send one.
- Why: it is the user's proof.
- How to check: the email arrives, names the account, has no deletion link that works twice and contains no sensitive data.
- Connected services.
- Why: social sign-in and analytics ids can outlive the account.
- How to check: list tokens and ids stored for sign-in providers, notifications and analytics. Each is revoked or covered in your policy.
- Error during deletion.
- Why: a half-deleted account is the worst outcome.
- How to check: cut the network during the request. The app says it failed, the account still works or deletion completes on retry, with no half state.
- Accessibility.
- Why: the destructive button must be clear to everyone.
- How to check: with a screen reader and large text, the warning is read before the final button, and the button is labeled as destructive.
Related
Back to all checklists · Consent and privacy checklist · Notification settings checklist
Hand your deletion flow to a stranger and see where they hesitate. Get started on AppReviewX: private, structured feedback, 1 feedback = 1 credit.