What is changing — The April 24, 2026 policy update
On March 25, 2026, GitHub announced a significant change to Copilot's privacy policy.
Starting April 24, interaction data from Copilot Free, Pro, and Pro+ users will be used by default to train AI models.
This marks a shift from the previous "opt-in" approach (affecting only those who consented) to "opt-out" (affecting everyone unless disabled manually). A 30-day grace period has been provided, but if no action is taken, data will automatically begin being used for training.
Scope of data covered
Hearing that "code is being trained on" naturally raises concerns, making it essential to understand the exact scope involved.
Data used for training
| Data category | Description |
|---|---|
| Input prompts | Questions posed to Copilot Chat, context during code completion |
| Output results | Code suggestions and chat responses generated by Copilot |
| Code snippets | Code fragments transmitted while using Copilot |
| Accepted and edited outputs | Copilot suggestions accepted or modified by users |
Data not used for training
- Saved code in private repositories is exempt from training
- Repository content "at rest" will not be read
However, it is crucial to note that prompts and code snippets transmitted to Copilot while working in private repositories fall within the scope. Even if the repository itself is not read, confidential code could be included in training data through interactions with Copilot.
Opt-out instructions (3 steps)
Changing the setting takes only one minute. Please complete it by April 24.
For personal accounts
- Log in to GitHub and click your profile icon in the top right corner
- Navigate to Settings → Copilot → Policies
- Change "Allow GitHub to use my data for AI model training" to Disabled
GitHub.com → Settings → Copilot → Policies
→ "Allow GitHub to use my data for AI model training" → DisabledIf you had previously opted out under the former "Product Improvement" setting, that preference will carry over.
For organization accounts
Organization administrators can configure the policy for the entire organization.
- Organization settings → Copilot → Policies
- Set "Allow GitHub to use my organization’s data for AI model training" to Disabled
Plans not affected
The following plans are exempt from this policy change:
| Plan | Training data usage | Notes |
|---|---|---|
| Copilot Business | ❌ Exempt | Contractually, interaction data is not used for training |
| Copilot Enterprise | ❌ Exempt | Same as above |
| Students and educators | ❌ Exempt | Free tier for educational institutions is also exempt |
| Copilot Free | ⚠️ Covered | Opt-out required |
| Copilot Pro | ⚠️ Covered | Opt-out required |
| Copilot Pro+ | ⚠️ Covered | Opt-out required |
Actions organizations and teams should take
When personal plans are used for work
This is the case that requires the greatest caution. If work code is handled under personal Free, Pro, or Pro+ plans, interaction data could potentially be used for training.
Recommended actions:
- Opt out immediately: Disseminate the procedure to all members and change settings by April 24
- Consider migrating to Copilot Business: Prohibits training data usage at the contractual level
- Update internal guidelines: Add clauses regarding training data to the Copilot usage policy
If already using Copilot Business/Enterprise
No additional action is required. However, verifying whether team members are concurrently using Copilot with personal accounts is worthwhile.
Frequently asked questions
Q: Will opting out degrade Copilot's accuracy?
A: No. Opting out only stops data from being used for training and does not affect Copilot's functionality or accuracy.
Q: What happens to data that has already been collected?
A: New data collection stops after opting out. Handling of historical data is governed by GitHub's Privacy Policy.
Q: Is code in private repositories safe?
A: Data stored in repositories is exempt, but prompts and snippets transmitted while using Copilot are subject to the policy. To completely prevent transmission, Copilot itself must be disabled for the repository in question.
Conclusion
GitHub's policy change involves risks that cannot be dismissed by claiming ignorance.
- Verifying opt-out settings by April 24 — this is the top priority
- While saved code in private repositories is exempt, interactions with Copilot are covered
- For business use, migrating to Copilot Business is the most reliable safeguard
- Team leads should notify all members as soon as possible
Adjusting the setting takes only one minute. Do not put it off; check it right now.
Related articles
- 2026 Supply Chain Attacks Recap: Defense Strategies Learned from Axios and LiteLLM Incidents — Latest security trends for developers
- Introduction to Website Security Measures — The bare minimum small businesses should do
- Cursor 3 vs. Claude Code: An In-Depth Comparison — Exploring AI development tools beyond Copilot
