Summary
Apple rejected the app because ATT behavior, tracking disclosure, or related policy and App Privacy answers do not match.
App Store App Review issue
App Store tracking transparency rejected
Apple rejected the app because ATT behavior, tracking disclosure, or related policy and App Privacy answers do not match.
app store tracking transparency rejectedATT rejected app storeapple app tracking transparency rejection
Fix App Store review issues before the next submission
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
What this means
Reviewers think the app tracks users or accesses device identifiers without the correct ATT prompt flow or disclosure alignment.
The issue often involves SDKs used for attribution, advertising, analytics, or cross-app measurement.
Even when tracking is disabled for some environments, the shipped build still needs defensible disclosure.
Common causes
- The app or an SDK accesses tracking-related identifiers before the ATT prompt.
- App Privacy answers understate tracking, linked data, or third-party measurement behavior.
- The policy does not explain advertising, attribution, or tracking choices clearly enough.
Step-by-step fix
- Step 1
Audit tracking-related SDK behavior and confirm when device identifiers are accessed.
- Step 2
Update ATT prompt timing, App Privacy answers, and policy sections so they reflect the real flow.
- Step 3
If necessary, remove or gate tracking SDKs more aggressively for the release under review.
What to update
- ATT prompt flow
- App Privacy tracking answers
- Privacy Policy tracking section
- SDK configuration
How LogicSpring helps
- Precheck flags common ATT and tracking disclosure mismatches across policy, SDKs, and store metadata.
- LogicSpring helps you regenerate tracking-related policy copy without losing the rest of the privacy document.
- You can use one source of truth for advertising, analytics, and attribution disclosures.
FAQ
Can I resubmit to App Store without changing the binary?
Only if the issue is purely metadata or disclosure copy. If the current build behavior still conflicts with the policy, permissions, or SDK inventory, you usually need a new build.
What evidence should I prepare before resubmitting?
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Should the privacy policy, store form, and in-app disclosure all match?
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.