Skip to main content
App review, readiness checks, and rejections Level: Intermediate 12 min read

Guideline 5.1.1 Compliance: Implementing In-App Account Deletion

A complete implementation and compliance guide to App Store Review Guideline 5.1.1(v), covering in-app deletion UI, Sign in with Apple token revocation, and App Review notes.

Published: 2026-11-02 • Last Updated: 2026-11-02 • Author: Kip Lawrence
Key MCP Tools: release_readiness_check

Overview: The Guideline 5.1.1 Mandate

Under App Store Review Guideline 5.1.1(v) (Data Collection and Storage), Apple enforces a strict requirement for all iOS, iPadOS, and macOS applications:

"If your app supports account creation, you must also offer account deletion within the app."

Failure to provide a functional, easily discoverable in-app account deletion mechanism is one of the most frequent causes of immediate App Review rejection for newly submitted applications.

For indie developers and AI-assisted "vibe coders," implementing account deletion is often misunderstood. Apple's guideline is not satisfied by merely providing a "Sign Out" button, letting users deactivate their profile, or directing them to email a generic customer support inbox. Apple mandates an end-to-end deletion flow that initiates within the app, informs users about active App Store subscriptions, severs authentication tokens (including Sign in with Apple revocation), and permanently purges user personal data from your backend databases.

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   COMPLIANT ACCOUNT DELETION ARCHITECTURE              │
│                                                                        │
│   IN-APP CLIENT (SwiftUI / Flutter / React Native)                     │
│   Settings ──► Account ──► [ Delete Account Button ]                   │
│                                   │                                    │
│                                   ▼                                    │
│   Confirmation Modal ──► Warns user: "Irreversible Action"             │
│                      ──► Subscriptions Notice: "Manage in iOS Settings"│
│                      ──► Re-authenticates user (Biometrics / Password) │
│                                   │                                    │
│                                   ▼                                    │
│   DEVELOPER BACKEND (API & Database)                                   │
│   POST /api/v1/account/delete ──► Revokes Sign in with Apple Token     │
│                               ──► Purges Personal Data & Auth Identifiers│
│                               ──► Retains ONLY legally mandated records│
│                                                                        │
│   APP STORE CONNECT (FlightDeck MCP)                                   │
│   App Review Information ───────► Provides Demo Credentials & Notes    │
│   Pre-Flight Readiness Check ───► Verifies 0 Review Blockers           │
└────────────────────────────────────────────────────────────────────────┘
Important

Operational Boundary: FlightDeck connects to Apple's App Store Connect REST API. FlightDeck has zero access to your private application databases, user accounts, or auth providers (such as Firebase, Supabase, Auth0, or PostgreSQL). Implementing account deletion requires modifying your app's client-side UI and backend API endpoints. FlightDeck's role is auditing App Store submission readiness, verifying App Review information, and staging review notes explaining your deletion flow to Apple reviewers.


Quick Answer: What Satisfies Guideline 5.1.1?

To satisfy Apple App Review under Guideline 5.1.1:

  1. Initiate Inside the App: Place an explicit "Delete Account" option in your app's settings or user profile screen. It must not require a phone call or support email.
  2. True Data Deletion: The user's account and personal data must be permanently erased. Merely deactivating an account or logging the user out is unacceptable.
  3. Warn About Subscriptions: Inform the user that deleting their app account does not automatically cancel active App Store auto-renewable subscriptions, and provide instructions to manage subscriptions in iOS Settings.
  4. Revoke Sign in with Apple: If using Sign in with Apple, your backend must call Apple's token revocation REST endpoint (POST https://appleid.apple.com/auth/revoke) to invalidate the user's authorization.
  5. Document for App Review: In App Store Connect's App Review Information, provide valid test login credentials and document the exact navigation steps to locate and test the deletion flow.

Copyable Prompts for Your AI Coding Assistant

1. Codebase Account Creation & Auth Audit

Run this prompt in your AI assistant to determine if your application is subject to Guideline 5.1.1 and locate existing account management code:

MARKDOWN
Please audit this codebase for user authentication and account creation:
1. Search our client-side code for user signup, registration, or third-party authentication (Sign in with Apple, Google, email signup, Firebase Auth, Supabase).
2. Determine whether our app creates user accounts. (Note: If the app is local-only with zero account creation, confirm whether Guideline 5.1.1 applies).
3. If account creation exists, search for any existing "Delete Account", "Close Account", or account settings screens.
4. Check our backend routes or API service layers for an account deletion endpoint.
5. Present a gap analysis comparing our current implementation against Apple Guideline 5.1.1(v) requirements.

