Showing ads in an Android app: what Google Play's Ads policy restricts
Review Google Play restrictions on ad placement, disruptive formats, location use and advertising identifiers in Android apps.
If an app earns from ads, Google Play's Ads policy affects design, not only paperwork: where ads appear, how they close and what data they use. This article summarises two Google pages as read on 15 November 2026. It says nothing about how much an app can earn; neither page does. Declare ads in the Play Console "Contains ads" setting (see our Play release article) and treat each ad SDK's data use in your Data safety form (see our Data safety article).
What Google's Ads policy says (as read 15 Nov 2026)
Google says it considers an ad's content, audience, user experience, behaviour, and security and privacy, and treats ads and their offers as part of the app, so they must follow all other Play policies. Extra requirements apply to apps targeting children (the Families ads rules, which we did not read).
- Appropriate ads. Ads and their offers, including an ad promoting another app's download, must suit the app's content rating. The page's example: a Mature ad in an Everyone-rated app.
- No deceptive ads. Ads must not imitate app features or operating-system notifications or warnings, and it must be clear which app serves each ad.
- No disruptive ads. Ads displayed unexpectedly, causing accidental clicks or getting in the way of device functions are not allowed. An app cannot force a user to click an ad or submit personal information for advertising before using the app fully. Ads must show only inside the app serving them and not interfere with other apps, system buttons or ports, including through overlays and widgets. Full-screen or interfering ads must be easily dismissible without penalty; the page's violation examples include no dismiss button, a fake dismiss button, ads that pop up where users usually tap for another function, ads that appear on the home screen after leaving the app, and ads triggered by the home button or other exit features.
- Better Ads Experiences. Not allowed: full-screen interstitials of any format that show unexpectedly, typically when the user chose to do something else; ads at the beginning of a game level or content segment; full-screen video interstitials before the loading (splash) screen; and full-screen interstitials that cannot be closed after 15 seconds. Exceptions in the text: opt-in interstitials or ones that do not interrupt the user's action (for example after a score screen) may last longer than 15 seconds; rewarded ads that users explicitly opt into are outside this policy; so is advertising that does not interfere with normal use, such as non-full-screen banners or video with integrated ads. The companion FAQ says natural breaks (end of a level or chapter) suit interstitials, that apps without natural breaks should use "good judgment from a UX perspective", that a static interstitial may follow the splash screen once the app has loaded, and that developers are responsible for ad SDK code, with SDK settings and placement adjustable in the app.
- Made for Ads. Apps that show interstitials repeatedly to distract users from in-app tasks are not allowed; the example is an interstitial after each consecutive user action.
- Lockscreen. Apps may not monetise the locked display unless lockscreen is the app's exclusive purpose.
- Ad fraud is strictly prohibited (separate policy, unread).
- Location data for ads. If permission-based location is used for ads, this must be clear to users and documented in the privacy policy, with links to relevant ad network privacy policies, and location permission may be requested only for current features and not solely for ads.
- Android advertising ID (AAID). For advertising and user analytics only; the "opt out of interest-based advertising / ads personalisation" setting must be checked on each access; the ID may not be joined to persistent device identifiers, and, for advertising use, may be joined to personally identifiable information only with explicit consent. For analytics, it may not be joined to personally identifiable information or persistent device identifiers; a reset ID must not be linked to the previous one without explicit consent; for users who opted out, no profiles or personalised targeting (the page allows contextual ads, frequency capping, conversion tracking, reporting and security or fraud detection); a deleted ID reads as zeros; and use must be disclosed in a legally adequate privacy notification. The source also requires advertising use of the AAID, when available, instead of other device identifiers, and compliance by parties with whom it is shared.
Planning notes (ours)
- Decide the ad formats and where they appear at design time, and check each against the lists above before building; moving an interstitial later changes flows and tests.
- Treat every ad SDK as part of the app for policy purposes: list what it transmits for the Data safety form and privacy policy.
- Say "Contains ads" in the Play declaration when ads are present (see our Play release article).
- No income estimate is possible from these pages. Do not add one.
Limits
Two Google pages, read in full; the advertising ID section was rechecked against the full currently fetched policy. We did not read the Ad Fraud, Families ads, Restricted Content or Mobile Unwanted Software policies. Policies change; check before publishing. Child-directed apps and privacy law need counsel.
By Omnistu.