Guideline 5.1.1(v) is short: "If your app supports account creation, you must also offer account deletion within the app." Apple's support page on the topic adds the details that decide whether you pass review. This is a summary of them.
Who it applies to
Any app where people can create an account, including accounts created automatically for a guest. If your app has no accounts at all, the rule doesn't apply. But your privacy policy should still explain how people can ask you to delete their data.
What counts as deletion
- Delete the entire account record and the associated personal data. Data you are legally required to keep can stay, but tell people what you keep.
- Deactivating or disabling the account is not enough if it is the only option. You may offer it in addition to deletion.
- User-generated content connected to the account should be deleted too, including content shared with others, unless a law requires you to keep it.
Where the option must be
- Inside the app, easy to find. Account settings is the usual place.
- A website is acceptable for finishing the process, as long as the app links directly to the page where people complete it. A link to your homepage isn't enough.
- No phone calls, emails or support chats as the required path, unless your app is in a highly regulated industry (for example banking or healthcare).
Confirmation and timing
- You may ask people to confirm their identity (for example with a code sent to their email) and to confirm that they really want to delete.
- Deletion doesn't have to be instant. Tell people how long it will take, and confirm when it is done.
- Making deletion "unnecessarily difficult" will not pass review.
Subscriptions and purchases
- If people have an auto-renewing subscription, tell them that billing continues through Apple and that they should cancel it. Point them to their subscription settings.
- Explain how refunds and existing purchases are handled.
Sign in with Apple
If your app supports Sign in with Apple, revoke the user's tokens with the Sign in with Apple REST API when the account is deleted.
A minimal implementation that passes review
- Add Delete account to your account or settings screen.
- Show a confirmation screen that explains what is deleted, what is kept, and what happens to subscriptions.
- Delete the data on your server (or start a job and say how long it takes), revoke Sign in with Apple tokens, and sign the user out.
- Mention the deletion process in your privacy policy, and put a test account in your review notes so the reviewer can try it.
How AppSubmitKit helps
AppSubmitKit's privacy questionnaire asks whether your app has accounts and how deletion works, and includes that answer in your hosted privacy policy. It cannot add the button to your app. That part is yours.
Related: Guideline 5.1.1 and your privacy policy and the App Store review checklist.