Skip to main content

Competitive Intelligence — Weekly Sync

📅 Week 1 — March 24, 2026 · ⏱ 30 minutes · 👥 Weekly cadence

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

  • ✗ Radar / FD WV — GPS simulator device from Vietnam bypassed verification
    Hardware GPS spoofer — entry-level attack class. Accepted spoofed coordinates.
  • ✗ Radar / FD WV — rooted Android (hidden root) not detected. Re-test from TN with all root-hiding steps confirmed.
  • ✗ Radar / Saracen AR (desktop) — Chrome-incompatible Verify + no bet within 1km of AR border
    Radar Verify doesn't work on Chrome (Win + Mac). Radar bounced between "State not Allowed" and "Buffer Zone" errors.
    🎫 CIV-20 — Saracen Arkansas / Radar: conduct full competitor validation
  • ⚠ PA regs — some clients are not compliant: FD, DK, Pala didn't integrate any soft checks; RSI, MGM, Penn didn't integrate Registration checks. 📎 PA_Regulations.xlsx
  • ⚠ BetMGM iOS app — lacks the high-speed fluidity of benchmarks; cumulative 1–2 second delays.
    🎫 CIV-30 — test BetMGM Casino app loading times.
  • ✓ BetMGM battery testing (TN/NY) — both latency and battery performance operating as expected. Elevated battery usage on older devices = hardware constraint, not product defect.
    🎫 POI-10239 — [iOS] BetMGM testing for latency and battery.
  • ✓ ARB Gaming US iOS — validated in VA. IP Change fix signed off on production.
  • ⚠ VGW AU (pre-launch) — validated in PA. Compliance issue / undercalling observed; intervals calculation under investigation.
    🎫 BO-18417 — VGW AU "geolocate_in" varies because of differently calculated "dist_to_b..."
  • ⚠ LotterySmith Oregon (pre-launch) — compliance issue / failed response not respected.

2 · Competitive Research (Valeria) — Key Findings​

  • Xpoint — we were able to obtain raw iOS and Mac SDKs of Xpoint, which allowed us to do deep analysis of their logic: they only use clientKey per session at runtime without any license expiry, return JWT token response, and re-geolocation happens automatically.
  • Xpoint SDK also returns a jurisdiction in the response which potentially allows easier handling of multi-state operators. Environment type is also handled via a simple method without the need to switch licences — potentially much easier for developers and testers.
  • Radar uses tracking rather than periodic checks with non-gaming clients which allows them to be more flexible, providing real-time triggers on entering or leaving the geofencing zone.
  • Radar has aggressive marketing — returns on searches for GeoComply, OpenBet, Xpoint where their site has pages "What is the best Xpoint/OpenBet/Geocomply alternative?". They position themselves way more developer-friendly due to open documentation and mocking testing tools available.

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

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

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

Field Testing​

  • Radar / FanDuel WV — Assess the effectiveness of Play Integrity API detection against a hidden root device. Assess Radar's ability to detect a coordinated spoofing attempt combining a new account, residential router VPN, and GPS emulation.
  • Spoofing testing scope — Define more spoofing tests together with the mobile SDKs teams. Radar - review testing scope - 2026/03/24 07:25 CET — Notes by...
  • PA regs — validate if the operators correctly trigger geolocation at adding new funding method
  • Bally NY — run a full review of the performance

Betting Hero​

  • Radar / Saracen AR (desktop) — perform full validation of the competitor's app
  • FanDuel PA — Conduct end-to-end testing of registration, deposit, and withdrawal flows to confirm whether and how Radar API calls are implemented, identify any proprietary geolocation checks, and verify compliance with PA regulations requirements.
  • XPoint / RushStreet DE — conduct validation of the XPoint integration
  • BetMGM — latency and battery drain — compare SB vs Casino performance, iOS & Android

Integrations team​

  • OpenBet Locator analysis
  • Define the usages of Xpoint 'jurisdiction' field
  • Define states to test Fanatics OpenBet Locator implementation