The short version
GitHub is changing its policy to use your interaction data—including the code you write and the snippets you see—to train its AI models, starting April 24. This applies automatically to Copilot Free, Pro, and Pro+ users, meaning your work could help "teach" their AI unless you manually change your settings. If you’d prefer to keep your work out of the training loop, you can opt out in your privacy settings today.
What happened?
Think of GitHub Copilot as a digital assistant that helps developers write code faster. Up until now, many users assumed their "private" repositories (folders for code only you can see) were off-limits to GitHub’s prying eyes.
GitHub is now hitting "CTRL-Z" on that assumption. Starting April 24, 2026, the company will begin collecting the data you generate while using Copilot. This includes the code you write, the suggestions the AI gives you, the comments you leave, and even the names of your files. They aren't just looking at public files anymore; they are looking at what you do inside your private projects to help their AI "learn" better.
Think of it like a teacher taking notes on a student’s private journal to figure out how to write better textbooks. While the goal is to make the AI smarter and catch bugs for you, it has caused a lot of concern for people who value absolute privacy for their intellectual property.
Why should you care?
If you are a casual coder or a professional using the Free, Pro, or Pro+ versions of Copilot, your "private" work is no longer just for your eyes.
GitHub argues that by "feeding the Octocat" (their mascot), you are helping the AI understand how to write better, more secure code. They claim that when they did this with their own employees' data, the AI became much more accurate and helpful. However, for a user, this means your unique logic, custom code structures, and private comments are being funneled into a system that helps train a product owned by Microsoft. If you are working on a secret project or proprietary code, this change might feel like a significant breach of trust.
What changes for you?
- The "Private" Asterisk: Your private repositories are effectively less private. If you use Copilot within those folders, that data is now eligible for training purposes.
- The Opt-Out Burden: You are now opted in by default. If you don't want your data used, you must take action.
- Business Users are Exempt: If you pay for Copilot Business or Enterprise, or if you are a student or teacher, your data is currently safe from this policy change.
- The Action Item: To stop this, you need to go to your GitHub Settings, find the "Privacy" heading, and toggle off "Allow GitHub to use my data for AI model training."
Frequently Asked Questions
Is this change happening to everyone?
No. Only users of Copilot Free, Pro, and Pro+ are affected. If you are on an Enterprise or Business plan, or if you are a student or teacher, your data will not be used for this training.
Is my code really "private" if I use Copilot?
Under the new policy, your private repositories are essentially "private*." While they remain hidden from the public, they are no longer shielded from GitHub’s own data collection for AI improvement unless you specifically opt out.
Can I stop GitHub from using my data?
Yes, but you have to do it yourself. GitHub has made this an "opt-out" system, which means you have to log into your account settings, navigate to the Copilot features page, and disable the data training setting to keep your information private.
Why is GitHub doing this?
GitHub claims that using real-world interaction data is the best way to make their AI better at spotting bugs and suggesting useful code. They point to internal tests showing that the AI performs much better when it can learn from actual human workflows.
The bottom line
GitHub is shifting the rules of the road for how your code is treated, moving toward a model where your private work becomes "fuel" for their AI engines. While they promise this will lead to a more helpful and accurate coding assistant, it puts the responsibility on you to protect your data. If you value your privacy, mark your calendar for April 24 or—better yet—log in and opt out now to ensure your work stays yours alone.