AdMob's program policies include the Google Publisher Policies, and those require a privacy policy that discloses the data collection that happens because you show Google ads. On top of that, the Google Mobile Ads SDK collects data that both Apple's App Privacy section and Google Play's Data safety form ask about, and on iOS the advertising identifier sits behind App Tracking Transparency. This guide covers what Google requires in the policy, what the SDK collects, and how each store's disclosures fit together.
Need these pages for your app?
Get a Privacy Policy, Terms and Support page in 2 minutes. Copy the text free, or host them for $6 one-time.
The privacy disclosures section of the Google Publisher Policies says you must have and abide by a privacy policy that clearly discloses any data collection, sharing, and usage that happens as a consequence of using Google's products, including the technologies involved, such as cookies, web beacons, IP addresses, or other identifiers. Google says this applies on any platform, apps included.
The policy must also tell users that third parties may place and read cookies, or use web beacons or IP addresses, to collect information as a result of ad serving. For Google's own use of data, Google gives you the option of a prominent link to its page on how it uses data from partners' sites and apps (policies.google.com/technologies/partner-sites). That link is one way to meet the disclosure, not a separate mandate.
If you have users in the European Economic Area, the UK, or Switzerland, Google's EU user consent policy adds more: legally valid consent for cookies or local storage where required and for personalized ads, records of that consent, and clear information about each party that may collect or use users' personal data. Google's AdMob help says linking its data-use page meets the part of that policy about Google's own use of data.
On Android, Google's data disclosure page says the SDK automatically collects and shares IP address (used to estimate general location), user product interactions such as app launches, taps, and video views, diagnostic information, and device and account identifiers including the Android advertising ID and app set ID. Google says this is for advertising, analytics, and fraud prevention, that the data is encrypted in transit, and that you're solely responsible for your Data safety form answers.
On iOS, Google's disclosure lists a device ID such as the advertising identifier, advertising data, product interactions, crash data, performance data, and IP address used to estimate general location. Google says you're responsible for checking the SDK's privacy manifest and keeping your disclosures up to date.
Apple counts data your third-party partners collect, so AdMob's data belongs in your App Privacy answers. Apple defines tracking as linking data from your app with third-party data for targeted ads or ad measurement, or sharing it with a data broker, and gives targeted ads based on data from other companies' apps and websites as an example. Guideline 5.1.2(i) requires explicit permission through the App Tracking Transparency APIs before you track.
Google's iOS docs say the SDK can use the IDFA in ad requests if the user grants ATT permission, and recommend waiting for the ATT prompt to finish before loading ads. If you show the prompt, add an NSUserTrackingUsageDescription string to Info.plist explaining why. Google also supports SKAdNetwork for install attribution when the IDFA isn't available.
Google Play counts data sent off the device by SDKs as collected by your app, so the Google Mobile Ads SDK's data goes in your Data safety form even though Google runs the SDK. Use Google's disclosure page as the starting point and check it against the SDK version you ship, since Google publishes the list for a specific version. Your privacy policy should cover the same data, because Google's User Data policy requires it to disclose how your app collects, uses, and shares user data.
Check 'Shows third-party ads' and BaseTerms adds an Advertising section to your privacy policy. It says the app shows third-party ads, such as those served by Google AdMob, that advertising partners may collect device identifiers and usage data to serve relevant ads, and that users can opt out of personalized advertising in their device settings. Your Terms of Service also gets a Third-Party Advertisements section disclaiming responsibility for ad content.
That section doesn't mention cookies, web beacons, or IP addresses, doesn't link Google's data-use page, and has no consent or ATT language. If you show AdMob ads, copy the raw Markdown and add those disclosures before self-hosting, and set up a consent flow if you have users in the EEA, UK, or Switzerland. Hosting the generated pages on the subdomain is $9 one-time.
Ready to ship?
Privacy Policy, Terms, Support, plus Data Deletion if your app has accounts — ready to paste into App Store Connect and Google Play Console. Copy the raw Markdown free or host on a custom subdomain for $6 one-time.
One-time payment. No subscription. No renewal fees.