Google AdMob · Platform guide
Privacy policy for apps using AdMob
If your app shows AdMob ads, your privacy policy should say the Google Mobile Ads SDK collects IP address, user product interactions, diagnostic information and device identifiers for advertising, analytics and fraud prevention. In the EEA and UK, Google’s EU User Consent Policy also requires disclosures and consent, usually via the UMP SDK.
What Google AdMob requires
Google Play data disclosure for the Google Mobile Ads SDK
“automatically collects and shares IP address, user product interactions, diagnostic information, and device/account identifiers for advertising, analytics, and fraud prevention”
Source: developers.google.com verified 2026-10-30
What common SDKs collect
| SDK / API | Data it collects | Source |
|---|---|---|
| Google Mobile Ads SDK (AdMob) |
| Source: developers.google.com |
Everything in this table must appear in your policy if the SDK ships in your build.
Where to put the URL
- 3.1Your app’s store listings (App Store Connect and Play Console) and an in-app link.
- 3.2Show the UMP consent message to EEA and UK users before ads load.
Sample clause
§ 4.1 · Advertising
Our app shows ads from Google AdMob. The Google Mobile Ads SDK collects your IP address, how you interact with ads, diagnostic data and device identifiers such as the advertising ID, for advertising, analytics and fraud prevention. In the EEA and UK we ask for your consent first, and you can change your choice in Settings → Privacy.
Questions
- Do I need a privacy policy to use AdMob?
- Yes in practice: both app stores require one for every app, and AdMob’s SDK collects device identifiers you must disclose.
- What must an AdMob privacy policy say?
- Name Google as an ad partner, list the data the SDK collects, explain cookies or advertising IDs, and say how users can change consent or reset their ad ID. This is not legal advice.