Home ›News ›Kalshi and Novig Seek State Lists to Close Self-Exclusion Gaps

Gamble Ballers · News analysis · Continuing coverage

Kalshi and Novig Seek State Lists to Close Self-Exclusion Gaps

The exchanges want state exclusion records to support broader restrictions on prediction-market trading. Our analysis examines the existing service, its coverage and the terms needed to preserve users’ choices.

In this article
Illustrative photograph of a fictional adult taking a quiet lakeside walk. A visual reference to a voluntary pause, not an actual Kalshi or Novig user, a self-exclusion participant or a person with an identified medical condition.
Illustrative editorial image.

Kalshi and Novig have asked 35 US states to share gambling self-exclusion lists so that people who have restricted their access to state-regulated gambling could also be blocked from prediction markets. Bloomberg reported that the companies sent the letter on 19 November and requested replies by 15 December. The proposal seeks cooperation while disputes over regulatory authority continue.

According to Bloomberg’s account of the letter, roughly 1,800 people had already self-excluded from prediction markets. The companies offered to share their records with states and proposed confidentiality agreements for state data supplied to Integrity Compliance 360 (IC360). The coverage of any arrangement would depend on the states joining it and the terms they agree.

Our 14 November analysis of the Commodity Futures Trading Commission’s disputes over state access examined the conflict involving Louisiana and Arkansas. This development adds a consumer-protection question to that story: how far should a person’s decision to stop participating travel when services sit within different regulatory systems?

Why the lists do not join up automatically

Consider someone who has excluded themselves from a state’s licensed sportsbooks. That record may not automatically enter a separate prediction-market programme. The person’s intention can be clear while the systems recognising it have different coverage. The proposed exchange of records is intended to carry that decision further, subject to the scope and lawful terms of each programme.

A private cross-platform service already exists. In an announcement dated 19 October, IC360 described Novig as one of two active exchanges using SelfExclude.io. The new request therefore concerns cooperation over state records, building on a privately operated network whose coverage depends on participating platforms.

Coverage includes access routes and duration

Checked on 21 November, SelfExclude.io’s FAQ identifies Kalshi and Novig as fully integrated and describes other integrations, including Polymarket and Robinhood, as in progress. That is the service’s published participation status. A platform named in future plans should not be counted as providing an operational block today.

SelfExclude.io FAQ: published integration status checked on 21 November 2026
PlatformPublished integration status
KalshiFully integrated
NovigFully integrated
PolymarketIn progress
RobinhoodIn progress

Access routes also matter. Kalshi’s help page separately warns that its own Voluntary Self-Exclusion tool does not restrict access to Kalshi products through a Futures Commission Merchant, a type of regulated intermediary. A wider scheme would need to explain how intermediaries implement its restrictions, alongside the checks carried out by the exchange and its direct app.

The programmes also offer different terms. SelfExclude.io lists one, three or six months, or one year, with automatic expiry at the selected term’s end. Pennsylvania’s interactive-gaming rules offer one year, five years or a lifetime option. In our view, any transfer needs to preserve the original protective decision: a longer state exclusion should not silently become a shorter pause.

Published programme options checked in the supplied article: SelfExclude.io lists one, three or six months, or one year, with automatic expiry at the selected term’s end. Pennsylvania interactive gaming offers one year, five years or a lifetime option under its own rules. The article’s assessment is to preserve the original protective term when programmes differ. Transfer terms still need agreement; coverage, access routes and permitted data uses require separate checks.
A comparison of published programme options, not an agreed transfer policy. Preserving the original protective decision is our assessment.

States have to assess their own disclosure rules

Pennsylvania provides a concrete example. Section 815a.4 of its interactive-gaming regulations treats exclusion information as confidential and limits disclosure, including a specified responsible-gaming exception for affiliated gaming entities. Section 815a.8 allows selected data for administering responsible-gaming programmes while restricting disclosure of identifying information. The provisions show why any proposed arrangement requires a programme-specific legal assessment.

Before agreeing, a state would need to establish the permitted recipients and purposes for its programme, alongside any consent or other legal basis required. Confidentiality terms could form part of that arrangement. They would need to sit within the applicable rules, with a clear process for updating records and correcting errors.

The data flow and enforcement roles need to be clear

SelfExclude.io’s FAQ describes hash-based matching that keeps raw identity details out of partner queries. Its privacy policy also permits disclosure of relevant identity data for enforcement and regulatory purposes. A state agreement would need to specify which transfers use hashed identifiers and what other disclosures are authorised. The distinction matters when a state assesses the data it can entrust to the service.

The terms of use describe IC360’s role as maintaining the registry and notifying partners. They also state that exclusion is not instantaneous and that IC360 cannot guarantee immediate or error-free enforcement by third-party platforms. This makes the platform’s actual restriction, as well as the registry entry, important evidence of protection. A successful data match is only one step in that process.

Our view: cooperation should preserve the person’s choice

In our view, cooperation is worth pursuing because it could carry a person’s protective choice beyond the service where it was first recorded. Its value would be measured by effective restrictions and preserved terms, with personal information used for the agreed protective purpose. The current dispute over jurisdiction makes clear allocation of responsibility especially important.

We would look for a published scope of coverage, evidence that partner platforms apply restrictions, and an accountable route for correcting a failed or mistaken match. Reporting should show how original exclusion periods survive the transfer and what happens when programme rules differ. Users also need a clear explanation of which services recognise their decision.

A data-sharing agreement would sit alongside the continuing jurisdiction disputes. It could nevertheless improve the practical reach of self-exclusion if the legal and operational arrangements hold together. For now, the reported request is an opening. The meaningful next development would be an agreed process showing whose decision is recognised, where it applies and who answers when it fails.

Sources

Bloomberg, Bobby Allyn, 19 November 2026, syndicated by Yahoo Finance: reporting on the letter, 35 states, proposed exchange, enrolment count and requested reply date.

IC360, 19 October 2026: Novig partnership announcement and existing use of SelfExclude.io.

SelfExclude.io, public site and FAQ, checked 21 November 2026: participating platforms, durations, expiry and matching description.

Kalshi Help Center, Voluntary Self-Exclusion: scope of the direct tool and the Futures Commission Merchant limitation.

58 Pa. Code 815a.3: interactive-gaming exclusion-period options.

58 Pa. Code 815a.4: interactive-gaming list, confidentiality and disclosure provisions.

58 Pa. Code 815a.8: selected data for responsible-gaming administration and restrictions on identifying information.

SelfExclude.io Privacy Policy: permitted uses and disclosures for exclusion enforcement and regulatory purposes.

SelfExclude.io Terms of Use, acknowledgments regarding registration: registry and partner roles, processing delays and enforcement limitations.

Topics and categories

Countries
United States

Background

Earlier reporting in this story.

All coverage: CFTC prediction market access dispute