What this rejection means
If people can create an account in the app, they must be able to start deleting it from inside the app too — not only by emailing you.
Why reviewers send it
Since 2022, any app that lets people create an account must let them start deleting it from inside the app. A support email or a hidden web form doesn’t count, and deactivating the account isn’t deletion.
The message App Review sends
Guideline 5.1.1(v) - Data Collection and Storage
The app supports account creation but does not include an option to initiate account deletion.The exact wording changes from one review to the next; the guideline number is what to look for.
How to fix it
- Add “Delete account” in the settings or profile screen, with a confirmation step.
- Delete the account and its data on your backend, or start that process and say how long it takes. Deactivating isn’t enough.
- If the law makes you keep some records, say so in the flow.
- Upload a new build and tell the reviewer where the button is.
Fix it with Lovable, Bolt or Cursor
If the app was built with an AI builder, paste this into it, then check the result on a phone:
Add a “Delete account” button in the profile or settings screen with a confirmation dialog. It must delete the user’s auth account and all their data on the backend (for Supabase, through an Edge Function using the service role), then sign out.What to reply in App Store Connect
Replace the [brackets] with what you actually changed:
Guideline 5.1.1(v) — Users can now delete their account from [Settings → Account → Delete account]. Deleting removes the account and its data from our servers.Got a different message?
Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.
Other App Store rejections
- App Store Guideline 4.3 Spam rejection
- Guideline 4.2 Minimum Functionality rejection
- Guideline 2.1 App Completeness rejection
- Guideline 2.1 Information Needed: demo account
- Guideline 4.0 Design rejection: sign-in in Safari
- Guideline 2.3.3 Accurate Metadata: screenshots
- Guideline 2.3.10: Android mentioned in the app
- Guideline 2.3.8: app icon or name doesn’t match
- Guideline 4.8 Login Services: Sign in with Apple
- Guideline 5.1.1: permission purpose string
- Guideline 5.1.1: sign-up required to use the app
- Guideline 5.1.1(i): privacy policy link missing
- Guideline 5.1.2: App Tracking Transparency
- Guideline 3.1.1: digital goods without In-App Purchase
- Guideline 3.1.2: subscription information missing
- Guideline 1.5: support URL doesn’t work