2 posts tagged with "draftkings"

What happened. DraftKings has moved its web DFS product in New Jersey from GeoComply to Radar.

What stayed. The DraftKings Sportsbook and the DraftKings mobile apps remain on GeoComply. This is a partial-displacement, not a wholesale loss.

Open question being tested. Whether running two different geolocation providers side by side introduces compliance or security gaps — internal ticket CIV-65: DraftKings DFS - validate the competitor's integration.

Why it matters. This is Radar's first major US live-traffic win on a Tier-1 operator. The sales narrative is two-sided:

• Concerning: DK's procurement team has now signed off on Radar for a regulated US product. Other operators may treat this as permission.
• Constructive: The pattern "challenger gets the DFS web slice, GeoComply keeps everything else" is the new template for second-source attempts. Lead with "we keep the high-stakes stuff" in displacement conversations.

Counter-evidence. Radar's compliance gaps across other operators (rooted-hidden Android, resigned iOS, GPS simulator, jailbroken iOS at Sleeper/PrizePicks/Fliff, Chrome extension at Underdog) are independent of this migration and should be in every DK-adjacent conversation.

Radar profile →

Source. Monthly social-media brief, May 5 weekly sync. Reddit + X / Twitter monitoring. Span: March 30 → April 27, 2026.

Volumes​

• Location verification failures dominate end-user complaints — 38% of all findings in the monitoring window.
• DraftKings: 11 mentions — app lag causing re-verify loops.
• FanDuel: 9 mentions — location dropping mid-session.

Both patterns are consistent with geo-check frequency friction, not outright failures. That's an account-management conversation, not a displacement conversation.

Circumvention sophistication is growing​

Circumvention attempts are present in every weekly report and rising: 2 → 3 flags 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. Reddit-sourced bypass methods should feed directly into our spoofing test backlog.

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

KYC friction is the halo problem (23%)​

KYC friction (23% of findings) is concentrated at Fanatics and DraftKings — duplicate account suspensions, document rejection loops, 2+ week verification delays, SSN privacy objections.

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