Google Play Data Safety Form and Privacy Policy
Who must complete the Data safety form, what to declare and the mistakes that cause problems later.
Read the guide →
You added AdMob to your app and now the Data safety form asks what data your app collects and shares. Answer too little and your app can be rejected. Answer carelessly and you may declare things that are not true. This guide uses Google's own disclosure for the Google Mobile Ads SDK, explains how to answer each question, and walks through a worked example.
For an AdMob app, declare that your app collects and shares the data types Google lists for the Google Mobile Ads SDK, for advertising, analytics and fraud prevention, and then add whatever your own code and other SDKs collect. Google publishes this list on its AdMob Play data disclosure page, and says developers are solely responsible for how they answer the form.
The page is versioned and updated over time. Always open the current version before you submit, and treat the tables below as a way to understand it, not a replacement.
Google's page for Google Mobile Ads SDK version 25.5.0 says the SDK automatically collects and shares the following data for advertising, analytics and fraud prevention.
| Data type (Google's wording) | What Google says |
|---|---|
| IP address | Collects the device's IP address, which may be used to estimate the general location of a device |
| User product interactions | Collects interaction information, including app launch, taps and video views |
| Diagnostic information | Collects information about app and SDK performance, including app launch time, hang rate and energy usage |
| Device and account identifiers | The Android advertising ID, the app set ID and, if applicable, other identifiers related to signed-in accounts on the device. Ad ID collection is optional. |
Google also says the collected data is encrypted in transit using TLS. Users can reset or delete the ad ID in Android settings, developers can prevent its collection through the manifest, and Limited Ads may also stop transmission of the ad ID and other data. Optional features such as advanced reporting or participating in tests may involve additional data, so check whether they need extra disclosures.
Play Console uses its own category names. This mapping is how developers commonly translate Google's list, so compare it with Google's current page and Play Console wording before you rely on it.
| Google's AdMob list | Typical Play Console category | Collected | Shared |
|---|---|---|---|
| IP address (may estimate general location) | Location > Approximate location | Yes | Yes |
| User product interactions | App activity > App interactions | Yes | Yes |
| Diagnostic information | App info and performance > Diagnostics | Yes | Yes |
| Advertising ID, app set ID, other identifiers | Device or other IDs | Yes | Yes |
The purposes to choose are the ones Google names: advertising or marketing, analytics, and fraud prevention, security and compliance, where those options fit your app.
| Form question | What to answer for an AdMob app |
|---|---|
| Does your app collect or share any required user data types? | Yes |
| Is all of the user data collected by your app encrypted in transit? | Google says the SDK's data is encrypted in transit with TLS. Answer yes only if your own code and other SDKs also encrypt in transit. |
| Do you provide a way for users to request deletion? | Depends on your app. If it has accounts, see the account deletion requirement |
| For each data type: collected, shared, or both? | Collected and shared for the AdMob types above |
| Is the data processed ephemerally? | Follow Google's description for the SDK and for your own processing |
| Is collection required or optional? | The SDK collects its data automatically. Ad ID collection is optional because you can stop it in the manifest. |
| Why is it collected or shared? | Advertising or marketing, analytics, fraud prevention |
The general walkthrough of the form is in Google Play Data safety form and privacy policy.
AdMob is usually not the only thing in your app. Add each SDK's data to the form.
| Component | What to do |
|---|---|
| Consent SDK (User Messaging Platform) | Google publishes a separate Play data disclosure page for it. Check it and add what it lists. |
| Firebase Analytics, Crashlytics or other Firebase products | Each product has its own disclosure. Add what applies. |
| Mediation partners | Check every partner's documentation, because each network collects its own data. |
| Your own login, database or backend | Declare what you store, for example email addresses. Add the account deletion answers. |
| No-code builder components | Check components for ads, analytics, location and storage. Kodular, App Inventor and Thunkable apps all need this check. |
This example is made up to show the process. Imagine a simple flashlight app with one AdMob banner, no login, no analytics and no other SDKs.
| Data type | Collected | Shared | Purposes | Source |
|---|---|---|---|---|
| Approximate location | Yes | Yes | Advertising, analytics, fraud prevention | AdMob SDK (IP address) |
| App interactions | Yes | Yes | Advertising, analytics, fraud prevention | AdMob SDK |
| Diagnostics | Yes | Yes | Advertising, analytics, fraud prevention | AdMob SDK |
| Device or other IDs | Yes | Yes | Advertising, analytics, fraud prevention | AdMob SDK (advertising ID, app set ID) |
| Name, email, photos and everything else | No | No | None | The app has no such features |
That app does not have accounts, so it does not need an account deletion path. If it adds a login later, update the form first. Also tell the truth about children: if the app is for children or mixed audiences, ad settings change. See the target audience declaration.
The policy must match the form. A policy that says no data is collected while the form declares IDs and location is a common reason for rejection. See why apps get rejected.
| Mistake | Fix |
|---|---|
| Declaring nothing because the app has no login | AdMob collects data even without accounts. Declare it. |
| Copying a list from an old article | Open Google's current page and check the SDK version you use |
| Forgetting other SDKs | List every SDK and read each one's disclosure |
| Marking the data as not shared | Google says the SDK collects and shares it |
| Privacy policy does not match the form | Update the policy and the form together |
| Updating the SDK without rechecking | Review the disclosure each time you upgrade a major version |
If your ads are not showing after you publish, read AdMob ads not showing in a new app and AdMob limited ad serving.
Yes. Google's AdMob page says the Google Mobile Ads SDK collects and shares certain data automatically, and that you are solely responsible for how you answer the Data safety form.
Google's disclosure for version 25.5.0 lists IP address, user product interactions, diagnostic information, and device and account identifiers such as the advertising ID and app set ID.
Google says ad ID collection is optional. Users can reset or delete it in Android settings, and developers can prevent collection by updating the app's manifest file.
Google says the data the SDK collects is encrypted in transit using TLS.
No. Google's page covers one specific version and says older versions may differ and that the page will be updated. Check the current page for the version you use.
Yes, if you use them. Each SDK has its own data collection. Check each provider's disclosure page and add what it collects.