Skip to main content

Competitive Intelligence — Weekly Sync

📅 Week 6 — May 5, 2026 · ⏱ 30 minutes · 👥 Weekly cadence · 🔖 Monthly Brief

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

Radar Browser-Based Solution — Saracen AR​

📹 Full video: BetSaracenFullTestingSession.mov (21 min, internal Drive)

OpenBet Locator iOS + Android SDKs — Fanatics TN​

  • ✗ Remote Access detection gaps — HopToDesk + iPhone screen mirroring bypassed
    Users outside Tennessee borders successfully wagered on the local platform via both Android and iOS. Substantial compliance + fraud-prevention risk.
  • ✗ Absence of State Border Buffer Zones — Players within 50m of the boundary experience frequent state-switching, enabling unauthorized cross-border wagering. Persistent page refreshes + inability to finalize cash-out.
  • ✗ Failure to Monitor IP Changes — System fails to flag IP address changes during active user sessions. Critical spoofing indicator missed.
  • ⚠ VPN Restriction Protocols — Aggressive VPN blocks risk false positives for legitimate corporate-network users.

2 · Competitive Research (Valeria) — Key Findings · MONTHLY BRIEF​

Gaming competitor research has proven its value​

Source analysis and behavioral testing surfaced real, confirmed vulnerabilities in every competitor we analyzed:

  • Radar — client-side compliance decisioning, an open-source unobfuscated SDK, and GPS injection methods in its public API.
  • XPoint — returns compliance decisions and raw coordinates in plaintext to the client with a public GPS injection method.
  • GeoLocs — missed RDP, FLA, iOS emulator, and IP change detection in live testing, with sessions persisting 15–60+ minutes after location services are disabled.
  • Locance — allowed a deposit before document verification in live testing, and exposes fraud flag names in plaintext JSON responses.
  • OpenBet — missed HopToDesk and iPhone screen mirroring with no border buffer zone.

15 test cases + SDK review tickets queued​

  • XPoint jurisdictionArea field investigation
  • Full GeoLocs retest suite (RDP, FLA, emulator, session persistence, cross-border, VPN mid-session)
  • First-ever Locance spoofing tests (RDP, FLA, emulator, JSON flag exposure)
  • Magisk bypass on Bet365 / XPoint Verify
  • Radar SDK tickets for iOS + Android teams to assess client-side decisioning and on-device signal storage vulnerabilities

Three open questions for the group​

  1. Do we start structured competitor research for non-gaming verticals?
  2. Do we need a dedicated KYC research track? KYC friction is now 23% of all end-user complaints in our monitoring data, and we have no testing on IDComply competitors (Shufti Pro, Sumsub, Socure). We do not yet have a list of competitors + the operators they assist.
  3. What is our next gaming research priority? Waiting for all tests to be conducted, but is there a specific area we need to dig into for each competitor (pricing models / adv models / etc)?

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

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

Location verification failures dominate​

38% of all findings. DraftKings (11) and FanDuel (9 mentions) generate the highest complaint volumes across March 30 → April 27. Top reported issues:

  • DraftKings — app lag causing re-verify loops
  • FanDuel — location dropping mid-session

Both patterns consistent with geo-check frequency friction, not outright failures.

QUESTION: Do we want to contact our clients about feedback, and if so, how do we want to approach them?

Circumvention attempts are growing in sophistication​

Present in every weekly report. Flags rose steadily from 2 to 3 per week. The community has moved beyond basic VPN queries to peer-sharing GPS spoofing and mock location methods on Reddit. An active DraftKings VPN bypass thread was still gaining replies in the April 27 report.

ACTION ITEM: All spoofing cases (even implied) should be reported to the testing team to reproduce. Claimed DraftKings Magisk bypass — test already requested.

KYC friction (23% of findings)​

Secondary but growing concern concentrated at Fanatics and DraftKings — duplicate account suspensions, document rejection loops, 2+ week verification delays, SSN privacy objections. Not geo issues — but they create halo damage: users conflate geo lockouts and KYC holds into a single "the app won't let me play" complaint.

QUESTION: Do we want to perform KYC competitor research? Do we want to have a list of all geolocation operators and their known KYC, with added feedback about every KYC provider?

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

Field Testing​

  • Ontario Competitor Analysis — validate current competitor integrations (Mkodo, LocationSmart) in Ontario in anticipation of Alberta launch
  • Radar / Saracen AR, XPoint, Radar / Bet365 — run the Replay Attack testing
  • GPS Simulator — test location spoofing on Radar & XPoint with GPS-simulator device
  • RobinHood — RAT
  • FD WV / Radar — Spoofing testing with PlayCover
  • Device farm VMOS — FD WV, Fanatics, BetRivers

Betting Hero​

  • UX testing for Betsson Brazil
  • Competitor Intel: 7kBet (Incognia), Bet.bet (Legitimuz), Estrella Bet (Radar), Oley Bet (internal)
  • Locance (LocationSmart) — Full Validation
  • mkodo Geolocs — Full Validation

Integrations team​

  • TBD