A real-money casino app is the one part of a mobile launch that has to be approved before anyone is allowed to review it. Google Play’s rule for it is a prohibition with a narrow exception, and the exception is granted through an application form rather than through a release pipeline. That turns a policy question into a sequencing one: the store’s approval gate sits in front of app review, it is filed market by market, and it moves on the store’s timetable rather than on the build’s.
The decision belongs to whoever owns the mobile channel — an operator’s product lead, a platform delivering the app for a set of markets, or the supplier contracted to ship it. The question in front of them is not whether the app is good. It is which markets the app may lawfully be offered in, which of those the store actually supports, what the store inspects inside the build, and who in the organisation has to be the licensee on the paperwork.
Play’s rule is a prohibition with an exception
The store states the starting position itself: while Google Play generally prohibits apps that facilitate 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 real-money product outside that list is not covered by it.
The boundary is worth reading closely, because it reaches marketing as well as mechanics. The same policy prohibits apps that let a user wager for a real-world prize, and its examples of violations include navigational elements — menu items, tabs, buttons, webviews — that issue a call to action to wager, such as inviting a user to “BET!” or “REGISTER!” or “COMPETE!” for a cash prize. Relabelling a wagering flow, or housing it in a webview, does not move it outside the rule.
Where the exception applies, the published requirements are short enough to check one by one: complete the application process; comply with applicable laws and industry standards in every country of distribution; hold a valid gambling licence for each country or state and territory where the app is distributed; offer no product beyond the scope of that licence; prevent under-age use; prevent access from areas the licence does not cover; be free to download and not sellable as a paid app; not use Google Play in-app billing; carry an AO, Adults Only, or IARC-equivalent rating; and display responsible-gambling information in both the app and its listing.
Approval is a form, and it is filed per market
The application is made through the Gambling Application Form in the store’s help centre, “for each market where you want your particular app distributed”. It is a submission in front of distribution, not a setting inside the release flow, and it carries two commercial consequences that are easy to discover late.
The first is that it is per market, and in the United States per state as well: submissions there are app- and state-specific, so each additional state is a separate form. The second is that the form fixes who may hold the approval — the licensee must be the same entity as the app developer or, in the case of a third-party application, the same entity as the operator. When a gambling licence sits with one company and the developer account with another, the launch has a paperwork fault that no engineering work can fix, and discovering it during a review window costs more than discovering it during a design sprint.
Approval is also not permanent. A change of ownership, or a change in licensing and authorisation, means the app must be recertified through the same process. On timing, the form sets its own expectation rather than a service level: certification and app review should be expected to take at least a week or more. And the consequences of shortcuts are stated without ambiguity — attempts to bypass the certification process, or repeated or serious violations, may result in full removal from Google Play.
The map, not the licence, decides which markets exist
An operator’s licence portfolio and the store’s product map are two different documents, and the launch plan needs the intersection of them rather than the union. The application form lists the countries where licensed gambling apps may be distributed — 41 of them at the time of reading — from Australia and Brazil to the United Kingdom and the United States, each with its own permitted product types, and with some categories in some countries reserved to governmental operators.
The United States is mapped state by state and product by product, and the map is narrower than most roadmaps assume. Reading the form’s table as published on 2026-10-10, online casino appears at all in eight entries — Connecticut, Delaware, Michigan, Nevada, New Jersey, Pennsylvania, Rhode Island and West Virginia — and Nevada limits it to poker. Several states are open for sports betting and closed for online casino; others are the reverse; lottery and horse racing have their own columns and their own footnotes, with some rows marked for governmental operators only. The form’s position on anything absent from the table is explicit: it does not currently support publishing real-money gambling apps in states that are not listed. This is also where a product roadmap and a licence collide — the policy requires that an app not offer a type of gambling product that exceeds the scope of its licence, so a casino app cannot carry a sportsbook tab on the strength of a casino licence.
Two further wrinkles are worth carrying into the plan. Nigeria is mapped at state level as well, with four states listed. And the form recognises a German-specific entity: an app offered by a licensed commercial gambling broker (gewerblicher Spielvermittler) is filed against the broker licence, and apps provided within the scope of that licence are not treated as aggregators for the purposes of the store’s gambling terms.
The pilot route has closed
Google Play has previously opened limited-time pilots for real-money game types that its policy does not otherwise allow. That route is not currently available. The status page states plainly that there are no active pilots, and its own history shows the doors closing rather than opening: the Indian pilot’s grace period ended on 22 January 2026, after which apps that had been in it could remain only by removing real-money functionality; the Mexican daily-fantasy pilot concluded on 4 June 2026, with real-money apps continuing only where they already fit the standard policy and the country’s permitted game types; and the Japanese online crane-game pilot ended on 11 July 2023, after which crane games became listable globally subject to requirements and applicable law.
For a supplier or a platform weighing an unlisted product type, the honest reading of that record is that an unlisted type is a closed door rather than a queue. A product that does not fit the five types, in a market not on the list, has no form to file.
What the store inspects inside the build
Four of the requirements are properties of the shipped app rather than of the paperwork, and each one is testable before submission:
- Age assurance. The app must prevent under-age users from using it, and it must carry an AO or IARC-equivalent rating. The form asks for that rating to be in place before the app is submitted for certification.
- Geo-restriction. The app must prevent access and use from countries, states, territories and geographic areas that the developer’s licence does not cover. A licence-scoped boundary in the client is therefore a requirement, not launch polish — the same build question the app geolocation architecture analysis addresses for the client generally.
- Price and payments. The app must be free to download, must not be sold as a paid app, and must not use Google Play in-app billing.
- Player-facing disclosure. The app and its listing must both clearly display information about responsible gambling.
The eligibility conditions also reach the listing rather than only the binary: the policy asks for placement in appropriate categories such as Games: Casino, Games: Card, Games: Sports, Sports or Entertainment, and the store supports those choices with its real-money gambling and games content policy. Where a brand’s platform decision is still open, the trade-offs between a native build, a wrapped WebView and an installable web app are the ones covered in the native app or PWA comparison, and the store gate is one of the costs on the native side of that comparison.
The other store’s rule is shorter, and it is not the same rule
Apple’s App Review Guidelines, last updated on 8 June 2026, answer the same question in a single paragraph. Guideline 5.3.4 requires apps that offer real-money gaming — sports betting, poker, casino games and horse racing are its examples — to have the necessary licensing and permissions in the locations where the app is used, to be geo-restricted to those locations, and to be free on the App Store; illegal gambling aids, card counters among them, are not permitted. Guideline 5.3.3 forbids using in-app purchase to buy credit or currency for use in connection with real-money gaming of any kind.
The part that matters to a launch plan is what the two published rules share and what they do not. Both make licensing and geo-restriction the operator’s duty and both require the app to be free. But the public guidelines state that duty without carrying the equivalent product-by-market table that Play’s form publishes, so an operator cannot read a country and product map out of Apple’s public guidance the way it can from the Play form. Any market plan built on one store’s map is therefore a plan for that store only.
The dossier to assemble before the build, not before the release
Every item below is obtainable before a line of the app is written, and each one has a cost when it is discovered late:
- The store’s map, intersected with the licence set — the countries and, in the United States and Nigeria, the states where the intended product types are supported.
- The licensee entity named on the application, and its identity with the developer account that will publish the app.
- The IARC rating and the degree of age assurance the build will carry, since the rating is asked for before certification is submitted.
- The geo-restriction mechanism and its evidence — how the client refuses a location the licence does not cover, and how that refusal can be demonstrated.
- The payment decision, made explicitly rather than by default: no in-app billing, no paid download.
- The responsible-gambling surface that will appear in the app and in the listing.
- The product scope statement — a list of the game types the app exposes, checked line by line against the licence, because an app may not offer more than the licence covers.
- The recertification trigger list — the ownership and licensing changes inside the organisation that will require the app to be filed again.
- A route for the markets the store does not support, decided on purpose, rather than left to be discovered at the point of a regional launch.
The ninth item is the one teams most often leave open, and it is answered below.
Outside the store is a route with its own gate
Where Play does not support a market or a product type, an operator can distribute an Android build outside the store, which the platform permits. That route is not unchanged. Android’s developer verification programme begins enforcement on 30 September 2026, from which point protections apply to apps installed from participating stores in select regions on certified devices, with a global rollout planned through 2027. Google Play registers the large majority of apps automatically, and the programme provides a separate registration route for apps distributed outside it, but the practical effect is that sideloaded distribution now carries an identity requirement of its own.
The trade-offs on that side — how players find the app, how updates reach them, and what the install path asks of a new customer — are the ones that make the store-versus-direct decision a product choice rather than only a compliance one.
What approval does not give you
It is worth stating the limits as clearly as the requirements, because the failure mode is treating a store approval as something it is not.
An approval is not a licence. The licence is held by the operator or developer and recognised by a regulator; the store’s approval adds the store’s own permission to distribute on its platform, and nothing more. It does not transfer between markets: each market is its own filing. It is not permanent — a change of ownership or of licensing requires recertification, and Google reserves the right to remove a gambling app from Google Play at any time. Under the store’s gambling terms, the developer also has to inform Google immediately if it becomes the subject of any ruling by its local gambling authority, another legal or regulatory authority, or an industry body that may be relevant to the app, and no binding agreement exists until Google notifies the developer that the application has been accepted.
And an approval says nothing about outcomes. Being listed is a condition of distribution in a market where the store supports the product; it is not evidence about retention, deposits or revenue, and it is not a substitute for the market-specific certification a game needs to sit in that market’s lobby at all, which the localised game certification evidence analysis covers from the content side. A commissioned title reaches players through a lobby that reaches them through a store, and both gates have their own paperwork.
A launch plan that treats market eligibility as settled before the build starts, and names the licensee, the licence scope and the store’s product map in one document, is cheaper than one that discovers the same three questions in the week the app is ready. Wizards plans market entry and go-to-market around market eligibility, channel constraints and the approvals a project still needs, which is where the store map belongs.
Questions operators, platforms and suppliers ask
Does Google Play allow a real-money casino app?
Yes, in the markets and for the product types the store supports, and only under an exception to its general prohibition on apps that facilitate real-money gambling. The developer has to complete Google’s application process and hold a valid gambling licence for each country, state or territory where the app is distributed. Online casino games are one of five eligible product types, alongside sports betting, horse racing where separately licensed, lotteries and daily fantasy sports.
Who has to be the licensee on the Google Play gambling application?
The licensee must be the same entity as the app developer or, in the case of a third-party application, the same entity as the operator. A licence held by one company and a developer account held by another is a defect in the submission rather than a technical problem, and it is worth settling before the build rather than during a review window.
How long does Google Play gambling app approval take?
The application form sets the expectation itself: gambling certification and app review should be expected to take at least a week or more. The form gives no service level beyond that, and the timing is per market, since each market is filed separately and each additional US state is a separate submission.
Which US states support a real-money casino app on Google Play?
Reading the application form’s table as published on 2026-10-10, online casino is supported in Connecticut, Delaware, Michigan, Nevada, New Jersey, Pennsylvania, Rhode Island and West Virginia, and Nevada’s listing is limited to poker. Several states are open for sports betting and closed for online casino. States not listed in the table are not supported for real-money gambling apps. The table is the store’s, and it changes, so it should be read again at the point of each submission.
Does the app have to block players outside the licensed markets?
Yes. The policy requires the app to prevent access and use from countries, states, territories and geographic areas that the developer’s licence does not cover, and to prevent under-age users from using it. Geo-restriction and age assurance are therefore properties the store checks in the product, not statements made in the paperwork.
Is a Google Play approval the same as being licensed?
No. The licence is held by the operator or developer and recognised by a gambling regulator; the store approval grants distribution on that store’s platform only. It does not transfer between markets, it does not survive a change of ownership or of licensing without recertification, and the store may remove a gambling app at any time. It is also not a claim about retention, deposits or revenue.
