FanDuel Voided Bill Simmons's Bets After He Admitted Proxy Betting

The Ringer founder said on his own podcast that he gave his sportsbook login to his daughter's boyfriend. Massachusetts requires operators to log every IP address an account is accessed from, and it still took a podcast.

• Bill Simmons, founder of The Ringer, said on his podcast that he had given his FanDuel login to his daughter's 21-year-old boyfriend so that bets could be placed for him in Massachusetts while Simmons was in California
• FanDuel said it handled the matter consistent with its terms and conditions and Massachusetts Gaming Commission regulations, reporting it to the MGC, voiding the wagers and actioning the account
• An MGC spokesman said the commission "is aware of the comments made on the Bill Simmons Podcast and staff are currently reviewing the matter", announced two days after the episode
• Massachusetts rules make a sports wagering account non-transferable and require every registrant to acknowledge at sign-up that they may not let another person access or use it
• Operators must already record every date, time and IP address from which an account is accessed, which is the control that should surface this conduct without a public admission

An Admission, Not an Allegation

Bill Simmons, the founder of The Ringer, said on an episode of his podcast that he had on multiple occasions given his FanDuel account login to his daughter's boyfriend, who is 21, so that the wagers could be placed in Massachusetts while Simmons himself was at home in California. That is proxy betting, and it is prohibited both by Massachusetts regulation and by FanDuel's own terms.

The distinction worth holding onto is that this is an admission rather than an allegation. Simmons described the conduct himself, unprompted, and has since called it a lesson learned after his bets were voided.

FanDuel said it handled the situation consistent with its terms and conditions and with Massachusetts Gaming Commission regulations, which included reporting the matter to the commission, voiding the bets and actioning the account. A commission spokesman said the MGC "is aware of the comments made on the Bill Simmons Podcast and staff are currently reviewing the matter". The review was announced two days after the episode aired.

The regulatory framework is unusually explicit. Under 205 CMR 248.01(2), a sports wagering account "may only be established in the name of a patron and is not transferable". Under 205 CMR 248.03(2)(d), every registrant must, during registration, "acknowledge that they are prohibited from allowing any other person to access or use their Sports Wagering Account", and under 248.03(2)(e) must consent to the monitoring and recording of the account's use by both the operator and the commission.

There is also a provision aimed squarely at proxies. 205 CMR 248.05(2) requires an operator's internal controls to implement procedures to terminate all accounts of any patron who establishes or seeks to establish more than one account, "whether directly or by use of another Person as proxy".

Most consequentially for how this should have been caught, 205 CMR 248.03(3)(g) requires the operator to maintain, in each patron's electronic file, "every date on, time at which, and IP address from which the Sports Wagering Account is accessed". Massachusetts also defines a category of prohibited person under 205 CMR 238.33(1) whom operators may not allow to hold an account at all.

Geolocation Would Have Passed This Cleanly

The instinctive assumption is that location checks should have stopped it, and that assumption is wrong in a way the industry should be honest about. Geolocation exists to confirm that a wager is placed inside the licensed jurisdiction. In this case the person tapping the screen was physically in Massachusetts, which is exactly what the check is designed to confirm, so it would have returned a compliant result every time. The bettor being in the state was the whole point of the arrangement. What failed is not location assurance but identity assurance, and the two are routinely conflated in compliance narratives and in regulatory testimony. Any operator claiming that geolocation protects account integrity is describing a control that does something else.

The Data to Catch This Was Already Being Collected

The uncomfortable part is that 248.03(3)(g) obliges operators to log every access with its IP address, which means the pattern here was recorded as it happened: an account belonging to a California resident being accessed repeatedly from Massachusetts. That is a device and network signature that anomaly detection is well capable of flagging, and the data was already mandated, already retained and already available to both FanDuel and the commission. It surfaced through a podcast instead. This is a familiar shape in gambling compliance, where the requirement to collect is treated as satisfied by collection and the monitoring obligation gets less engineering attention than the acquisition funnel. Pennsylvania's regulator issued written guidance to operators on monitoring accounts for proxy wagering back in October 2023, so nobody can argue the industry lacked notice that this was expected of it.

A Celebrity Case Is How Enforcement Norms Get Set

Nothing about proxy betting is rare, and the reason this one matters is not Simmons. Account sharing between family members and friends is common, largely invisible and mostly small, and it corrodes the integrity claims the regulated market makes against offshore competitors: known customer, verified age, enforceable self-exclusion. If a well-resourced operator's controls surface a repeat proxy arrangement only after the patron announces it publicly, the same is true of the quieter cases that never get announced. The MGC's review will determine what happens to one bettor. The more useful outcome would be a question put to every licensee in the state about what their access logs are actually monitored for, given that Massachusetts has been among the more assertive regulators on who is permitted to take bets there.

Simmons broke a rule he had acknowledged at sign-up and the operator acted once he said so. The question for the sector is why the acknowledgement, the consent to monitoring and the mandated access logs all had to wait for a microphone.