GitHub still sends the same personal data to their own analytics endpoint, and the privacy policy which lists third-party data subprocessors [1] has not been updated.
Tracking cookies have little value for GitHub when they can collect data about users that have already been authenticated, and they send the username and user ID as part of their tracking request.
Inspect the request sent to collector.githubapp.com on every page load to see the type of personal data that is being collected on the client-side.
We have no visibility into how they associate this data with analytics data collected on the server-side, and that's where an updated privacy policy would also help.
See my comment below for details: https://news.ycombinator.com/item?id=25458635
Tracking cookies have little value for GitHub when they can collect data about users that have already been authenticated, and they send the username and user ID as part of their tracking request.
Inspect the request sent to collector.githubapp.com on every page load to see the type of personal data that is being collected on the client-side.
We have no visibility into how they associate this data with analytics data collected on the server-side, and that's where an updated privacy policy would also help.
[1] https://docs.github.com/en/free-pro-team@latest/github/site-...