The flag is about your IP, not your intent — and half the culprits aren't apps you'd call a VPN.
DraftKings Says VPN Detected But You Don't Use One: What Triggers the False Positive

The short answer
DraftKings flags "VPN detected" whenever your IP address doesn't match your physical location — and several tools trigger that without being a VPN you knowingly installed: iCloud Private Relay, corporate or school VPN profiles, ad-blockers with built-in VPN (AdGuard, Blokada, NordVPN's DNS mode), remote-desktop software, and hotel/airplane Wi-Fi that routes traffic through a remote gateway. Check Settings > VPN on your device — a profile can exist and run even if you forgot installing it.
In this article
When DraftKings (through GeoComply) detects a VPN, it means the IP address your traffic exits from disagrees with your GPS/Wi-Fi position. The system can't tell a privacy tool from a spoofing attempt — anything that relocates your IP looks identical. That's why the error so often appears for people who never installed a VPN: several legitimate tools move your IP without calling themselves one.
The six false-positive triggers
- iCloud Private Relay (iPhone/Mac): Safari traffic exits through Apple relays, not your real IP. Settings > [your name] > iCloud > Private Relay > off.
- A VPN profile you forgot: employers, schools, and even some antivirus apps install VPN profiles. iPhone: Settings > General > VPN & Device Management. Android: Settings > Network > VPN. If anything is listed and connected, that's your flag.
- Ad-blockers with VPN profiles: AdGuard, Blokada and similar blockers route traffic through a local VPN interface to filter it. GeoComply can't distinguish that from a real tunnel.
- Remote-desktop software running in the background (TeamViewer, AnyDesk, Chrome Remote Desktop, a VM) — flagged as remote control even if you're not using it this second.
- Hotel, airplane and some campus Wi-Fi: these route all guest traffic through a central gateway, sometimes in another state entirely.
- IPv6 tunneling or a carrier that NATs traffic through an out-of-state gateway — rare, but it happens on smaller MVNO carriers.
How to clear it
Check the device's VPN screen first — that's where forgotten profiles live. Turn off Private Relay if you're on Apple hardware. Quit remote-desktop tools fully (system tray, not just the window). Switch from hotel/public Wi-Fi to cellular, which gives you the carrier's local IP. Then force-quit the app and retry — the flag doesn't clear mid-session, it re-checks on a fresh connection.
If every one of those is clean and it still flags you, contact support and say exactly that — they can see which IP class flagged and can whitelist-clear the block after confirming your location independently.


