Competitive Intelligence — Weekly Sync
📅 Week 3 — April 14, 2026 · ⏱ 30 minutes · 👥 Weekly cadence
1 · Competitive and Client Testing (Julia) — Key Findings
Border Performance Limitations (Radar)
- ✗ Proximity Constraints (OK Border) — validation fails until 100m iOS / 220m Android
Plus desktop verification failed at 1,750m from the border via public Wi-Fi (Mac/Windows). Success threshold remains undetermined.
Desktop UX + System Performance
- ✗ Bundle: mobile-hotspot incompatibility, auto-launch, 4% CPU pulses, macOS/Chrome compat gaps
Five distinct desktop UX problems: mobile-hotspot instability (Mac/Windows), persistent install download prompts, auto-launch on system startup without consent, 4% CPU spikes every 10s at 600m from the border, and inconsistent behaviour across macOS 26.0.1 vs 26.3.1 / Chrome 146 vs 147.
User Experience Deficiencies
- ⚠ UX + Error Messaging — BetSaracen displays generic "account security" alerts lacking diagnostic data. Significant user friction.
2 · Competitive Research (Valeria) — Key Findings
- ⓘ MITM tests partially completed on Xpoint — they seem to be blocked, thus compliant. Will retest some test cases; Radar tested next.
- ⓘ Splash Sports — aiming to offload Xpoint in June 2026 over multi-state DFS gap
Xpoint has no Multipass equivalent and no Dynamic Boundaries equivalent — Splash Sports has to handle multi-state DFS rules themselves. - ⓘ Bet365 dual-stack — XPoint on web, Radar on mobile
Radar SDK Release Analysis (Apr 2025 → Apr 2026)
- ⓘ Strategy shift — from "where is the user?" to "can we continuously trust this location?"
Releases every 3 weeks – couple of months. Axes of movement: IP-triggered re-validation, multi-signal decisioning (motion / device / network alongside GPS), indoor / floor-level accuracy with BLE beacons, modular plugin-based fraud architecture.
GitHub monitoring
We will start the GitHub monitoring — subscribed to both XPoint and Radar GitHub repositories to track new releases, SDK changes, and any publicly visible technical updates going forward.
3 · End-user Feedback (Valeria) — Key Findings
📊 Full dataset: Social Media Competitive Signals · Reddit + X/Twitter public posts. Monitoring initiated March 2026.
- 36 new posts added to the tracking spreadsheet. Key signals:
- ⓘ FanDuel — $12,000 payout denied due to "suspicious location" flag
FanDuel dominated complaints this week — persistent location errors, bans for cross-state logins, plus the headline payout denial. - DraftKings — multiple reviews citing location checks taking 10+ minutes, disrupting live bets. (Hard to determine which states they're from / which provider.)
- Bet365 (XPoint web / Radar mobile) — continued app freeze + bet slip erasure reports; one user must delete and reinstall the app every session.
- Fanatics (OpenBet) — location error on first launch reported by new users.
- TQJ 'Todos Querem Jogar' switched OpenBet off — described as working poorly and causing UX issues. Now using IP as their primary geolocation solution — no proper geo-enforcement.
- Bet365 web (XPoint) — Reddit user publicly asking how to spoof XPoint Verify from Florida. Two users confirmed it is possible and offered help via Magisk. Worth investigating Magisk + XPoint Verify vulnerability.
4 · What's Next — Plan for Next Week
Field Testing
- Jailbroken root-hidden iOS — to test on FD WV, Saracen AR
- Device farm on Android — run spoofing test for Saracen AR
- Fanatics / OpenBet Locator — validate the integration
- Radar / Saracen AR, XPoint, Radar / Bet365 — run Replay Attack testing
- Underdog: GeoComply vs Radar — full integration validation + comparison analysis
Betting Hero
- Radar / Saracen AR (web desktop) — perform static connection validation of the competitor's app
Integrations team
- Conduct Mkodo research
- Request Mkodo tests
- Research Xpoint updates frequency + what's changed
Portal cross-links
- Xpoint profile → — Splash Sports offload + Multipass gap.
- Radar profile → — desktop UX + border performance issues.