Skip to content
Get a quote

App Store rejectionGuideline 5.1.1 - Legal - Privacy - Data Collection and Storage

App Review found a problem with how the app asks for, explains or lets people remove their data. The rejection names the sub-section, such as (i), (ii), (iv) or (v). Here’s what each common one means in Apple’s words and how to fix it, or hand it over at a fixed price.

Short answer

The most common 5.1.1 rejections: no way to delete an account inside the app (5.1.1(v)), purpose strings that don’t explain why the app needs a permission (5.1.1(ii)), a missing privacy policy link (5.1.1(i)), or a permission demanded before the user can do something unrelated (5.1.1(iv)). Each is a fixable change in the app or its listing.

The usual sub-sections, and the fix

  1. 01

    (v) No account deletion in the app

    “If your app supports account creation, you must also offer account deletion within the app.” Apple, Guideline 5.1.1(v)

    If people can create an account, they must be able to start deleting it from inside the app, not only by email or on a website. Add a Delete account option where users would look for it, usually in settings, that starts permanent deletion of the account and its data on your server, not just deactivation. Show it in a screen recording in your reply.

  2. 02

    (ii) Purpose strings that don’t explain the use

    “Ensure your purpose strings clearly and completely describe your use of the data.” Apple, Guideline 5.1.1(ii)

    Each permission prompt shows the purpose string from your Info.plist. "This app needs your camera" isn’t enough; say what the feature does with it, such as scanning a receipt. Make every string accurate for what this app actually does.

  3. 03

    (i) The privacy policy link is missing

    “All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner.” Apple, Guideline 5.1.1(i)

    Add the privacy policy URL in App Store Connect and a link inside the app, for example in settings or on the sign-up screen. Check the policy says what data the app collects, how it’s used and how users can ask for it to be deleted.

  4. 04

    (iv) A permission forced before it’s needed

    “Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access.” Apple, Guideline 5.1.1(iv)

    Ask for a permission when the user reaches the feature that needs it, and let the rest of the app work if they say no. If someone declines location, for example, let them type an address instead.

Checked against the vendor’s docs on : Apple: App Review Guidelines, 5.1.1 Data Collection and Storage (last updated October 16, 2026); Apple: App Review (replying and appeals); Apple Developer Forums: Guideline 5.1.1 rejection threads.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: ITMS-90683: missing purpose string · App Store Guideline 2.1

Questions

More on this rejection

Should I reply to App Review or appeal?

Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.

Is a "contact us to delete your account" email enough?

Not for 5.1.1(v): Apple asks for account deletion within the app. A support email can be part of the process behind it, but the user has to be able to start the deletion inside the app.

My upload got an ITMS-90683 email. Is that the same thing?

Related, but earlier. ITMS-90683 arrives when you upload a build whose code uses a protected API with no purpose string at all. A 5.1.1(ii) rejection comes from App Review, which can cite purpose strings it finds unclear, among other consent problems. The ITMS-90683 guide covers the first.

Can you fix it for me?

Yes, through the App Fix Ticket: you send the rejection message and access to the app, Simon writes a diagnosis of what App Review hit and how to fix it, then fixes the code so you can resubmit. Each step has a fixed price, paid upfront. Approval stays Apple’s decision; the ticket covers the fix.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes