Google Play and real-money gambling: the Android half of the problem

Android tends to be treated as the easy half of an operator’s mobile launch. Apple gets the anxiety, and the Google Play gambling app policy gets read the week before release. That order is usually backwards. Google’s rules are just as specific as Apple’s Guideline 5.3, and they come with a gate that sits in front of app review entirely.

What the Google Play gambling app policy says

Google’s starting point is a prohibition with an exception. In its own words:

“While Google Play generally prohibits apps from facilitating real-money gambling and gaming, an exception is made for those that are licensed and approved by Google.”

The exception covers five product types: online casino games, sports betting, horse racing (where regulated and licensed separately from sports betting), lotteries and daily fantasy sports. A product that doesn’t fit one of those isn’t covered by it.

For apps that do qualify, the published requirements concern:

• Approval — the developer must complete Google’s application process before the app is distributed.
• Licensing — a valid gambling licence for each country or state/territory the app is distributed in, with nothing offered beyond that licence’s scope.
• Age and location — the app must prevent under-age use, and access from anywhere the licence doesn’t cover.
• Price and payments — free to download, not sold as a paid app, and no use of Google Play’s in-app billing.
• Rating and disclosure — an AO (Adults Only) or IARC-equivalent rating, with responsible gambling information in both the app and its listing.

The gambling application form comes first

The part teams miss is that approval is a separate step, handled through the gambling application form Google Play publishes in its Play Console Help centre, not a checkbox in the release flow.

A few details on that form shape the timeline more than the policy does:

It is per market. Google asks for the form to be completed “for each market where you want your particular app distributed”. In the US, submissions are app- and state-specific, so each additional state is a new application.

The licensee has to line up. The form states that the licensee must be the same entity as the app developer, or the operator in the case of a third-party app. When the licence sits with one company and the developer account with another, that becomes a paperwork problem before it becomes a technical one.

Approval isn’t permanent. A change of ownership, or a change in licensing, means the app must be recertified.

Google also sets expectations on time: certification and app review should be expected “to take at least a week or more”. And the form is blunt that attempts to bypass certification may result in full removal from Google Play.

Country by country, state by state

Google Play lists the countries where licensed gambling apps can be distributed: 41 at the time of writing, from Australia and Brazil to the United Kingdom and the United States, each with its own permitted product types. Some categories in some countries are limited to governmental operators. In Canada, the form distinguishes Ontario and Alberta from the rest.

The US has its own table, state by state and product by product. A state can be open for sports betting and closed for online casino, or the reverse. Google’s position on anything missing from that table is plain: states not listed are not supported for real-money apps.

This is where commercial plans and Play’s map drift apart. A licence in hand doesn’t mean the market is open on Play, and a market open on Play doesn’t mean every product in the licence is.

Why Android release plans slip

The slips we see rarely come from the policy text. They come from sequencing:

• The application is started after the build, so review waits on paperwork.
• The licensed entity, the developer account and the store listing belong to different parts of the organisation.
• One market’s approval is assumed to cover the next.
• Geo-restriction and age checks are treated as launch polish rather than requirements Google checks for.

Each one costs weeks, and they tend to arrive together.

When Play isn’t an option

Where Google Play doesn’t support a market or product type, operators fall back to distributing the Android app outside the store, which Android permits. That route has its own costs, discoverability and updates among them, and it is changing: Google’s Android developer verification programme starts regional enforcement on 30 September 2026, with a global rollout on certified devices planned from 2027. The trade-offs look a lot like the ones in native, WebView or PWA.

Which markets you can reach through Play, in what order, and what the Android app has to contain to get there depends on your licences, your products and your organisation. If you’re planning an Android launch and want the store side mapped before the build rather than after it, get in touch.

---

Google’s policies and the gambling application form change, and the live wording is what review applies. This is a plain-language summary, last checked on 28 September 2026 — not compliance advice. Check the current Real-Money Gambling, Games, and Contests policy and take proper advice before submitting.