Skip to content
Notifications
Clear all

How do I stop Copilot from using my private repos to train its models?

1 Posts
1 Users
0 Reactions
1 Views
(@graces)
Estimable Member
Joined: 1 week ago
Posts: 95
Topic starter   [#8631]

Hello everyone,

I've been seeing a recurring question both here in the community and across other forums, and I felt it warranted a dedicated discussion. Many developers and teams using GitHub Copilot are understandably concerned about data privacy, particularly regarding how their private repository code is handled. The core anxiety seems to be this: even if we trust the stated policies, how do we actively ensure our proprietary code isn't being used to train or improve the underlying AI models?

This is a perfectly valid concern, especially for those working with sensitive intellectual property, under strict compliance requirements, or in organizations still formulating their AI governance policies. The distinction between the service *processing* your code to provide real-time suggestions and *retaining* it for long-term model training is crucial, yet often murky in people's minds.

From my reading of GitHub's current documentation and terms, the primary control mechanism is the "GitHub Copilot for Business" subscription. This tier explicitly states that it does not retain code snippets or use them for model improvement. For individual users or those on a "Copilot for Individuals" plan, the data usage policies are different, and code from public repositories may be used. However, the handling of private repository code seems to hinge on whether you have the business license.

I'd like to steer us toward a constructive, evidence-based breakdown. Could we collectively gather and examine the specific, actionable steps one can take? I'm thinking along these lines:

* A clear comparison of the data handling commitments for "Individuals" vs. "Business" plans, directly from the official terms of service and privacy policy.
* Verification steps: Are there account-level settings, repository-level settings, or GitHub-wide privacy controls that explicitly opt you out of data retention for training?
* For organization admins, what is the exact process to configure and enforce these settings across all members and repositories?
* Beyond GitHub's controls, what are the practical development environment practices (like using local models or specific IDE settings) that can add an extra layer of isolation?

Let's try to move from general worry to specific configurations and verified facts. If you've navigated this process for your team or found definitive documentation, sharing those details would be incredibly valuable for everyone here. The goal is to create a reference that helps users make informed choices based on their specific security needs.

— Grace


Stay curious.


   
Quote