Complete Guide to App Store Privacy Settings When Using AdMob

When using AdMob in your iOS app, properly configuring privacy information in App Store Connect is crucial. Since December 8, 2020, disclosing privacy details has become mandatory when publishing or updating apps. This article provides a comprehensive guide on the correct settings when using the AdMob SDK.

Why Privacy Settings Matter

Apple positions user privacy as one of the core values of the App Store. Without proper settings:

Your app may be rejected during review
You may lose user trust
Legal issues may arise

Data Collected by AdMob SDK

The AdMob SDK collects the following data:

1. Location Information

Type: Coarse Location
Purpose: Ad targeting
Linked to User: Yes
Used for Tracking: Yes

2. Identifiers

Type: Device ID (IDFA, etc.)
Purpose: Third-party advertising
Linked to User: Yes
Used for Tracking: Yes

3. Usage Data

Type: Product Interaction
Purpose: Measuring ad performance
Linked to User: Yes
Used for Tracking: Yes

4. Diagnostics

Type: Crash Data, Performance Data
Purpose: Improving ad SDK
Linked to User: No (exceptionally)
Used for Tracking: No

Step-by-Step App Store Connect Configuration

Step 1: Start Privacy Information Entry

Log in to App Store Connect
Select your target app
Navigate to "App Privacy" section
Click "Get Started"

Step 2: Select Data Types

When using AdMob, select:

✅ Location → Coarse Location
✅ Identifiers → Device ID
✅ Usage Data → Product Interaction
✅ Diagnostics → Crash Data, Performance Data

Step 3: Configure Each Data Type

Coarse Location

Purpose: Third-Party Advertising
Data Linked to User: Yes
Used for Tracking: Yes

Device ID

Purpose: Third-Party Advertising
Data Linked to User: Yes
Used for Tracking: Yes

Product Interaction

Purpose: Third-Party Advertising
Data Linked to User: Yes
Used for Tracking: Yes

Crash Data

Purpose: Analytics
Data Linked to User: No
Used for Tracking: No

Common Mistakes and Important Notes

1. Under-reporting Data Collection

It's crucial to accurately declare all data collected by AdMob. Some data types are easily overlooked, so check carefully.

2. Wrong Purpose Selection

Most data is collected for "Third-Party Advertising" purposes. Avoid selecting "Analytics" or "App Functionality."

3. Incorrect Tracking Settings

AdMob's ad delivery basically involves tracking. Select "Used for Tracking: Yes" for all data except crash data.

Relationship with ATT (App Tracking Transparency)

Since iOS 14.5, user permission is required for tracking:

import AppTrackingTransparency
import AdSupport

// Request tracking authorization
ATTrackingManager.requestTrackingAuthorization { status in
    switch status {
    case .authorized:
        // Tracking authorized
        print("Tracking authorized")
    case .denied:
        // Tracking denied
        print("Tracking denied")
    case .restricted, .notDetermined:
        // Other states
        print("Tracking status: \(status)")
    @unknown default:
        break
    }
}

Best Practices

1. Create a Privacy Policy

Include a privacy policy link both within your app and on the App Store product page.

2. Ensure Transparency

Clearly explain the purpose and scope of data collection to users.

3. Regular Reviews

As AdMob SDK updates may change collected data, review your settings periodically.

4. Test Environment Verification

Verify that settings work correctly in a test environment before releasing to production.

Conclusion

While App Store privacy settings for AdMob may seem complex at first glance, understanding the purpose and configuration of each data type enables proper implementation. Use this guide to ensure accurate settings that maintain user trust and facilitate smooth app reviews.

Privacy settings are not a one-time task. It's important to continuously review and update them in response to SDK updates and Apple policy changes.