Locance (LocationSmart) / Luxury Casino Ontario: cross-border play, RDP, and Android VPN gaps; Mac VPN blocked
Source. June 16, 2026 weekly sync.
Ticket. CIV-54: Locance (LocationSmart) — full validation.
What we tested
Integration validation of Locance (LocationSmart) on Luxury Casino Ontario — cross-border movement between Ontario and Quebec, remote access (TeamViewer, AnyDesk, HopToDesk on desktop and Android), VPN usage across Mac / Android / iOS, and near-border location accuracy on iOS.
What happened
| Area | Result | Notes |
|---|---|---|
| Cross-border play (ON ↔ QC) | ✗ Non-compliant | Wagering was possible for multiple kilometres across the provincial boundary in both directions with no friction. |
| Remote access (TeamViewer, AnyDesk, HopToDesk) | ✗ Undetected | Gameplay continued with active remote control on desktop and Android solutions with little to no friction. |
| VPN — Mac | ✓ Detected | VPN / proxy usage was identified; platform access denied. |
| VPN — Android | ✗ Undetected | Active VPN tunneling was not blocked; user authenticated and wagered. |
| VPN — iOS | ⚠️ Blocked, no UX | Access was denied with VPN enabled, but no error message or troubleshooting guidance was shown. |
| Near-border UX (iOS) | ✗ Poor accuracy | ~100–150 m from the border the app placed the user in Quebec despite a physical Ontario location. |
Why it matters
Locance failed on the two vectors regulators care about most on a border-adjacent Ontario deployment: jurisdictional containment (cross- border play for kilometres) and remote session control (three major RDP tools undetected). VPN handling is inconsistent across platforms — Android is fully open, iOS blocks silently — which is both a compliance gap and an operator-support problem. The near-border mis-location suggests geofence accuracy degrades exactly where enforcement should be strictest.
Cross-reference
- Locance / Luxury Casino Ontario — remote-access block fails on retry (June 8, CIV-53) — prior retest on the same operator; retry-fragile remote block.
- Locance Ontario — KYC gap + detection rules exposed in API (June 2, CIV-53) — compliance finding on the same provider from the prior cycle.