Real-World Cases

Guideline 5.1.1 - Legal - Privacy. Your app fingerprints users using a combination of device characteristics without going through AppTrackingTransparency.

Fix: Removed all device fingerprinting code. Implemented SKAdNetwork for attribution instead. Used ATT prompt for any user-level tracking. Apple has become very strict about fingerprinting as a tracking wo...

Guideline 5.1.1 - Legal - Privacy. Your app uses the AdSupport framework to access the advertising identifier but does not present the App Tracking Transparency prompt before accessing it.

Fix: Delayed Facebook SDK initialization until after ATT prompt response. If user denies tracking, initialize Facebook SDK with tracking disabled using Settings.setAdvertiserTrackingEnabled(false). Never a...

Guideline 5.1.1 - Legal - Privacy. Your app does not include an ATT prompt but uses IDFA through a third-party advertising SDK.

Fix: Added ATT prompt before initializing any ad SDK. In AppDelegate, request tracking authorization first. Only initialize AdMob after receiving authorization response. If declined, AdMob uses contextual...

Apple rejecting apps because they don't ask users for app tracking permission

Fix: Implemented ATTrackingManager.requestTrackingAuthorization and added NSUserTrackingUsageDescription to Info.plist.

App rejected because we don't ask users for app tracking permission

Fix: Implemented ATTrackingManager.requestTrackingAuthorization before any tracking code runs.

Guideline 5.1.1 - Legal - Privacy. Your game uses the DeviceCheck framework in a way that functions as fingerprinting rather than fraud prevention.

Fix: Restricted DeviceCheck usage to its intended purpose: fraud prevention and abuse detection only. Removed it from the analytics pipeline. Used ATT-compliant methods for device-level analytics with user...

Guideline 5.1.2 - Your app uses tracking frameworks (Facebook SDK, Adjust) but the ATT purpose string does not accurately describe why tracking is needed.

Fix: Rewrote the ATT purpose string to be specific: This app would like permission to track your activity across other companies apps and websites to provide personalized ads and measure ad effectiveness....

App rejected several times related to ATT and Google Ads

Fix: Completely removed all tracking SDKs, removed ATT prompt, updated privacy nutrition labels to reflect no tracking.

App rejected several times related to ATT and Google Ads

Fix: Completely removed Google Ads SDK along with ATT framework. Updated privacy nutrition labels to reflect no tracking.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage. Your app accesses the IDFA via AdSupport framework but does not present the ATT prompt.

Fix: Added ATT prompt that fires before any SDK initialization. If user declines tracking, Facebook SDK is initialized with tracking disabled. Also updated privacy nutrition label to reflect ad tracking.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage. Update the AppTrackingTransparency framework purpose string to explain how the app will use the requested information.

Fix: Updated purpose string to: We use your advertising identifier to deliver personalized ads and measure ad campaign effectiveness. Your data is not sold to third parties. Apple approved with the specifi...

Guideline 5.1.1 - Legal - Privacy. Your app asks for first and last name after Sign in with Apple, which defeats the purpose of Apples privacy features.

Fix: Used the name provided by ASAuthorization credential response. If user hides their name, respect that choice and use a display name or username instead. Never force users to provide information they c...

Guideline 5.1.2 - Your app accesses the Advertising Identifier (IDFA) but does not present the App Tracking Transparency prompt before accessing it.

Fix: Restructured app initialization to show the ATT prompt before initializing any ad SDKs. Added a pre-ATT explanation screen telling users why we ask for tracking. Only initialize AdMob after the user r...