GeoLocs / mkodo at OLG iOS: session terminated immediately when device location services are disabled ✓
Source. May 26, 2026 weekly sync.
Ticket. CIV-52: Ontario — mkodo / GeoLocs — Compliance Failures & Retest.
What we tested
Whether the OLG iOS app (GeoLocs / mkodo geolocation) would correctly refuse to operate when device location services were turned off — i.e. the most basic compliance pre-condition (no location signal → no wager).
What happened
- ✓ Session was terminated immediately on detection of disabled location services.
Why it matters
The baseline check works. A platform that allows wagering with no location data is unambiguously non-compliant; this vendor correctly refuses, on iOS, at session start.
That said — pair this with the OLG / GeoLocs VPN gap recorded the same week: the vendor does enforce when the device claims to be unable to locate, but falls down when the device claims to be located somewhere it isn't. The two findings together describe the shape of the gap: GeoLocs trusts the device's location signal too uncritically when that signal is present.
Cross-reference
- OLG ON (GeoLocs / mkodo) — VPN-from-Ontario allowed + Netherlands VPN late detection (May 26) — same vendor, same operator, opposite outcome.
- High Flyer Casino TN (GeoLocs / mkodo) — iOS + Android spoofing bypass (May 26) — vendor failure pattern on a second operator the same week.