Wagering app store compliance: what Australian operators face

Wagering app store compliance is one of the least-discussed operational friction points in Australian iGaming. Operators focus heavily on state licensing, ACMA obligations, and responsible gambling technology, but the rules imposed by Apple and Google on wagering apps are separate, privately enforced, and capable of pulling an operator's primary acquisition channel overnight. Understanding both sets of constraints, and how they interact, is now a basic competency for any Australian wagering product team.

How the two platforms approach wagering apps differently

Apple and Google both permit real-money wagering apps in Australia, but their frameworks differ in meaningful ways. Apple requires operators to hold a valid local licence before submitting a wagering app for review. Google Play's policy also mandates a territory-specific licence, and operators must apply separately for certification in each country where they want the app listed. Neither platform accepts an operator's word on compliance status. Both require documentation at the point of application and reserve the right to delist an app if licence status changes.

Apple reviews wagering apps through its App Store Review Guidelines under section 5.3, which covers physical gambling and real-money games. The review is manual for initial submissions and for major updates. That review timeline, which can run from 24 hours to over a week, creates operational risk for operators who need to push compliance-driven updates quickly. Google's process is broadly similar but applies through its gambling ads and apps policy, which is enforced by a separate certification team rather than the standard review queue.

What operators must document before submission

Both platforms require operators to submit proof of a valid gambling licence issued by the relevant Australian authority. For sports betting and wagering products, that means a Northern Territory licence issued under the Racing and Wagering NT framework or a state-issued licence where applicable. The documentation must be current. An app submitted with a licence that expires in the next 30 days will typically be flagged or deferred.

Beyond the licence itself, operators need to demonstrate geographic restriction capability. Apple and Google both require that real-money wagering apps are only accessible in jurisdictions where the operator holds a valid licence. For Australian operators, that means implementing IP-based geo-blocking and, where possible, device-locale checks that prevent the app from functioning in unlicensed markets. This requirement overlaps with the obligations that third-party account verification frameworks place on operators at the account level, but the app-store version applies before a player even registers.

Age gate requirements are also specified. Both platforms require a hard age verification mechanism within the app, not just at the point of account creation on the web. Operators who use a lightweight "confirm you are 18" checkbox during onboarding may find that insufficient for platform review purposes. A properly documented identity verification flow is the expected standard.

Where operators commonly get it wrong

The most common compliance failure is treating app store requirements as a one-time submission exercise rather than an ongoing obligation. Both Apple and Google reserve the right to conduct periodic audits of listed apps. An operator whose licence lapses, even briefly during a renewal process, risks having its app delisted without advance notice. Operators that have experienced this describe it as one of the most damaging customer-facing outages possible, given that mobile now accounts for the majority of Australian wagering sessions.

A second failure point is update management. Every substantive update to a wagering app triggers a new review. Operators who push app updates without accounting for platform review timelines can find themselves in situations where an app version that addresses a responsible gambling regulatory requirement is stuck in review while the older, non-compliant version remains live. Building review windows into product release schedules is not optional. It's a basic planning requirement.

Metadata compliance catches operators less often but creates issues when it does. App store listings for wagering products cannot contain promotional language that would breach Australia's wagering advertising rules. A listing that advertises a bonus offer or uses promotional copy directed at new customers may pass the platform's own review but still expose the operator to ACMA enforcement action under Australian advertising restrictions. The two compliance regimes don't speak to each other, so operators need both their platform team and their legal team reviewing listing copy before submission.

Responsible gambling requirements within the app

Both Apple and Google require that real-money wagering apps include accessible responsible gambling tools. Apple's guidelines specify that the app must include information about responsible gambling and links to support resources. Google's certification process asks operators to confirm that the app surfaces responsible gambling messaging and provides access to deposit or spend limits.

These requirements broadly align with what Australian state regulators already expect, but the platform layer adds its own enforcement mechanism. An app that passes Apple's review but subsequently removes its responsible gambling section in an update faces both potential delisting and regulatory exposure. Operators whose responsible gambling tooling is built correctly from the start, including deposit limits, session reminders, and self-exclusion access, are in a better position on both fronts simultaneously. The connection between sound responsible gambling technology and app store compliance is direct, not incidental.

What happens when an app gets delisted

Delisting is abrupt. The app disappears from search results and the download page returns a "not available" message. Existing installs typically continue to function in read-only mode or with limited functionality, depending on how the operator has structured server-side controls. Players who try to reinstall after a device reset or upgrade can't, which accelerates churn.

Reinstatement requires the operator to resolve the underlying compliance issue, resubmit documentation, and wait for platform review. That process has taken between 5 and 21 business days in cases reported by operators across regulated markets. During that period, the operator's mobile acquisition channel is closed. Paid search campaigns directing traffic to the app store listing produce dead links. Players who would have converted via app download are lost.

The practical answer is a pre-emptive compliance schedule: licence renewal tracked against app store documentation deadlines, responsible gambling tool audits tied to app update cycles, and a direct relationship with Apple and Google's gambling certification contacts where possible. Operators who treat app store compliance as a background task tend to find out it isn't.

Australian wagering is a mobile-first market. Keeping the channel open means treating the platforms that control it as regulators in their own right, with their own rules and their own enforcement timelines.