12AppTesting logo12AppTestingClosed Testing Service
HomeAboutHow It WorksPricingBlogFAQContact
Home › Blog › Google Play Data Safety Form for AdMob Apps: What to Declare

Google Play Data Safety Form for AdMob Apps: What to Declare

Quick answer In the Data safety form for an AdMob app, declare that your app collects and shares the data Google lists for the Google Mobile Ads SDK: IP address, app interactions, diagnostics and device identifiers, for advertising, analytics and fraud prevention. Check the current AdMob page, then add data from your other SDKs.
Illustration for the guide: Google Play Data Safety Form for AdMob Apps: What to Declare

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.

What do you declare for AdMob in the Data safety form?

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.

This is not legal advice: We explain what Google's pages say and how developers usually map them. You are responsible for answers that match what your app really does.

What does the Google Mobile Ads SDK collect?

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 addressCollects the device's IP address, which may be used to estimate the general location of a device
User product interactionsCollects interaction information, including app launch, taps and video views
Diagnostic informationCollects information about app and SDK performance, including app launch time, hang rate and energy usage
Device and account identifiersThe 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.

How do these map to Play Console categories?

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 listTypical Play Console categoryCollectedShared
IP address (may estimate general location)Location > Approximate locationYesYes
User product interactionsApp activity > App interactionsYesYes
Diagnostic informationApp info and performance > DiagnosticsYesYes
Advertising ID, app set ID, other identifiersDevice or other IDsYesYes

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.

How do you answer the form questions?

Form questionWhat 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.

What about your other SDKs?

AdMob is usually not the only thing in your app. Add each SDK's data to the form.

ComponentWhat 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 productsEach product has its own disclosure. Add what applies.
Mediation partnersCheck every partner's documentation, because each network collects its own data.
Your own login, database or backendDeclare what you store, for example email addresses. Add the account deletion answers.
No-code builder componentsCheck components for ads, analytics, location and storage. Kodular, App Inventor and Thunkable apps all need this check.

What does a worked example look like?

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 typeCollectedSharedPurposesSource
Approximate locationYesYesAdvertising, analytics, fraud preventionAdMob SDK (IP address)
App interactionsYesYesAdvertising, analytics, fraud preventionAdMob SDK
DiagnosticsYesYesAdvertising, analytics, fraud preventionAdMob SDK
Device or other IDsYesYesAdvertising, analytics, fraud preventionAdMob SDK (advertising ID, app set ID)
Name, email, photos and everything elseNoNoNoneThe 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.

What must your privacy policy say?

  • That the app shows ads through Google AdMob and that the Google Mobile Ads SDK collects the data you declared.
  • Which data types, for which purposes, and that some data is shared with advertising partners.
  • How users can reset the advertising ID or limit ad personalization.
  • How to contact you, and how to request deletion if the app has accounts.
  • Any data you keep and why.

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.

What are the common mistakes?

MistakeFix
Declaring nothing because the app has no loginAdMob collects data even without accounts. Declare it.
Copying a list from an old articleOpen Google's current page and check the SDK version you use
Forgetting other SDKsList every SDK and read each one's disclosure
Marking the data as not sharedGoogle says the SDK collects and shares it
Privacy policy does not match the formUpdate the policy and the form together
Updating the SDK without recheckingReview 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.

Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.

Sources

Frequently asked questions

Do I have to declare data collection if I only use AdMob?

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.

Which data types does the Google Mobile Ads SDK collect?

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.

Is the advertising ID optional?

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.

Is the data encrypted?

Google says the data the SDK collects is encrypted in transit using TLS.

Does the list apply to every SDK version?

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.

Do I also need to declare Firebase or mediation partners?

Yes, if you use them. Each SDK has its own data collection. Check each provider's disclosure page and add what it collects.