How to Fix App Store Account Deletion Rejection

Implement an in-app account-deletion path, remove unnecessary friction, and explain legitimate retention after an Apple account-deletion rejection.

What this rejection usually means

If an app supports account creation, Apple generally expects users to be able to initiate deletion from inside the app. Deactivation, logout, a support-only email, or a hidden web process may not satisfy the requirement.

Likely rejection signals

• Users can create accounts but cannot start deletion in the app
• The only deletion route is contacting support
• The flow merely deactivates or freezes the account
• Retention and deletion timing are not explained

Recovery plan

1. Add a clearly labeled deletion action in an intuitive account or privacy location.
2. Require only proportionate confirmation needed to prevent accidental or fraudulent deletion.
3. Delete associated personal data unless a legitimate retention obligation applies.
4. Explain retained categories, reason, and duration in the privacy policy and confirmation flow.
5. Test the path with a production-like account and provide exact reviewer navigation.

Evidence to prepare

• Screen recording of account creation through deletion
• Backend confirmation that associated data is removed
• Updated privacy-policy retention section
• Reviewer test account and navigation steps

Appeal or fix first?

Reviewer response framework

Your response should be factual, short, and limited to the submitted build. Cover these points:

1. State where deletion is initiated in the app.
2. Describe confirmation and processing time.
3. Explain any legally required retention.
4. Provide a test path that does not use a real customer's account.

Frequently asked questions

Source: Apple App Review Guidelines — 5.1.1(v). Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.