App Store Guideline 5.1.1 Checklist: Meeting Account Deletion Rules

Apple's App Store Guideline 5.1.1 mandates an in-app account deletion option for apps that allow account creation. This post provides a practical compliance checklist for meeting App Store Guideline 5.1.1 account deletion requirements, detailing exact UI placement, identity revocation rules for services like Sign in with Apple, and data-purging timelines required to pass App Store review.

Guideline 5.1.1(v) states: If your app supports account creation, it must also support account deletion from within the app. This isn't just about removing a user's record from your database; it's about providing a clear, accessible, and functional path for users to manage their data privacy directly within your app.

Providing an In-App Account Deletion Option

Apple requires that users can initiate account deletion directly from within your app. This means no forcing users to visit a website, send an email, or call customer support to delete their account. The option should be easily discoverable and not buried deep in obscure menus.

Place the account deletion option within a dedicated account management section. This typically means finding it under "Settings," "Profile," or a similar "Manage Account" pathway. For instance, in a social networking app, users might access Profile > Privacy Settings > Delete Account. In a utility app, it could be under Settings > Account > Delete My Account. The goal is to ensure the option is discoverable within a few taps from the app's main interface, not hidden in an obscure submenu or requiring extensive navigation.

The deletion option must be unconditional. While you can include warnings about data loss, you cannot require users to contact support, visit a website, or send an email to complete the deletion. The entire process, from initiation to confirmation, needs to happen inside your app.

Managing Identity Revocation for Third-Party Sign-ins

If your app integrates with third-party sign-in services like Sign in with Apple, Google Sign-in, or Facebook Login, simply deleting the user's data from your database isn't enough. You must also revoke the user's token or authorization with that third-party service. This ensures that their identity is truly disassociated from your app.

For Sign in with Apple, your app's backend must make a server-to-server call to Apple's API to revoke the user's authorization when an account is deleted. This action tells Apple that your app no longer has permission to access the user's information, even if it was anonymized via Private Relay Email. If you fail to do this, your app will likely be rejected.

Ensure your backend code handles this programmatic revocation. For Sign in with Apple, this involves a server-to-server API call to Apple's authentication servers to invalidate the user's refresh token. For other providers, consult their specific SDKs and documentation for token revocation APIs. This step is a common oversight that leads to rejections.

Data Purging Timelines and Legal Compliance

Once an account deletion request is initiated, all associated user data must be purged from your servers. This includes personal identifiable information (PII) such as names, email addresses, user IDs, and any stored payment details. Apple expects this data removal to occur "expeditiously," although no specific timeframe in days is provided by the guidelines.

Inform users clearly what data will be deleted and if any data must be retained for legal or regulatory purposes. For instance, apps handling financial transactions or medical records often face specific legal obligations to retain certain data for a defined period. In such cases, these records should be anonymized or pseudonymized to remove direct links to the user whenever possible, and users must be explicitly informed of this retention in your app's privacy policy before they proceed with deletion.

When you generate your App Privacy Label, consider how your data retention policies align with deletion. Your privacy policy, linked in App Store Connect, should clearly outline the data deletion process, what data is purged, and any exceptions. This helps prevent review rejections based on unclear privacy practices.

App Store Guideline 5.1.1 Account Deletion Checklist

Use this checklist to ensure your app meets Apple's requirements for account deletion before your next submission:

1. In-App Deletion Path: Is there a clear, easily discoverable option to delete an account within the app? (e.g., Settings > Account > Delete Account).
2. Unconditional Deletion: Can users complete the entire deletion process without leaving the app, contacting support, or visiting a website?
3. Confirmation Step: Does the app include a clear confirmation dialog (e.g., "Are you sure you want to delete your account? This action cannot be undone.") to prevent accidental deletions?
4. Third-Party Sign-in Revocation: If using Sign in with Apple or other third-party services, does your backend programmatically revoke the user's authorization with that service upon deletion?
5. Data Purging: Does your system delete all associated user data, especially PII, expeditiously?
6. User-Generated Content (UGC): Is all UGC associated with the account also deleted or anonymized?
7. Privacy Policy Update: Does your privacy policy clearly describe the account deletion process, data retention policies, and any legal exceptions? Ensure your policy is current and accessible via a direct link in App Store Connect. You can use a Privacy Policy Generator to help with this.
8. Test Account Deletion: Have you thoroughly tested the account deletion flow with your App Store Review demo account to ensure it works as expected?
9. Customer Service Path (Optional but Recommended): Do you still offer a way for users to contact support for assistance with account deletion, even if it's not the primary method?

FAQ

Does Guideline 5.1.1 apply to all apps?

Guideline 5.1.1(v) specifically applies to apps that allow users to create an account from within the app. If your app does not support account creation or user data storage, this particular requirement typically does not apply.

What if my app doesn't store user data?

If your app doesn't store any user data on your servers (e.g., it's a completely local, offline utility), then you likely don't need to implement account deletion. Apple's concern is with apps that collect and store user data, especially PII, and how users can control that data.

Can I offer account deactivation instead of deletion?

No, Apple explicitly requires account "deletion," not just deactivation. While deactivation might be an option you offer *in addition* to deletion, it cannot replace the full deletion requirement. Deletion implies the permanent removal of user data, with limited exceptions for legal or regulatory reasons.

What's the fastest way to get rejected on 5.1.1?

The fastest way to get rejected is to either completely omit an in-app account deletion option or to require users to contact support, visit an external website, or send an email to complete the deletion. Also, failing to revoke third-party sign-in tokens (like Sign in with Apple) is a frequent cause of rejection.

How long does Apple give me to fix a 5.1.1 rejection?

Apple typically gives you a timeframe to address the rejection and resubmit your app. There is no fixed timeframe. Communication with the App Review team via App Store Connect is key if you need more time or clarification.

Review Your Deletion Flow

Take this checklist and audit your app's existing account deletion process. If you don't have one, it's time to build it into your next update. Ensuring compliance with Guideline 5.1.1 helps you pass App Store review.