Skip to main content

Competitive Intelligence — Weekly Sync

📅 Week 4-5 — April 28, 2026 · ⏱ 30 minutes · 👥 Weekly cadence

1 · Competitive and Client Testing (Julia / Melissa) — Key Findings​

Radar Browser-Based Solution — Underdog DFS​

  • ✗ Location spoofing vulnerability — Chrome Browser Extensions undetected (Location Guard)
    Critical vulnerability identified. Free Chrome extension defeats geo without any technical skill.
  • ✗ Inaccurate device + user tracking — every login recorded as a new device. Inflates device counts and prevents the system from identifying multiple accounts sharing the same device — significantly weakening fraud detection and account controls.
  • ✗ Compliance gap at border crossings — users can continue placing wagers for approximately 1 minute after entering a restricted zone before Radar intervenes. Regulatory compliance risk.
  • ⚠ Increased geolocation frequency + fail rates — Without single-license support, Radar requires more frequent checks and generates unnecessary buffer-zone failures.
  • ⚠ Loss of meaningful error messaging — Following the switch from GeoComply, players now receive generic error messages for all geolocation failures, removing the ability to self-troubleshoot.

2 · Competitive Research (Valeria) — Key Findings​

Radar new release — v3.31.0 (iOS + Android, April 24)​

  • ⓘ v3.31.0 — SDK generates geofence events offline, without server
    When backend unreachable, the SDK generates geofence entry/exit events directly on the device from cached data, tagged as offline. Backend-toggled feature; unclear whether it will be used for gaming markets. Tracking intensity adjusts automatically based on geofence context — even mid-outage.

Watch point: validate whether these offline-generated events satisfy regulatory requirements or are used in regulated field integrations.

Mkodo GeoLocs​

  • Three confirmed spoofing failures from our own testing — RDP (AnyDesk / Assistant), iOS Emulator (XCode), and Fake Location App (iAnyGo) all undetected on live operators. Sessions also persisted 15–60+ minutes after location services were off, and cross-border sessions weren't terminated for 20+ minutes. Confirmed, repeatable findings — use them in any conversation where GeoLocs is being evaluated.
  • Canada: OLG, BCLC, AGLC, WCLC, ALC — mkodo built their apps and their geolocation. Don't compete for those. However, GeoLocs is already live in Alberta (AGLC + WCLC) before the regulated commercial market opens. GeoComply has no Alberta presence. This needs action now.

Locance (formerly LocationSmart) — 3 main points​

  1. Significant historical baggage — surface it every time
    2019: leaked real-time location data of all major US carriers without consent. Also a data source for Securus, used for illegal individual tracking without a court order. A separate vulnerability allowed bypassing opt-in location protections by switching request format. Their FAQ now defensively states "we do not sell location data." Bring this up in every competitive conversation.
  2. Their response format exposes their detection rules
    Results returned as plain JSON — fraud flag names are visible to anyone who receives a rejection. A fraudster can reverse-engineer exactly what triggered a block and adjust. GeoComply uses encrypted XML; detection logic is never exposed. Check count is unpublished; anti-spoofing capability (RDP, FLA, emulator) untested.
  3. Ontario-only footprint + compliance gap confirmed in testing
    All known clients in Ontario (LeoVegas, Royal Panda, Betway, Luxury Casino, Jackpot City). No US sports betting presence. Feb 2026 Luxury Casino Ontario: deposit went through before identity documents were verified. Pitch is 2-3 day integration + no download required — same wedge as mkodo.

3 · End-user Feedback (Valeria) — Key Findings​

📊 Full dataset: Social Media Competitive Signals · Reddit + X/Twitter public posts. Monitoring initiated March 2026.

  • GeoComply (FanDuel, DraftKings): KYC friction dominated — multi-week identity verification failures, accounts locked after first deposits, SSN submissions going unresolved. On the geo side, FanDuel is seeing location drops every 5 minutes during active sessions, and a Reddit thread on VPN bypass for DraftKings in restricted states is actively gaining replies.
  • XPoint Verify (Bet365, PrizePicks): Three new entries, all negative. Bet365 privacy backlash — users objecting to demands for SSNs, driver's licenses, and birth certificates, with one report of the sign-up submit button being broken entirely. PrizePicks logged a straightforward location error complaint on Twitter/X.
  • OpenBet (Fanatics): Two new KYC entries. Fanatics users report selfie/ID scans failing repeatedly on sign-up, and a separate account suspension immediately following a winning streak — funds held, bank statements submitted, no resolution. Consistent with the pattern of negative Fanatics/OpenBet sentiment tracked since February.

4 · What's Next — Plan for Next Week​

Field Testing​

  • Fanatics / OpenBet Locator — finish validation of the integration
  • Ontario Competitor Analysis — validate current competitor integrations (Mkodo, LocationSmart) in Ontario in anticipation of Alberta launch
  • Radar / Saracen AR, XPoint, Radar / Bet365 — run Replay Attack testing
  • GPS Simulator — test location spoofing on Radar & XPoint with GPS-simulator device

Betting Hero​

  • Radar / Saracen AR (web desktop) — perform static connection validation of the competitor's app

Integrations team​

  • TBD