
Image by Leopold Varga
In the version of its App Review Guidelines that Apple published on October 16, 2026, guideline 5.3.4 tied every real-money gambling app to a place. An app offering poker, casino games, sports betting, horse racing or lotteries needs licenses and permissions for the locations where it’s used, and Apple requires it to block use everywhere else.
That rule belongs to the app-store layer, one of three that decide where a person can gamble online. The layer most people have heard of is the state-line check a licensed US gambling app runs on the phone’s position before it accepts a bet. The third is the commercial IP database that tells an ordinary website which country a connection seems to come from.
A phone meets the storefront first, and offshore crypto casinos don’t get past it. For a gambling site with no app, the next check runs on the IP address, a location signal a website receives without asking.
Apple checks the account’s country before it checks the phone
Apple sells apps through 175 country or region storefronts. Its App Store Connect help pages say a customer’s Apple Account country or region setting decides which storefront they can buy from; an account set to Japan, in Apple’s own example, can only buy from the Japanese App Store. Developers pick their storefronts country by country, and Apple warns them that an app may not be available in some places because of legal or regulatory requirements.
That first filter is a setting on an account. It says nothing about where the phone is sitting. Guideline 5.3.4 adds a second filter. A gambling app may only work in the places its licenses cover, so it has to know where the device is, whichever storefront it came from. Apple’s privacy rules reach that step too. Guideline 5.1.5 tells developers to notify users and get their consent before they collect, transmit or use location data.
A gambling app on an iPhone therefore faces two location checks, the account’s country when it’s downloaded and the handset’s position when it’s used.
Apple also narrows who can apply. Under guideline 5.1.1(ix), an app in a highly regulated field such as gambling should come from the legal entity that provides the service, not from an individual developer.
Google’s application form names 45 countries and keeps a state table
Google Play writes its map down. A real-money gambling app gets onto Play only through Google’s gambling application form, which names 45 countries where licensed apps can be distributed. Every country, or US state, the app goes to needs its own valid gambling license, and the app has to refuse use from any area that license doesn’t cover. Google tells applicants to expect certification and review to take at least a week.
Inside those 45 countries the rules split again by product. Google’s page of country allowances lists sports betting and lotteries for Australia, with no online casino games, and its entry for Germany leaves online casino games out as well. Canada is cut into three pieces. Ontario and Alberta list sports betting and online casino games with no government-only condition, while every other province gets those products from government operators only.
The United States gets a state-by-state table on the form itself. Online casino apps have a tick in seven states (Pennsylvania, New Jersey, Michigan, West Virginia, Rhode Island, Connecticut and Delaware), Nevada has one for poker only, and Google says it doesn’t support real-money apps in states the table leaves out. Each application covers one app in one state, so a developer who wants a second state files a second form.
An offshore license has no place on either store’s form
Both stores work from a map of permission, drawn around the places an app’s licenses cover, and the app has to stay inside it. Offshore crypto casinos tend to draw their maps the other way round. They take players from anywhere outside a restricted-country list in their terms, and for most of the places on such a map they hold no local license either form could accept.
A thin app that wraps a casino’s website fares no better on Google Play. Among the policy’s examples of violations are apps whose menu items, tabs, buttons or webviews invite users to wager real money.
When the crypto-casino comparison page at https://www.bestbitcoincasino.com/ explains in its mobile section why none of its listed casinos has a real-money app in either store, guideline 5.3.4 is the rule it cites. The casinos run in a mobile browser instead.
In that browser, a restricted-country list in each casino’s terms decides who may open an account, and the page names the United States first among the countries those lists exclude. No US state licenses an offshore crypto casino.
No reviewer at Apple or Google has looked at a license or an age rating for these sites. Each site enforces its restricted-country list by itself, with whatever location signal reaches it through the browser.
A web page reads the IP address without asking permission
A site open in a mobile browser has two ways to place a visitor, and only one of them involves a question. The W3C’s Geolocation specification calls location a powerful feature that requires express permission before any location data is shared with a web application, which is why browsers put up a prompt. The IP address needs no prompt at all. It travels with every request the phone sends.
Geolocation vendors sell that signal for exactly this kind of decision. MaxMind lists iGaming and jurisdiction enforcement among the compliance uses of its GeoIP data, and the check it describes for iGaming allows or denies a connection based on licensed territory, starting from the country’s ISO code and the subdivision code beneath it. Some of its products attach a confidence percentage to the country value, so a site can treat a shaky answer differently from a firm one. MaxMind’s own example falls back from the city to the subdivision level when city confidence drops below 50.
How often is the country right? MaxMind’s geolocation accuracy page estimates that its GeoIP products identify users at the country level with 99.8% accuracy, which leaves about 2 lookups in every 1,000 pointing at the wrong country. For US addresses the same page puts accuracy at around 80% for the state and 66% for the city, measured within a 50-kilometer radius.
A restricted-country list, then, asks the IP data for the one answer it gives most reliably. Drop a level, to the state, and one lookup in five would land somewhere else.
Registry country codes record where an address holder is based
The country code a vendor returns doesn’t come straight from the internet’s address registries, and the registries say so. The statistics exchange format that the regional internet registries use to publish their allocations, documented by RIPE NCC, defines the country field as the country where the resource holder is legally based. The same document adds that it isn’t specified whether that’s where the addresses are used, so the field can’t reliably map IP addresses to countries.
Vendors fill the gap with their own data, and phones are where it gets hardest. MaxMind’s accuracy page says addresses on mobile networks may be used by phones across a large distance; for an address used across Massachusetts, it returns the country and the state but no city.
A GIS User guide to impossible-travel checks made the same point on November 5. A mobile IP may point to a carrier gateway, the guide noted, and carriers rotate addresses; a phone can even switch between gateways hundreds of kilometers apart while its user stays in one place.
Borders bring their own edge cases. MaxMind says it follows ISO in almost all cases to decide which country a subdivision belongs to, even where a region is disputed, and that the choice isn’t a political position. A restricted-country list enforced with that data inherits the choice for anyone connecting from such a region.
The data also ages. MaxMind releases a new GeoIP Country database every weekday, and its terms require customers to use updates promptly and delete outdated copies within 30 days. For a site enforcing a restricted-country list, the answer for one address can change between a Monday and a Tuesday.
None of that edits a casino’s terms. The restricted-country list in them says who may hold an account, and a stale or mistaken lookup leaves that list as it was.
Maine’s row in Google’s state table is still one column short
Maine is the next US state where the storefront layer looks set to change. LD 1164 became law on January 11, 2026, without Governor Janet Mills’ signature, and gave the state’s four Wabanaki Nations exclusive rights to online casino gaming. Google’s state table still lists Maine for lottery and sports betting apps only, and the form says Play doesn’t yet support distribution of a gambling type that isn’t listed for a state.
Under Maine’s framework, as G3 Newswire reported on November 17, each of the four nations can hold one iGaming license and partner with no more than one licensed management-services provider. That caps the state at four online casino licenses. An app from any of them would need its Maine license before guideline 5.3.4 lets it run there.
Google’s form already covers one state where online casino gaming belongs to tribes. Its Connecticut entry notes that the state lottery’s master wagering license doesn’t cover online casino gaming, which is open only to the Tribes and their online gaming partners.
The Maine Gambling Control Unit has estimated that the market will likely go live in the first quarter of 2027, though no official date has been set. When it does, an Android app for that market will also need Google to put a tick in the online casino column of Maine’s row, which shows a cross today.