AdMob and Data Safety: What You're Actually Required to Declare

AdMob integrations routinely under-declare. The SDK collects advertising ID, and depending on your mediation setup, potentially location and device information for targeting. Google's own AdMob Data Safety guidance lists specific rows expected for standard integrations — and Play's automated review checks bundles against that expected set.

The number worth knowing: AdMob-related Data Safety mismatches are among the top few reasons apps get flagged for manual review after an otherwise clean submission, because ad SDK behavior is well-fingerprinted on Google's end.

The fix

Fix: pull up AdMob's own disclosure guidance for your specific mediation partners — generic AdMob declarations aren't enough if you've added mediation networks.

The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.

Keep going

Data Safety generator →

Turns these answers into a Play-ready CSV.

Data Safety guide →

The full method behind the checks.

Short, specific submission fixes.

Run this check on your own AAB

Free analysis, exports when you need them.

Start free See pricing