Apple widens insider controls to include prediction market bets

A person viewing a trading screen, illustrating the use of prediction markets and controls on confidential information.
Photo by George Morina on Pexels

Apple has expanded its insider-trading controls to cover prediction-market event contracts, barring staff from using confidential company information to trade them. The company added the restriction to its policy in a filing made Tuesday with its annual report to the US Securities and Exchange Commission (SEC). Before the change, the document addressed securities transactions rather than event-based wagers.

What employee information is covered

The restriction applies to directors, officers, employees, contractors and consultants, as well as family members who live with them. It covers contracts traded using Apple Confidential Information, defined in the company's Business Conduct Policy to include material nonpublic information, among other things.

Information about suppliers, manufacturers, vendors and customers such as cellular network carriers is included when staff learn it through Apple. Employees are also barred from giving such information to someone else to trade. The rule applies even when the activity does not meet the legal definition of insider or securities trading. Breaches may lead to discipline, dismissal or repayment of equity awards.

Firms and platforms add controls

Apple joins other listed companies that have brought prediction markets into their employee rules. Emcor Group updated its policy on April 2 to prohibit trades based on nonpublic information, while GoDaddy said in an April 24 proxy statement that its policy also covers these markets. Seagate Technology's May 1 conduct-code revision names Polymarket and Kalshi and bars speculative activity concerning the company. Finance Magnates reported on the differences between the companies' restrictions, including Apple's coverage of information learned about business partners.

Prediction-market activity has increased: combined taker volume at Kalshi, Polymarket and Polymarket's US venue rose between the second and third quarters, according to FM Intelligence calculations. The policy change follows a Polymarket case involving a user alleged to have made more than $1 million on Google's Year in Search rankings, which fuelled accusations of trading on nonpublic information in January.

In March, David Miller, enforcement director at the Commodity Futures Trading Commission (CFTC), described insider trading on Kalshi and Polymarket as illegal. The CFTC ranked the conduct as its leading item among five enforcement priorities. Polymarket's March rule update prohibits trading with stolen confidential information, illegal tips or the ability to influence an outcome. Kalshi fined a YouTube channel editor $20,397.58 and suspended him for two years over contracts connected to his workplace. The House Oversight Committee requested records from both platforms in May on their detection of insider trading, with documents due by June 5.

FigureContext
$172.4 billionCombined taker volume at Kalshi, Polymarket and Polymarket's US venue in the third quarter.
$98.5 billionCombined taker volume at those venues in the second quarter.
More than $1 millionAmount a Polymarket user allegedly won betting on Google's Year in Search rankings.
$20,397.58Fine Kalshi imposed on a YouTube channel editor.
Two yearsLength of the editor's suspension from Kalshi.

Where this lands in the stack

For trading firms, the operational issue is how internal information controls map to event contracts, not only listed securities. Compliance and risk teams can check whether their policies identify confidential information about counterparties and suppliers, and whether staff reporting and escalation procedures cover activity on prediction-market platforms.

Operators should also ask what evidence would let them investigate a suspected breach, how access to sensitive business information is recorded, and who owns the review when a potential event-contract trade is flagged. Apple's policy does not specify how the company will detect or monitor such trades, so those controls remain an open question.

The policy also raises questions about how a firm defines relevant information across its business relationships and how that definition is communicated to contractors, consultants and household members covered by the restriction. Operations teams can review whether their existing incident process captures event-contract activity, preserves the information needed for an investigation and routes cases to the appropriate compliance and risk owners. The source does not say what monitoring Apple will use or how the rule will be enforced in practice.