Live data from Hacker News

If you don't opt out by Apr 24 GitHub will train on your private repos

news.ycombinator.com

161–170 of 346 posts

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#161
I have an individual GitHub Copilot Pro subscription and also am a member of an Enterprise account that has one of its GitHub Copilot Business seats assigned to me. The opt-out setting doesn't appear on my individual profile anymore. However, I want to be able to use individual GitHub Copilot subscription for my individual work, and it seems like I can't do it anymore as Enterprise has taken over all my preferences. What a mess.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#162

No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…

> https://github.blog/news-insights/company-news/updates-to-gi...

> Should you decide to participate in this program, the interaction data we may collect and leverage includes:

> - Outputs accepted or modified by you

> - Inputs sent to GitHub Copilot, including code snippets shown to the model

> - Code context surrounding your cursor position

> - Comments and documentation you write

> - File names, repository structure, and navigation patterns

> - Interactions with Copilot features (chat, inline suggestions, etc.)

> - Your feedback on suggestions (thumbs up/down ratings)

"should you decide to participate.."??? You didn't ask if I wanted to participate. You asked if I didn't.

I didn't get to decide to participate. I had to decide not to. You made me do work to prevent my privacy from being violated.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#163
Rather than defending this absurd decision, GitHub could instantly win back trust by admitting they f*** up and reversing it entirely.

If they want to incentivise people to contribute their sources and copilot sessions, they could easily make it opt-in on a per-repository basis and provide some incentive, like an increased token quota.

This is not hard.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#164
post #139

No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…

Yes, you will. This is what the setting says on my account when I clicked the link: > model training > Allow GitHub to collect and use my Inputs, Outputs, and associated context to train and improve AI models. Read more in the Privacy Statement Are you seriously trying to claim that the code isn't input, output, or associated context of Copilot operating on a private repo? What term do you think better applies to the…

I don't like that they are training on any interactions with Copilot by default but training on something that you've put through Copilot yourself is much different than them just shoving all the private repos currently on Github into the training data.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#166
post #22

Earlier quoted context omitted.

Under privacy. > Allow GitHub to use my data for AI model training

I don't see it there, but I do see it in screenshots online. Maybe it was removed or moved.

Still at https://github.com/settings/copilot/features#copilot-telemet... for me.

It's not a new setting, fwiw. I opted out years(??) ago.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#167
Lots of hair splitting in the comments. The service is so unreliable at this point that I don’t trust them to not train on private repos even accidentally. You’re one vibe-coded PR away from having all your data scooped up regardless of any policy or intention.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#168
post #110

No we won’t. Details here https://github.blog/news-insights/company-news/updates-to-gi... For users of Free, Pro and Pro+ Copilot, if you don’t opt out then we will start collecting usage data of Copilot for use in model training. If you are a subscriber for Business or Pro we do not train on usage. The blog post covers more details but we do not train on private repo data at rest, just interaction data with Copilot.…

So you will train on data collected from free users working on GPL and copyrighted projects?

And on users that don’t even use github, other than the required account to use CoPilot in Visual Studio.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#169

This headline is false; it will not go take your private repos and dump them into a training dataset. Rather, GitHub will train on your copilot interactions with your private repos. If you do not use copilot, this makes no difference to you, though you should probably still turn it off.

That's also my read of the flag. But if they can train co pilot on input, I don't see what prevents them from training copilot on the code itself. In a court case they would simply say the opt in meant we can train from input. That's all we did.

To be fair, they display it reasonable prominently in GitHub when you are logged in. Given that, I feel the post title fall under the click bait category. I was fully aware of the Co-pilot opt-out change, but still clicked due the phrasing of the title.

Re: If you don't opt out by Apr 24 GitHub will train on your private repos

#170

Earlier quoted context omitted.

I've never seen the banner. Where does this show up?

right up top. I'm not sure how anyone could miss it.

  $ git pull
  $ vim foo.rs
  $ git commit
  $ git push
That's how.
Post reply on HN