GAMSTOP on an iPhone: what it blocks and what it does not

That raises the practical question of what the registration stops on a phone that already has the app installed.

The answer is no. The national multi-operator self-exclusion scheme does not delete applications, does not alter iOS system permissions, and does not stop Safari from rendering a web page. The block lives in a completely different layer of the infrastructure.

What registering actually switches off

When a person registers with the national multi-operator self-exclusion scheme, the administrative machinery targets accounts rather than devices. Under provision 3.5.5 of the licence conditions and codes of practice, the Gambling Commission places the duty of compliance entirely on the gambling business. Participating in the scheme requires the operator to query the central register and prevent the excluded individual from accessing facilities for gambling.

The scheme describes what registering does as blocking the person's access to accounts on gambling websites and apps. That block operates remotely across the server networks of participating businesses. When a user submits identification details to log into an existing profile or attempts to register a new account, the operator checks those customer details against the central database. If the record matches, the operator closes the session, denies account creation, or refuses the login attempt.

The technical reach of the service ends at the operator's digital border. The national scheme is a shared database registry. It contains identity markers that licensed remote operators must check under the rules of their licence. It does not possess access to Apple's App Store, cannot issue commands to the iOS operating system, and cannot monitor network traffic passing through an individual iPhone. The scheme supplies no software for the handset and nothing is installed on the phone.

Because the regulatory mechanism operates at the account stage, the enforcement check only occurs when a user interacts with an account system. If an online action does not require authentication, the operator's servers have no reason to inspect the national register. A person can view sports fixtures, examine casino promotional material, check fluctuating odds, and read game rules without interference, because those pages are public assets delivered before any account validation happens.

What stays on the phone afterwards

A user who completes registration will find their iPhone storage and home screen completely unchanged. Every gambling application installed prior to registration remains functional as local software.

The visible symptoms on the phone follow from this separation between the device and the account:

• Installed applications launch normally and load their standard visual assets.
• Mobile browsers load gambling websites and display live odds, account interfaces, and game graphics.
• The App Store continues to display gambling applications in search results and permits new downloads to the handset.
• The block occurs only when the user submits their details to log in or attempts to open a new account.

An iPhone manages applications as isolated packages of code. The operating system does not evaluate the regulatory status of a developer, nor does it check whether the device owner is listed on an exclusion database. When a user taps an application icon, iOS executes the local data stored on the handset. The app establishes a network connection to retrieve images and interface text from the company's servers. Those assets load because public content delivery networks do not require account verification.

The failure point arrives when the user enters a username, email, or password. At that moment, the application sends a request to the operator's authentication server. The operator runs the identification details against the national multi-operator self-exclusion database, recognizes the exclusion, and returns an instruction denying access. The application does not crash or disappear. It simply remains open on the screen, displaying a rejected login notification.

Web browsing behaves the same way. Safari requests data from web servers and renders the code it receives. A gambling operator's website is a public site that returns content to any standard web request. The exclusion scheme is not a domain filter, a DNS reroute, or a network firewall. The web page loads completely because the restriction does not belong to the site itself; it belongs to the account record stored inside the operator's private database.

The gaps the provision is not written to close

Because the scheme is enforced through Gambling Commission licence conditions, its jurisdiction matches the legal boundaries of those licences. Provision 3.5.5 applies directly to remote licences, but the text includes specific statutory exceptions.

The licence conditions state that mandatory participation in the national multi-operator self-exclusion scheme applies to remote licences with listed exceptions. Among these listed exceptions are:

• Remote lottery licences that do not offer instant win lotteries.
• Remote general betting (remote platform) licences.
• Ancillary remote bingo licences.
• Ancillary remote casino licences.

These categories do not have to integrate the multi-operator self-exclusion scheme under provision 3.5.5. An account held with an operator running exclusively under an exempt ancillary licence or a non-instant lottery licence does not interact with the central database in the manner of a standard commercial betting or casino licence.

The regulatory boundaries have also shifted over time. From 1 April 2024 remote operators that take bets placed over the telephone or by email are also required to implement the scheme. Before that date, direct off-platform transactions handled by phone or email operated under separate procedural arrangements. The Commission's update brought those remote communication channels under the mandatory verification requirement, obliging operators to cross-reference customer details before accepting bets through non-automated channels.

The broadest limitation is jurisdictional. The licence conditions and codes of practice govern entities that hold a Gambling Commission licence. An operator that does not hold a Gambling Commission licence is not bound by the provision, because the LCCP binds licensees. Unlicensed operators have no regulatory link to the British statutory framework, do not receive data from the national scheme, and do not cross-reference their account registrations against its records.

Where a handset-level block does a different job

Preventing an iPhone from opening gambling software or visiting gambling domains requires a handset-level restriction. This is a separate mechanism with a different owner and a different architecture. While statutory self-exclusion relies on remote businesses checking customer identities, device-level filtering operates directly within iOS.

On an iPhone, web filtering sits in Screen Time under a child's Apps & Websites settings. Apple provides specific tools within that menu to manage internet access:

• Limit Adult Websites, which applies automated device filters to restrict access to adult content.
• Approved websites only, which cuts off general browsing and permits navigation solely to an explicit list of allowed domains.
• The Block Website setting, which allows an administrator to block an individual site by entering its exact URL.

These settings act locally before a web request leaves the device. If a domain is listed under Block Website, Safari intercepts the connection on the phone, preventing the site from loading or transmitting interface code to the screen.

The operational ownership of this system is distinct. A handset-level restriction belongs to whoever holds the Screen Time passcode. A blocked app or website can be unblocked at any time simply by entering that passcode and changing the setting back.

This direct reversibility separates device controls from the national multi-operator self-exclusion scheme. Provision 3.5.5 establishes an external, operator-enforced obligation that removes account access across participating remote licensees without touching the phone. Apple's Screen Time provides local content filtering that changes what the handset can display, governed entirely by the device passcode and subject to immediate alteration by whoever enters it.