# Guideline 5.1.1(v): account deletion required > Rejected under Guideline 5.1.1(v) because users can’t delete their account in the app? What the delete flow needs, and a reply for App Review. **Guideline 5.1.1(v) — Account deletion: let people delete their account in the app.** 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. - App Store · Guideline 5.1.1(v). Account deletion: let people delete their account in the app. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## 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 1. Add “Delete account” in the settings or profile screen, with a confirmation step. 2. Delete the account and its data on your backend, or start that process and say how long it takes. Deactivating isn’t enough. 3. If the law makes you keep some records, say so in the flow. 4. 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](https://capwr.app/free-tools/app-store-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](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)