Kalshi makes some users disclose job details to curb insider trading

Kalshi is tightening access rules for its prediction betting platform, requiring some users to reveal job details as part of efforts to tackle insider trading. The BBC reports that this update comes after “issues with insider trading,” and that the platform is now adding new rules to address the problem.

In plain English: Kalshi is trying to reduce the chance that people with inside or job-linked information can place trades on public or semi-public predictions in a way that looks unfair. The most immediate consequence is operational. For a subset of users, onboarding and betting will now include extra steps that surface information about their employment. That means the platform is not only reacting to behavior after the fact, it is reshaping the information environment before bets are placed.

This is not just a policy tweak. In markets built on expectations, the edge often comes from what you know and when you know it. In traditional finance, insider trading is a familiar regulatory concept: trading on material nonpublic information is widely treated as illegitimate. Prediction markets do not always map neatly onto the same legal frameworks, but the underlying incentives are similar. If participants can systematically use nonpublic or job-connected knowledge, outcomes stop reflecting crowds and start reflecting information asymmetry. That is where trust breaks first, liquidity can follow, and regulators become more likely to look closer.

Kalshi’s move also highlights how platforms increasingly treat compliance as product design. Instead of relying purely on investigations or post-trade enforcement, the platform is changing the inputs. Asking for job details changes the risk profile of who can participate in certain circumstances and gives the company more data to monitor, review, and potentially exclude. It is the difference between “police after the incident” and “prevent the incident by changing eligibility.”

For executives watching from the sidelines, the second-order effect is clear. Prediction market operators and adjacent fintech platforms are being pushed toward higher-friction onboarding, more explicit user qualification, and stronger internal controls. Even if a platform believes it can moderate individual behavior, the board has to answer a bigger question: can the company prove it designed the system to discourage misuse? When insider trading is in the headline, proving your controls are working becomes as important as the controls themselves.

There is also a governance angle. Boards typically want evidence that compliance is not reactive. After insider trading issues, a platform that simply says “we will be stricter” often gets replaced by a more concrete standard: documented rules, consistent enforcement, and clear user disclosure requirements. Requiring job details for some users is the kind of specific change that can be audited. It gives compliance teams something to verify, and it gives the company a clearer story if regulators or courts ever scrutinize how the platform prevents unfair advantage.

Finally, the stakes extend beyond Kalshi. Prediction markets are built to be fast and global. But speed and global access make it harder to police information flows, especially when users span industries. If one operator responds to insider trading issues by increasing user disclosure, peers will notice. Competitors may face pressure to match these controls to protect their own reputations and reduce regulatory exposure. Investors, too, will treat these policy shifts as signals about long-term risk management, not just short-term fixes.

So while the BBC report is straightforward, the meaning is broader: Kalshi is moving from “allow people to bet” to “verify who they are, at least for some users, by collecting job details.” That is a compliance direction many platforms will likely follow if they want to keep participation credible, protect liquidity, and avoid becoming the next company that has insider trading issues in the rear-view mirror rather than the control room.