App rejected: no way to delete an account
If the app creates an account, Apple expects the app to delete it too. Sending people to an email address or a web form is what gets flagged.
What the rejection means
If the app creates an account, Apple expects the app to delete it too. Sending people to an email address or a web form is what gets flagged.
The usual causes
- Deletion is offered only by writing to support.
- The route exists but is buried three levels deep in settings.
- The app deactivates rather than deletes, without saying so.
What to change
Add a deletion route inside the app, say plainly what it removes and what survives, and publish a page describing the same thing for Google Play.
Before you resubmit
- Open every URL you entered in a private window.
- Read the reviewer's message again and answer the specific point, not the general topic.
- Reply in Resolution Center saying what you changed and where to see it.
Keeping it true after launch
A legal page stops being true the moment the product moves past it, usually by adding a payment provider, an analytics SDK or a sign-in. No store re-checks your pages against your build, so the drift is yours to notice.
- Re-read it whenever you add a dependency that sees user data.
- Re-check what loads on the page after any change: the cookie notice and the policy have to agree.
- Keep the URL stable. Changing where a policy lives breaks every listing that points at it.
Common questions
How long does a resubmission take?
Usually the same as a first review. Answering the exact point raised, with a link, is what shortens it.
Can I argue a rejection?
You can, and sometimes you should. It works when the reviewer has misread something and you can show it in one sentence with a link. It rarely works as a general objection.
