Apple App Store's data disclosure requirements
Stay organized with collections
Save and categorize content based on your preferences.
Select platform:
iOS
Unity
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.
The following table lists the minimum third-party adapter and SDK versions
that contain a privacy manifest declaration.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-09-04 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eApple mandates privacy disclosures for new apps and updates on the App Store starting December 8, 2020, requiring developers to detail their app's data collection practices.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Mobile Ads SDK, used by AdMob, collects various data like IP addresses, crash logs, performance data, device IDs, advertising data, and user interactions to improve ad performance and functionality.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers are responsible for reviewing the privacy manifest files within the Google Mobile Ads SDK (versions 11.2.0 and higher) to ensure accurate and up-to-date data disclosures for their apps.\u003c/p\u003e\n"],["\u003cp\u003eWhen using optional features or participating in new product feature tests, developers need to verify and disclose any additional data collection associated with these functionalities.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides a table outlining minimum adapter and SDK versions for various ad sources, enabling developers to ensure their mediation partners also comply with Apple's privacy disclosure requirements.\u003c/p\u003e\n"]]],["Apple mandates that app developers disclose data usage practices. The Google Mobile Ads SDK, from version 7.68.0, collects data like IP addresses, crash logs, performance data, device IDs, advertising data, and user interactions for ad performance and analytics. Developers must update disclosures as the SDK evolves and check for additional data requirements with optional features. SDK version 11.2.0 supports Apple's privacy manifest declarations. Using Xcode 16 will generate `Upload Symbols Failed` warnings that can be ignored.\n"],null,["Select platform: [iOS](/admob/ios/privacy/data-disclosure \"View this page for the iOS platform docs.\") [Unity](/admob/unity/privacy/data-disclosure \"View this page for the Unity platform docs.\")\n\n\u003cbr /\u003e\n\nApple requires that developers publishing apps on the App Store disclose\n[certain information](//developer.apple.com/app-store/app-privacy-details/)\nregarding their apps' data use. Apple has\n[announced](//developer.apple.com/news/?id=vlj9jty9) that these disclosures will\nbe required for new apps and app updates starting December 8, 2020. This guide\nexplains the Google Mobile Ads SDK's data collection practices as of\n7.68.0, to make it easier for AdMob\ndevelopers to answer the questions in App Store Connect.\n\nTo improve the performance of AdMob, the Google Mobile Ads SDK may collect\ncertain information from apps, including:\n\n- IP address, which may be used to estimate the general location of a device.\n- 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.\n- 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.\n- 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.\n- Advertising data, such as advertisements the user has seen, may be used to power analytics and advertising features.\n- Other user product interactions like app launch taps, and interaction information, like video views, may be used to improve advertising performance.\n\nIf you are using any optional product features that involve additional data\n(such as advance reporting) or participating in any tests of new product\nfeatures that involve additional data, be sure to check if those features or\ntests require additional data disclosures.\n\nIf you are using a prior version of the Google Mobile Ads SDK, consider\nupdating to the latest version to ensure your app's disclosures are accurate.\nThe Google Mobile Ads SDK will continue to be updated over time. This\narticle will reflect these changes, so make sure to check back and update your\ndisclosures as necessary.\n\nApple's privacy manifest files\n\nGoogle Mobile Ads SDK version 11.2.0 and higher supports\nprivacy manifest declarations. You are responsible for checking the privacy\nmanifest and ensuring that your application's data disclosures are up to date.\nRefer to\n[Apple documentation](//developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)\nfor details on interpreting a privacy report and their [enforcement update](//developer.apple.com/news/?id=pvszzano) for app submission requirements.\n\nXcode 16 validation warnings\n\nWhen submitting apps built with Xcode 16 to the App Store, you might encounter\n`Upload Symbols Failed` warnings related to the Google Mobile Ads and User\nMessaging Platform SDKs. You can dismiss these warnings because these SDKs are\nstatic frameworks, which don't need a separate dSYM file for debugging.\n\nMediation\n\nThe following table lists the minimum third-party adapter and SDK versions\nthat contain a privacy manifest declaration.\n\n| Ad Source | Adapter version | Third-party SDK version | Third-party SDK documentation |\n|-----------------------|-----------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| AppLovin | 12.4.1.0 | 12.4.1 | [Privacy Manifests](//dash.applovin.com/documentation/mediation/ios/getting-started/apple-privacy-manifests) |\n| Chartboost | 9.7.0.0 | 9.7.0 | [Privacy Manifest](//docs.chartboost.com/en/monetization/integrate/ios/privacy-manifest/) |\n| DT Exchange | 8.2.7.0 | 8.2.7 | [Privacy Manifest File Data Transfer](//developer.digitalturbine.com/hc/en-us/articles/13384579176860-iOS-SDK-v-8-2-7-Privacy-Manifest-File-Data-Transfer) |\n| i-mobile | N/A | Not supported | |\n| InMobi | 10.7.2.0 | 10.7.2 | [Privacy Manifest](//support.inmobi.com/monetize/sdk-documentation/ios-guidelines/overview-ios-guidelines#privacy-manifest) |\n| ironSource | 7.9.0.0.0 | 7.9.0.0 | [Privacy Manifest Support](//developers.is.com/ironsource-mobile/ios/ios-privacy-settings-and-configurations/#step-5) |\n| Liftoff Monetize | 7.3.1.0 | 7.3.1 | [Adapting to Privacy Changes](//liftoff.io/blog/liftoff-privacy-changes-google-tcf-apple-manifest/) |\n| Line | 2.7.20240318.0 | 2.7.20240318 | [App Store Disclosure](//adsnetwork-docs.linebiz.com/fivesdk-ios/store-release/app-store-disclosure.html) |\n| maio | 2.1.4.0 | 2.1.4 | [Release Notes](//github.com/imobile/MaioSDK-v2-iOS/blob/master/release-notes.md) |\n| Meta Audience Network | 6.15.0.0 | 6.15.0 | [App Store Review requirements](//developers.facebook.com/docs/ios/#update-facebook-and-audience-network-sdk-for-ios-with-privacy-manifest-for-app-store-review-requirements) |\n| Mintegral | 7.6.1.0 | 7.6.1 | [SDK Privacy Compliance Statement](//dev.mintegral.com/doc/index.html?file=sdk-m_sdk-ios&lang=en#sdkprivacycompliancestatement) |\n| myTarget | 5.21.2.0 | 5.21.2 | [iOS SDK: Version history](//target.my.com/help/partners/mob/ioshistory/en) |\n| Pangle | 5.8.0.8.0 | 5.8.0.8 | [Privacy Manifests](//www.pangleglobal.com/zh/integration/privacy-manifests) |\n| Unity Ads | 4.10.0.0 | 4.10.0 | [Apple privacy survey for Unity Ads](//docs.unity.com/ads/en-us/manual/ApplePrivacySurvey) |"]]