2. Implement Client-Side Deletion UX & Confirmation Flow

Use this prompt to have your assistant implement the required client-side UI and subscription warnings:

MARKDOWN
We need to implement a fully compliant in-app account deletion flow under Guideline 5.1.1:
1. Add an easily discoverable "Delete Account" button in our settings/profile view (styled with destructive red tint).
2. When tapped, present a confirmation alert explaining that:
   - All personal data, progress, and history will be permanently deleted.
   - Deleting the account does not automatically cancel App Store subscriptions (advise the user to cancel in iOS Settings > Subscriptions).
3. Require the user to re-authenticate or type "DELETE" before sending the request.
4. Call our backend deletion endpoint, clear all local tokens/keychain data upon success, and navigate the user back to the welcome screen.

3. Implement Sign in with Apple Token Revocation (Backend)

If your app uses Sign in with Apple, use this prompt to generate the mandatory server-side token revocation handler:

MARKDOWN
Apple requires revoking Sign in with Apple tokens when a user deletes their account:
1. Provide the backend implementation to call Apple's revocation endpoint: `POST https://appleid.apple.com/auth/revoke`.
2. Generate the required client secret JWT signed with our Apple Developer private key (`.p8`), Key ID, Team ID, and Client ID.
3. Pass the user's refresh token or access token to Apple with `token_type_hint=refresh_token`.
4. Ensure the user's database record and authentication credentials are completely purged upon successful revocation.

4. Prepare App Review Information via FlightDeck

Once the flow is implemented and tested, prepare the App Review submission notes:

MARKDOWN
Please inspect our active App Store Connect draft version using FlightDeck:
1. Check our draft version to ensure all App Review information fields are populated.
2. Draft a clear App Review Note explaining our Guideline 5.1.1 compliance:
   - Provide active demo account credentials (username & password).
   - Document the exact navigation steps: "Open Settings > Tap Profile > Scroll down and tap 'Delete Account' > Tap Confirm".
   - Confirm that the reviewer can test account creation and deletion without encountering errors.

What Account Deletion Is NOT: Common Rejection Traps

Apple reviewers frequently issue Guideline 5.1.1 rejections when developers confuse account deletion with partial account management actions:

Action Satisfies Guideline 5.1.1? Apple Reviewer Rationale
"Sign Out" or "Log Out" NO Signing out merely clears the session token; the user's account and personal data remain stored in your database.
"Deactivate Account" NO Deactivation disables the profile but retains the user's data for future reactivation. Apple requires permanent erasure.
"Email Support to Delete" NO Forcing users to compose an email or open a Zendesk ticket creates friction. The process must initiate directly within the app.
"Delete App / Delete Local Data" NO Deleting the app binary removes local sandbox files but leaves the cloud account intact.
Direct In-App Deletion Flow YES User initiates deletion in-app; confirmation dialog warns user; backend purges personal data and revokes auth tokens.
Direct Web Link (With Conditions) YES Permitted only if the link opens directly to the authenticated deletion page without forcing the user to log in again or navigate through marketing pages.

Managing Subscriptions During Account Deletion

One of the most complex aspects of account deletion is auto-renewable subscriptions:

Because in-app purchases are billed and managed directly by Apple through the user's Apple Account, a third-party developer cannot programmatically cancel an App Store subscription on the user's behalf.

If a user deletes their account while an annual subscription is active, Apple will continue to bill the user unless the user cancels the subscription in iOS Settings.

Mandatory Subscriptions Notice Requirement

Apple requires your deletion confirmation dialog to clearly explain this reality:

TEXT
┌────────────────────────────────────────────────────────┐
│                   Delete Account?                      │
│                                                        │
│ This action is permanent and cannot be undone. All     │
│ your data, saved workouts, and routine history will be │
│ immediately deleted.                                   │
│                                                        │
│ ⚠️ Important Subscription Notice:                      │
│ Deleting your account does not cancel your App Store   │
│ subscription. To avoid future charges, please cancel   │
│ your subscription in iOS Settings > Apple Account.     │
│                                                        │
│ [ Cancel ]                         [ Delete My Account ]│
│                                                        │
│ Manage Subscriptions: https://apps.apple.com/account/subscriptions │
└────────────────────────────────────────────────────────┘

