Skip to main content

Competitive Intelligence — Weekly Sync

📅 Week 9 — May 26, 2026 · ⏱ 30 minutes · 👥 Weekly cadence

Agenda​

#Topic
1Competitive and Client Testing — Key Findings
2Competitive Research — Key Findings
3Win/Loss — Competitive Win-Backs (Salesforce)
4Social Media — Key Findings
5What's Next — Open Planning

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

Confirmed compliance vulnerability — iOS-on-Mac sideloading​

  • ✗ FanDuel WV (Radar) — iOS betting app runs undetected on Mac via PlayCover, real-money bet placed
    PlayCover allows the iPhone / iPad app to run on a Mac while spoofing location. Radar did not detect the non-standard environment; both the standard and an advanced variant of the technique produced the same result. PlayCover was confirmed blocked the prior week on Bet365 MI and Fanatics TN — FanDuel WV is the standing outlier.
    🎫 CIV-61 — iOS spoofing testing with PlayCover tool

Confirmed compliance vulnerabilities — Remote Desktop undetected​

  • ✗ Bet365 NJ (XPoint) — macOS↔macOS RDP via Tailscale + Screen Sharing undetected
    Tailscale put two Macs on the same private network; macOS Screen Sharing drove one from the other. Tester accessed Bet365 NJ from a different physical location and placed bets. Follow-up testing across Radar, OpenBet, and GeoComply-integrated clients has been requested.
    🎫 CIV-73 — Bet365 NJ: Remote Desktop via macOS Screen Sharing (XPoint)

Bet365 MI — full integration validation (Radar / XPoint)​

  • ✗ Bet365 MI (Radar / XPoint) — five issues in one cycle: near-border lag, FaceTime + Windows RDP undetected, jurisdiction error, UX recovery broken
    Full validation of the Bet365 MI integration:
    • Near the Canadian border (Belle Isle): unreliable behaviour 200–1,000 m from the border; insufficient buffer-zone enforcement.
    • Detroit ↔ Canada cross-border: erroneous jurisdiction alert on the betting slip incorrectly stating wagering is restricted to NJ residents.
    • iOS FaceTime RDP: undetected. Tester in MA placed bets remotely on a device in MI.
    • Windows RDP: undetected. Tester in MA placed sportsbook and casino wagers on a device in MI.
    • UX recovery flow: persistent app glitches after any location failure, such as a VPN-detection event — forced restart required to resume.
      🎫 CIV-63 — Bet365 MI: full Radar / XPoint integration research

Ontario — mkodo / GeoLocs — multiple compliance failures​

Bet Saracen AR (Radar)​

Attacks successfully stopped (negative results)​

2 · Competitive Research (Valeria) — Key Findings​

Placeholder — Valeria to add.

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

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

Placeholder — Valeria to add.

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

Field Testing — Active & Upcoming​

  • CIV-64 — MI Advanced Spoofing
    • Fanatics MI — jailbroken iOS
    • BetRivers MI, Bet365 MI — VMOS device setup in progress before BH team training
  • CIV-78 — GeoComply: Remote Control of Jailbroken iOS via TeamViewer
  • CIV-74 — RDP via macOS Screen Sharing — extend Bet365 NJ findings to Radar, OpenBet, GeoComply clients
  • CIV-45 — Alberta launch: GeoLocs / mkodo competitor testing

Betting Hero — Upcoming Tasks​

  • CIV-63 — Bet365 MI: full Radar / XPoint integration research — retest RDP detection
  • CIV-67 — Michigan ↔ Wisconsin IP verification
  • CIV-55 — mkodo / GeoLocs: full validation
  • CIV-54 — Locance (LocationSmart): full validation
  • CIV-42 — RSI (BetRivers) in DE: CPU usage on macOS

Integrations team​

  • TBD

All findings this week​

Competitor profiles​

Radar → · Xpoint → · OpenBet → · GeoLocs → · Locance →