Guideline 5.1.1(v)
Does your app need an account deletion option? Apple's rule, explained
Since June 30, 2022, any app that lets a user create an account must also let them initiate deleting it from inside the app. It's one of the most common late-stage rejections because it's easy to overlook until submission.
The rule
If your app supports account creation, it must also support account deletion, and that deletion must be initiated from within the app itself — not only by emailing support or visiting a website.
The one exception: if the account was originally created outside the app (for example, on a website before the app existed), Apple allows directing the user to that same website to complete deletion.
This applies regardless of whether the account is free or tied to a paid subscription.
Deletion, not deactivation
Apple is explicit that this must be actual deletion of the account and its associated personal data, not a 'disable my account' toggle that just blocks login while keeping the data.
You can add a confirmation step or a short cooling-off period before deletion finalizes — the requirement is that the user starts the process in the app, not that it completes instantly.
Common mistakes that trigger this rejection
Deletion is only reachable through a support email or a contact form, with no in-app action.
The app offers 'Deactivate' or 'Log out everywhere' and calls it deletion.
The account was created in-app, but deletion only exists on a website — this only satisfies the guideline if the account originated on the website.
The option technically exists but isn't visible from account or profile settings, so reviewers can't find it.
How to implement it correctly
Add a clearly labeled 'Delete Account' action inside account or profile settings — not nested behind unrelated menus.
Confirm intent with a simple dialog, then actually delete or schedule deletion of the user's personal data.
If you're legally required to retain some data (billing records, fraud prevention), state that plainly in the deletion flow instead of refusing deletion outright — partial retention with disclosure is acceptable, silently ignoring the request is not.
If you already got rejected for this
Reply in Resolution Center confirming the new build number and the exact path to the deletion flow (e.g. 'Settings → Account → Delete Account').
If the reviewer tested an older build, say so and point to what changed — don't assume they'll re-check the whole app.
Next step
Confirm the rest of your account flows are review-safe
Sign in to AcceptMyApp and run a pre-submission check that flags account, login, and privacy issues — including account deletion — before Apple does.
Get startedRelated resources
App Store Guide
App Store Submission Checklist
A practical pre-submission checklist covering metadata, screenshots, privacy, account deletion, and in-app purchases — the things App Review actually checks before approving an iOS app.
Guideline 4.8
Sign in with Apple Rejection: Guideline 4.8 Explained
Rejected for missing Sign in with Apple? Here's when Guideline 4.8 actually applies, the false triggers that catch developers off guard, and how to fix or reply to it.
Guideline 5.1.1
App Store Guideline 5.1.1: Privacy
Understand Guideline 5.1.1 privacy rejections, privacy policies, data collection, permission prompts, and App Privacy declarations.