App Store Account Deletion (2026): Requirement & Implementation Guide
If your iOS app lets users create an account, Apple requires you to provide an in-app option to delete that account. This requirement, enforced since 2022, catches many developers off guard because the implementation must meet specific criteria — simply pointing users to a support email is not enough. This article covers what compliant account deletion looks like, the most common rejection reasons, and a step-by-step implementation checklist.
Quick checklist: What counts as account deletion?
| Approach | Compliant? |
|---|---|
| In-app button that deletes account and data | Yes |
| Settings page with "Delete account" option | Yes |
| Email support link only | No |
| Web-only deletion (redirect to website) | Risky — must be clear and accessible |
| Deactivation (not full deletion) | No — must be permanent deletion |
| "Contact us to delete" without a clear path | No |
What the requirement actually covers
Apple's account deletion requirement states that apps offering account creation must also offer account deletion within the app. The deletion must be permanent — not just deactivation. If your app stores user data server-side (which most apps do), the deletion flow must actually remove the user's data from your backend, not just mark the account as inactive.
The requirement applies specifically to apps where users can create accounts. If your app uses anonymous sessions, guest access, or device-only storage with no server-side account, the requirement may not apply. However, if you collect any personal data tied to an identity, you should provide a deletion path.
Implementation checklist
1. Add a "Delete account" option in the app
Place the deletion option in a discoverable location — typically in Settings or Account management. The button should be clearly labeled (e.g., "Delete My Account") and not buried in a sub-menu.
2. Implement confirmation
Show a confirmation dialog explaining what will be deleted and that the action is irreversible. Include a text input where the user types "DELETE" or similar to prevent accidental deletion.
3. Delete data server-side
The deletion flow must call your backend API to permanently remove the user's data. This includes: user profile, authentication tokens, app data, analytics identifiers, and any uploaded content. If you use Sign in with Apple, revoke the user's authorization token.
4. Handle subscription cancellation
If the user has an active subscription, inform them that deleting their account will also cancel their subscription. Do not require them to cancel separately before deleting — the deletion should handle everything.
5. Update your privacy policy
Your privacy policy must describe the account deletion process, what data is deleted, and the timeline for deletion. This aligns with the privacy labels declared in App Store Connect.
6. Provide feedback after deletion
After deletion, show a confirmation screen or email confirming the account was deleted. Log the user out and return them to the login or onboarding screen.
Common rejection mistakes
- Support email only: The most common rejection. Apple wants an in-app deletion flow, not a "contact support" link.
- Deactivation instead of deletion: Marking a user as "inactive" is not deletion. Data must be removed.
- Partial deletion: Deleting the auth record but leaving user content, analytics, or uploaded files in the database.
- Buried in settings: The deletion option is hidden behind multiple menus or obscure labeling.
- Requires web visit: Redirecting users to a website for deletion is risky. Apple may accept it if the web flow is seamless, but an in-app flow is safer.
Before you submit
Account deletion is one of the top rejection reasons for apps with user accounts. Run a free Launch Score check to verify your app has a compliant deletion flow before submitting to App Store review.
Frequently asked questions
Does my app need account deletion?
If your app lets users create accounts, Apple requires an in-app account deletion option. The deletion must be permanent, not just deactivation. Simply providing a support email is not compliant — the deletion flow must be accessible within the app.
Can I just deactivate instead of deleting user data?
No. Apple requires permanent deletion, not deactivation. Marking a user as inactive while keeping their data in your database is not compliant. The deletion flow must remove the user account, profile data, and associated content from your backend.
Does account deletion cancel subscriptions automatically?
Account deletion should handle subscription cancellation. If a user has an active subscription, inform them that deleting their account will cancel the subscription. Do not require them to cancel separately before deleting.