Apple requires that developers publishing apps on the App Store disclose certain information regarding their apps' data use. Apple has announced that these disclosures will be required for new apps and app updates starting December 8, 2020. This guide explains the Google Mobile Ads SDK's data collection practices as of 7.68.0, to make it easier for AdMob developers to answer the questions in App Store Connect.
To improve the performance of AdMob, the Google Mobile Ads SDK may collect certain information from apps, including:
- IP address, which may be used to estimate the general location of a device.
- Non-user related crash logs, which may be used to diagnose problems and improve the SDK. Diagnostic information may also be used for advertising and analytics purposes.
- User-associated performance data such as app launch time, hang rate, or energy usage, which may be used to evaluate user behavior, understand the effectiveness of existing product features, and plan new features. Performance data may also be used for displaying ads, including sharing with other entities that display ads.
- A Device ID, such as the device's advertising identifier or other app- or developer-bounded device identifiers, which may be used for the purpose of third-party advertising and analytics.
- Advertising data, such as advertisements the user has seen, may be used to power analytics and advertising features.
- Other user product interactions like app launch taps, and interaction information, like video views, may be used to improve advertising performance.
If you are using any optional product features that involve additional data (such as advance reporting) or participating in any tests of new product features that involve additional data, be sure to check if those features or tests require additional data disclosures.
If you are using a prior version of the Google Mobile Ads SDK, consider updating to the latest version to ensure your app's disclosures are accurate. The Google Mobile Ads SDK will continue to be updated over time. This article will reflect these changes, so make sure to check back and update your disclosures as necessary.
Apple's privacy manifest files
Google Mobile Ads SDK version 11.2.0 and higher supports privacy manifest declarations. You are responsible for checking the privacy manifest and ensuring that your application's data disclosures are up to date. Refer to Apple documentation for details on interpreting a privacy report and their enforcement update for app submission requirements.
Xcode 16 validation warnings
When submitting apps built with Xcode 16 to the App Store, you might encounter
Upload Symbols Failed warnings related to the Google Mobile Ads and User
Messaging Platform SDKs. You can dismiss these warnings because these SDKs are
static frameworks, which don't need a separate dSYM file for debugging.
Mediation
The following table lists the minimum third-party adapter and SDK versions that contain a privacy manifest declaration.
| Ad Source | Adapter version (Unity) | Adapter version (iOS) | Third-party iOS SDK version | Third-party SDK documentation |
|---|---|---|---|---|
| AppLovin | 7.2.1 | 12.4.1.0 | 12.4.1 | Privacy Manifests |
| Chartboost | 4.6.0 | 9.7.0.0 | 9.7.0 | Privacy Manifest |
| DT Exchange | 3.1.10 | 8.2.7.0 | 8.2.7 | Privacy Manifest File Data Transfer |
| i-mobile | N/A | N/A | Not supported | |
| InMobi | 4.5.1 | 10.7.2.0 | 10.7.2 | Privacy Manifest |
| ironSource | 2.6.0 | 7.9.0.0.0 | 7.9.0.0 | Privacy Manifest Support |
| Liftoff Monetize | 5.1.0 | 7.3.1.0 | 7.3.1 | Adapting to Privacy Changes |
| Line | 1.1.0 | 2.7.20240318.0 | 2.7.20240318 | App Store Disclosure |
| maio | 2.0.2 | 2.1.4.0 | 2.1.4 | Release Notes |
| Meta Audience Network | 3.12.0 | 6.15.0.0 | 6.15.0 | App Store Review requirements |
| Mintegral | 1.6.0 | 7.6.2.0 | 7.6.2 | SDK Privacy Compliance Statement |
| myTarget | 3.16.2 | 5.21.2.0 | 5.21.2 | iOS SDK: Version history |
| Pangle | 2.6.0 | 5.8.0.8.0 | 5.8.0.8 | Privacy Manifests |
| Unity Ads | 3.10.0 | 4.10.0.0 | 4.10.0 | Apple privacy survey for Unity Ads |