Guideline 5.1.2
Guideline 5.1.2(i) - Privacy: Gating Functionality Based on System Permissions
Our Take
Apple is rejecting your app because it gates or limits access to content or functionality on the condition that the user enables tracking or allows push notifications. Under guideline 5.1.2(i), apps may not require users to permit tracking (via ATT) as a condition of using the app, and similarly may not gate features behind push notification opt-in. This rejection typically appears when an app shows the ATT prompt and then blocks or degrades the experience for users who decline tracking. Examples include: disabling core features for users who deny tracking, showing a dismissal-proof screen urging users to go to Settings and enable tracking, or requiring push notification permission before allowing app access. Apple treats this as a dark pattern. The ATT prompt must be truly optional — users who deny tracking must get the same core experience as those who allow it. You can show a pre-prompt screen explaining the benefits of allowing tracking (a common tactic), but after the user makes their choice, the app must function fully regardless.
Resolution Guide
**Remove tracking gates** — Ensure all core features work identically whether the user allows or denies tracking. No feature should be locked behind ATT authorization.
**Remove notification gates** — If your app requires push notification permission before proceeding, make it optional. Add a 'Skip' or 'Not Now' button.
**Don't re-prompt after denial** — Once a user declines ATT, do not show additional screens asking them to go to Settings to enable tracking. One pre-prompt explanation is acceptable; nagging is not.
**Use contextual alternatives** — If tracking is denied, switch to contextual advertising or remove ads rather than degrading the experience. If notifications are declined, use in-app notifications or badges.
**Test the declined path** — Walk through the entire app with tracking denied and notifications declined. Every feature that works with permissions granted must also work without them.
Prevention
Example Rejection Email
Before & After
After user denies ATT prompt, app shows a full-screen dialog saying 'To use this app, please enable tracking in Settings > Privacy' with no dismiss option
After user denies ATT prompt, app proceeds normally with contextual ads; all features remain accessible; a small optional banner offers to explain ad personalization benefits
What changed: Tracking and notification permissions must be truly optional. Users who decline must get the same core experience.
Community Solutions · 0
Sign in to share your solution.
More Guideline 5 (Legal) rejections
- Guideline 5 - Legal: Remove Watermark Feature
- Guideline 5.1.1 - Data Collection and Storage: Incomplete Privacy Manifest
- Guideline 5.1.1 - Data Collection and Storage: Missing Purpose Strings
- Guideline 5.1.1 - Data Collection and Storage: Privacy Manifest Missing
- Guideline 5.1.1 - Data Collection and Storage: Privacy Nutrition Label Mismatch
- Guideline 5.1.1 - Data Collection and Storage: Privacy Policy