Guideline 5.1.2

Guideline 5.1.2(i) - Privacy: Gating Functionality Based on System Permissions

High RiskMedium DifficultyTypical Fix: 2-8 hours0 Reports
Also known as:App requires users to allow tracking to access featuresCore functionality degraded for users who decline ATTApp repeatedly prompts users to enable tracking after declineFeatures gated behind push notification permissionApp conditions content access on enabling tracking or notifications

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

01

**Remove tracking gates** — Ensure all core features work identically whether the user allows or denies tracking. No feature should be locked behind ATT authorization.


02

**Remove notification gates** — If your app requires push notification permission before proceeding, make it optional. Add a 'Skip' or 'Not Now' button.


03

**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.


04

**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.


05

**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

  • Design the app to work fully without tracking from the start
  • Treat tracking permission as a revenue optimization, not a feature gate
  • Use a soft pre-prompt to explain benefits, then respect the user's choice completely
  • Example Rejection Email

    From:Apple App Review Team
    Subject:Guideline 5.1.2 - Guideline 5.1.2(i) - Privacy: Gating Fun
    Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing Your app requires users to allow tracking or enable push notifications as a condition of using the app's features. Specifically, users who decline the App Tracking Transparency prompt are unable to access the app's core functionality, or the app repeatedly prompts users to enable tracking after they have declined. Next Steps: Please update your app so that: 1. Users who decline tracking can still access all core features. 2. The app does not repeatedly prompt or pressure users to enable tracking or push notifications. 3. Functionality is not degraded for users who decline tracking or push notification permissions.

    Before & After

    Before — Rejected

    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 — Approved

    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

    View all Guideline 5 rejections