GLI-33 geolocation + mobile + internet wagering security. GEOLOCATION VERIFICATION: in regulated jurisdictions (US states + provinces) wager acceptance must be CONTINUOUSLY GEO-VERIFIED to ensure player is physically within authorized boundary; typical implementation uses third-party geolocation provider (GeoComply + Xpoint + Locator-X + IDology Position + others - often GLI-19 certified separately); verification methods include GPS + Wi-Fi triangulation + cell tower + IP + LBS + device sensors + spoof detection (VPN + proxy + emulator + jailbreak + GPS spoofing); CONTINUOUS RE-VERIFICATION typically every 5-15 minutes during active session + at every wager submission; FAILED VERIFICATION must block wager + may suspend session. MOBILE WAGERING SECURITY: app distribution via App Store + Google Play with regulator-approved hash + integrity check + jailbreak/root-detection + emulator-detection + tamper-resistant device-binding; secure communication (TLS 1.2+ + certificate pinning); secure storage (Keychain + Keystore); app-update lifecycle + forced-update for regulatory or security patches. INTERNET WAGERING SECURITY: web-app same protections + CSP + frame-ancestors + HSTS + cookie security + session-management; WAF + DDoS protection; bot-detection (Cloudflare + Akamai + DataDome + Imperva); credential-stuffing protection; account-takeover detection. SESSION MANAGEMENT: session timeout + reauthentication + concurrent-session-limits + IP-change + geolocation-change triggers + MFA for high-value actions (withdrawals + profile changes + responsible-gaming-limit changes).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.