Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple rejected my app because of the tracking permission prompt

Short answer

Apple requires permission before an app tracks users or reads the advertising identifier, and its review guidelines say you cannot gate features on tracking or push users to agree. Open the rejection message, see which of those points it names, and ask your developer to check the app and its third-party tools against them.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The rejection message mentions App Tracking Transparency or tracking.
  • Apple says my app tracks users but I never added a tracking prompt.
  • Apple says my prompt text does not explain why I track.
  • The app was approved before and the same code is now rejected.
  • My developer says the app does not track, and Apple disagrees.

Why does this happen?

  1. A tool inside the app counts as tracking

    Apple defines tracking as linking your app's user or device data with data from other companies for targeted advertising or measurement, or sharing it with data brokers. It says a third-party SDK that combines your data with other developers' data counts, even if you never use it for those purposes.

  2. You are responsible for every SDK in the app

    Apple states that you are responsible for all the code in your app, including third-party SDKs. A rejection can come from an ad or analytics tool added long ago.

  3. The prompt has no clear purpose text

    Apple requires a purpose string explaining why you want to track the user. A prompt without one, or with a vague one, is a common reason for a rejection.

  4. Features are locked behind tracking

    Guideline 5.1.2(i) says you cannot gate app functionality on agreeing to tracking, or give incentives for agreeing. Guideline 5.1.1(iv) says apps must respect permission settings and must not manipulate or force consent.

  5. The app tries to identify the device in other ways

    Apple says apps must not derive device data to uniquely identify a device, and that apps doing this or using SDKs that do may be rejected.

What can I do about it today?

  1. Read the whole rejection messageOpen App Store Connect, go to the rejected version and read what Apple wrote. Note the guideline number it names.
  2. Do not resubmit the same buildThe same build will be rejected again. Wait until the cause is understood.
  3. Send the message to your developerForward it unedited and ask which tools in the app collect device or user data, and whether any of them share it with other companies.
  4. Check your privacy answersAsk for the privacy answers in App Store Connect to be compared with what the app really does.
  5. Reply to Apple only after the fixApple's review team responds to the message in App Store Connect. A reply that says what changed gets further than an argument.

When should I bring someone in?

  • Rejections keep returning and nobody can say what the app shares.
  • Your business depends on ad measurement and you do not know what the tracking rules allow.
  • Your developer is not available and a release is blocked.

How do I handle it?

  1. Match the message to the guidelineI read the rejection against the guideline it cites and Apple's tracking page, and write down what Apple objects to.
  2. List what leaves the appI check each tool and network call to see which data is sent, to whom, and whether it is combined with other companies' data.
  3. Fix the setup, not just the wordingEither the tracking is removed or it is placed behind a proper prompt with a clear purpose. Features never wait on the answer.
  4. Align the privacy answersThe privacy answers in App Store Connect are corrected to match the app.
  5. Reply and resubmitI draft the reply to Apple. The decision belongs to App Review, so I cannot promise an outcome.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does every app need the tracking prompt?

No. Apple requires it before tracking users or accessing the advertising identifier. Whether your app does that depends on what is inside it.

What happens when a user says no?

Apple states that unless permission is granted, the advertising identifier is all zeros and you may not track the user.

Can I make the app stop working if people refuse?

No. Apple guideline 5.1.2(i) says you cannot gate functionality on agreeing to tracking.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.