Private Relay, VPNs and why a UK casino locks you out
1 of the Gambling Commission's Licence Conditions and Codes of Practice, every gambling operator taking bets in Great Britain must obtain and verify a customer's identity, including name, address and date of birth, before permitting that person to gamble. The licensee is also barred from demanding additional identity documents as a condition of a withdrawal if it could reasonably have asked for them earlier.
On this page — contents
Yet thousands of account holders who have satisfied every verification check find themselves suddenly locked out at the login screen.
The lockout occurs because verified identity and live network location are entirely separate inputs. When a player opens Safari on an Apple device and sees a prompt saying the casino cannot verify location, iPhone Private Relay users often assume their identity verification has failed. It has not. The friction is network-level, caused by privacy architecture masking the connection.
What the site is reading when it decides where you are
A regulated gambling site relies on two distinct sources of customer information to decide whether to accept a wager. The first is the verified customer profile established under licence condition 17.1.1. That profile confirms the physical person who registered the account, proving their full name, residential address and age through documentation checked before play begins.
The second source is the incoming network address arriving with every web request. Under the Gambling Act 2005, only a Gambling Commission licensee may lawfully offer gambling to customers in Great Britain. Beyond the baseline statute, an operator's own published terms and conditions govern where it will accept play from, defining the geographic territories from which a customer may connect and place bets.
When an account holder attempts to log in, deposit or place a wager, the operator reads the network address transmitting the traffic. If the incoming connection appears from a region outside the boundaries specified in the licensee's published terms, or if the network data fails to demonstrate a clear point of origin, the site blocks the session.
This creates an immediate split between who the customer is and where the connection appears to be. A customer can possess an account verified with a domestic address, full documentation and an active balance, yet find their access blocked instantly because the live data packet carries an obscured network identifier.
Private Relay and the temporary address
For iPhone and Mac users browsing the web, the most common source of masked network data is iCloud Private Relay. Available as part of an iCloud+ subscription, the feature is engineered to protect privacy when browsing in Safari by separating web traffic across two distinct points of transit.
When a user navigates to a website with Private Relay enabled, the request is encrypted. The request passes through two separate relays. The first relay is operated by Apple, which sees the user's original IP address but cannot see the destination website the user wants to visit. The encrypted traffic is then forwarded to a second relay, operated by a third-party content provider.
This second relay does not know the user's true identity or original IP address. Instead, the third-party content provider will generate a temporary IP address before connecting to the site.
The gambling operator's server receives the incoming connection from that generated, temporary address rather than the direct connection provided by the user's local internet provider. Because the second relay assigns a temporary address designed to obscure the user's specific connection path, the website cannot resolve a stable, verified network origin.
Apple's own support documentation confirms this consequence, stating that without access to your IP address, some websites may require extra steps to sign in or access content. Apple also notes that Private Relay is not available in all countries or regions. When an operator's platform detects traffic arriving through a relay architecture that masks the true IP address, its automated controls reject the connection to prevent transactions from unverified territories.
Turning it off for one network and nothing else
Resolving a Private Relay lockout does not require disabling iCloud+ or stripping away privacy across all internet browsing. Apple provides a granular toggle within iOS to disable the relay mechanism for a single connection via the Limit IP Address Tracking setting.
Adjusting this setting instructs the device to route Safari traffic directly through that specific network rather than through the two-hop relay architecture.
For a Wi-Fi connection, the adjustment is made through the following sequence:
- Open the Settings app on the Apple device.
- Select Wi-Fi from the primary menu list.
- Tap the More Info button beside the connected network name.
- Locate Limit IP Address Tracking and switch the toggle off.
For a cellular connection, the process depends on the software version running on the device. On current operating systems, open Settings, tap Cellular, select the primary phone number listed under SIMs, and turn off Limit IP Address Tracking. On devices running iOS 18 or earlier, this control sits under Cellular Data Options inside the Cellular menu.
Two technical conditions apply to this setting. First, changing the Limit IP Address Tracking setting on a network applies to all of the person's devices on which Private Relay is turned on. Second, each distinct connection is configured independently. If a device connects to a second SIM, a separate Wi-Fi network or an Ethernet interface, the setting must be adjusted on that individual connection to allow direct routing.
Private Relay can be turned back on for that network from the same place whenever the user chooses. When the feature is turned off for a network or website, the user's network provider can see which site is being browsed, because traffic routes directly rather than through Apple's dual-relay structure.
Why a VPN turns a location problem into a terms problem
While iCloud Private Relay is a Safari-specific privacy toggle that substitutes a temporary IP address, a virtual private network (VPN) presents a fundamentally different challenge for account holders.
Private Relay operates within the user's approximate regional boundary by default, using temporary addresses to shield browsing identity. A VPN deliberately tunnels all device traffic to an intermediate server, often in an entirely different jurisdiction, substituting the remote server's IP address for the user's true physical location.
This distinction separates a temporary browser friction from a contractual breach. Under the Gambling Act 2005, the regulatory perimeter is absolute: only an operator holding a licence from the Gambling Commission may lawfully offer gambling to consumers located in Great Britain. Licensees construct their operations around this mandate, incorporating clear geographic restrictions into their published terms and conditions.
Those published terms define where a licensee will accept play from, barring customers from placing wagers or managing accounts from excluded territories. When a player routes traffic through a VPN, the connection appears on the operator's servers as an access attempt from the location of the host server.
If that server sits in a region where the licensee's published terms exclude play, the connection violates the agreement between the customer and the site. No local software toggle or device preference resolves a terms violation.
While a user facing an iCloud Private Relay lockout can restore direct network visibility through the Limit IP Address Tracking setting, an account blocked for violating territorial rules in an operator's terms faces administrative closure under the operator's contractual policies.
Written and maintained by the i-phonecasino.co.uk desk. Licence status comes from the UK Gambling Commission public register; bonus figures, wagering and withdrawal rules come from the operator’s own published terms on the day shown below. Where a number is not published, this site leaves the field out rather than estimating it.
Last checked . Spotted something out of date? Tell the desk.