The Opt-Out Illusion: The Deadline

Twelve days from now, GitHub will begin using your Copilot interaction data — inputs, outputs, code snippets, and surrounding context — to train AI models. The policy change was announced in a changelog update on March 25, with a 30-day notice period.¹ If you use Copilot Free, Pro, or Pro+, you are opted in by default.

What Gets Collected

Per GitHub's FAQ:²

• Accepted and modified Copilot outputs
• Input prompts and code snippets
• Surrounding code context
• Comments and documentation
• Filenames and repository structure
• Navigation patterns and feature interactions

GitHub is careful to note that repositories "at rest" are not directly trained on. But code from private repositories that you actively interact with during Copilot sessions can be collected through interaction logs.³ The distinction is real but narrower than it sounds. If you discuss a proprietary algorithm with Copilot Chat, that conversation enters the training pipeline. The repo stays private. The knowledge doesn't.

Who's Exempt

Copilot Business ($19/user/month) and Enterprise ($39/user/month) customers are exempt under their Data Protection Agreements. Students and teachers on free Copilot access are also exempt.²

Individual developers on Free, Pro ($10/month), and Pro+ ($39/month) are not.

As one developer noted: the enterprise exemption is an implicit admission that the data has commercial value and legal risk. if the data were harmless, why exempt the customers with legal departments?⁴

How to Opt Out

Go to github.com/settings/copilot. Under the Privacy heading, set "Allow GitHub to use my data for AI model training" to Disabled.¹

If you previously opted out of data collection for product improvements, your preference has been preserved — you don't need to act again.¹

The Timing

The April 24 training deadline lands in the same month as two other Copilot changes:

• April 10: GitHub enforced new rate limits and retired Opus 4.6 Fast from Pro+ plans⁵
• April 10: GitHub paused new Copilot Pro free trials

In March, GitHub injected promotional "tips" into pull requests before reversing after backlash.

The pattern: tighten limits, remove the best model, pause trials, and start training on user code. All in the same billing cycle. For Pro+ users paying $39/month, the value proposition on April 25 will be: fewer models, stricter limits, and your interactions training GitHub's next product.

The Community Response

A Hacker News thread titled "If you don't opt out by Apr 24 GitHub will train on your private repos" hit 745 points and 319 comments.⁶ GitHub's own community discussion received hundreds of downvote reactions versus a single upvote.²

GDPR concerns were immediate. Under EU law, opt-out is not valid consent. Switching from opt-in to opt-out for a new data processing purpose could be challenged.⁶ No enforcement action has been taken yet, but European data protection authorities are monitoring.

Migration signals are already visible. Developers are discussing self-hosting with Forgejo, Gitea, and Sourcehut. Cursor is the primary alternative for those staying in the commercial ecosystem.

The Receipt

We wrote about the opt-out pattern before GitHub announced this specific policy. The playbook is consistent across the industry: launch with privacy-friendly defaults to build trust and market share, then expand data collection once the user base is locked in.⁴

GitHub has millions of paid Copilot subscribers across every industry. Most of those users will never change their settings. That's the point.

The deadline is April 24. The opt-out is at github.com/settings/copilot. You have 12 days.