How to fix it
- Decide whether you really track. If not, remove tracking SDK features and update privacy labels.
- If you do, add NSUserTrackingUsageDescription and call requestTrackingAuthorization before any tracking.
- Make sure SDKs respect the result.
- Never reward or punish the choice.
- Tell the reviewer where the prompt appears.
App tracking transparency rejection: key rules and context
What the rejection means. Guideline 5.1.2 covers data use and sharing. Apple's App Tracking Transparency framework is how you ask permission to track.
Why it usually happens
- Ad or attribution SDKs collecting the IDFA or fingerprinting before consent.
- App Privacy details say "Data Used to Track You" but no prompt appears.
- The prompt appears, but the app blocks features if the user declines.
- A pre-prompt screen that pressures users.
What to tell the reviewer. Explain when the prompt shows (for example, after onboarding screen 2) and how to trigger it on a fresh install.
How to avoid it next time. Audit every new SDK's privacy manifest and data practices before adding it.
Worked example (hypothetical)
This example is illustrative. The app is made up, and so are any numbers in it.
Imagine ArcadeDash shows the ATT prompt and blocks play if the user declines. We'd remove the block, show a short pre-prompt explaining personalised ads, and configure the ads SDK to serve non-personalised ads when declined.
Common mistakes
- Blocking features on decline. Not allowed.
- Tracking before the prompt. Initialize SDKs after the choice.
- Privacy labels that say no tracking. They must match reality.
- Misleading pre-prompts. Be plain.
If you want this handled for you, our pricing page lists every fixed package.
How to fix a 5.1.2 rejection, step by step
Follow these steps in order. Each one is something we do on client work.
- Audit tracking. List SDKs that link data with other companies' data for ads or share it with data brokers.
- Add App Tracking Transparency where needed. Apple's guidelines require permission via the ATT APIs to track.
- Don't gate features on consent. Apps may not require users to enable tracking to use the app.
- Match the privacy labels. App privacy answers in App Store Connect must match what the app does.
- Configure SDKs. Turn off identifiers when consent is denied.
- Reply with the flow. Show when the prompt appears.
The guidelines behind most rejections
The table maps each point to the app tracking transparency rejection context. Compare the guideline number in your rejection message with the matching row. If your message cites a number not listed here, read that section of the guidelines in full.
| Guideline | What it covers | Usual fix |
|---|---|---|
| 2.1 App Completeness | Final builds, working URLs, no placeholder content | Fix crashes, add a demo account, test every link |
| 2.3 Accurate Metadata | Description, screenshots and previews reflect the app | Re-shoot screenshots from the real app; remove claims you can't show |
| 2.3.7 | Unique name, accurate keywords, no trademarked or irrelevant terms | Remove competitor names and pricing from metadata |
| 3.1.1 In-App Purchase | Digital features and content unlocked via IAP | Move digital unlocks to StoreKit IAP |
| 4.2 Minimum Functionality | More than a repackaged website | Add native, useful features |
| 4.3 Spam | No duplicate bundle IDs or saturated copycat apps | Consolidate apps; show what is unique |
| 5.1.1 Data Collection and Storage | Privacy policy, permissions, account deletion (5.1.1(v)) | Add policy links, clear purpose strings, in-app deletion |
Checklist
Copy this list into your release notes or ticket and tick each item off before you ship.
- Tracking SDKs listed
- ATT prompt before tracking
- App works when declined
- Privacy labels match
- SDKs respect choice
- Reply explains flow
Sources
- Apple: App Review Guidelines (accessed 26 October 2026)
- Apple: Privacy manifest files (accessed 26 October 2026)
- Apple: Ratings, reviews and responses (accessed 26 October 2026)
Questions
What counts as tracking?
Linking data from your app with other companies' data for ads or sharing with data brokers.
Is ATT needed if I only use analytics?
Not if the data isn't used for tracking as Apple defines it.
Can I show a screen before the prompt?
Yes, if it doesn't mislead or pressure.
Does SKAdNetwork need ATT?
No; SKAdNetwork is Apple's privacy-preserving attribution.
Can you fix it?
Yes, in 1–2 business days.
Do I need ATT if I only use first-party analytics?
Apple's definition of tracking involves linking data with other companies' data or sharing with data brokers. Check Apple's tracking definition for your SDKs.