Technical Flow: Sign in with Apple Token Revocation

When an app offering Sign in with Apple deletes an account, Apple mandates that the developer's server notify Apple to invalidate the user's authorization.

MERMAID
sequenceDiagram
    autonumber
    actor User as App User
    participant App as Mobile App
    participant Server as Developer Server
    participant Apple as Apple ID Server (appleid.apple.com)

    User->>App: Taps "Delete Account"
    App->>User: Displays confirmation alert + Subscriptions warning
    User->>App: Confirms deletion
    App->>Server: POST /api/account/delete (with Auth Token)
    Note over Server: Generates client_secret JWT<br/>signed with Apple private key
    Server->>Apple: POST /auth/revoke (client_id, client_secret, token)
    Apple-->>Server: HTTP 200 OK (Apple ID association severed)
    Server->>Server: Purges user row & personal data from database
    Server-->>App: HTTP 200 OK (Deletion confirmed)
    App->>App: Clears local Keychain & cache
    App->>User: Navigates to logged-out welcome screen

Apple Revocation Endpoint Specification

BASH
POST https://appleid.apple.com/auth/revoke
Content-Type: application/x-www-form-urlencoded

client_id=quest.kip.companion&
client_secret=[GENERATED_ES256_JWT]&
token=[USER_REFRESH_TOKEN]&
token_type_hint=refresh_token

Grace Periods and Legitimate Data Retention

Apple's guideline recognizes that real-world legal and financial requirements may delay immediate database eradication:

  1. Immediate Access Revocation: The moment the user confirms deletion, their session must be terminated, their login credentials invalidated, and their profile made inaccessible.
  2. Grace Periods Permitted: You may offer a temporary grace period (e.g., 14 to 30 days) during which the account is queued for deletion, provided the user is explicitly informed.
  3. Legitimate Retention Exceptions: You may retain records strictly necessary to comply with applicable laws (e.g., tax records, financial transaction histories, anti-fraud logs, or medical compliance under HIPAA). However, all marketing identifiers, analytics profiles, and user-generated content must be purged.

App Review Instructions and Demo Credentials

When submitting an app update with account creation, Apple Reviewers must be able to test your flow:

  1. In App Store Connect, open your draft version and scroll to App Review Information.
  2. Sign-In Required: Check the box and provide a functional demo username and password.
  3. Review Notes: Add explicit testing instructions: ```text Guideline 5.1.1 Compliance Notes: Our app supports in-app account creation and account deletion. To test account deletion:
  4. Sign in using the provided demo account credentials.
  5. Navigate to Settings (gear icon in top right) > Account Profile.
  6. Scroll to the bottom and tap "Delete Account".
  7. Confirm the alert dialog. The account will be immediately deleted and return to the login screen. ```
  8. Verify that the demo account is not an administrative account with special deletion restrictions.

Troubleshooting Common Guideline 5.1.1 Rejections

1. "Rejection 5.1.1(v) - Account deletion not found"

  • Cause: The reviewer could not locate the deletion button, or it was buried under obscure nested menus.
  • Fix: Move the "Delete Account" button directly into the primary Account or Settings screen. Document the exact navigation steps in your App Review Notes.

2. "Deletion requires contacting customer support"

  • Cause: Your app displays a message saying "Please email support@example.com to delete your account."
  • Fix: Replace the email link with an automated in-app button or an authenticated direct web view.

3. "Sign in with Apple tokens not revoked"

  • Cause: The app purges local data but fails to call Apple's /auth/revoke endpoint.
  • Fix: Implement server-side token revocation and verify that Apple returns HTTP 200 during testing.

Security & Privacy Safeguards

  • Re-Authentication Gate: Destructive account deletion should always require re-authentication (biometrics or password re-entry) to prevent unauthorized deletion from unlocked devices.
  • Fail-Closed Session Cleansing: All local authentication tokens, OAuth credentials, and cached personal records must be wiped from the device's secure enclave and Keychain.
  • Zero Third-Party Storage: FlightDeck MCP never processes, collects, or stores end-user credentials or personal data.

Official Apple Documentation

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store