That's pretty much the norm in Linux.

One typically gets packages from the distro's repository. And traffic with modern repositories uses HTTPS. So third parties don't see what packages are being used. And unless one configures a developer repository, there's never any traffic to the developer.

Also, IP addresses are considered PII under GDPR.

Edit: Still, if one cares that much about ones IP address, it's prudent to use a VPN service or Tor.

IP addresses are only PII if attached to other information. I can generate a list of IP addresses and store/sell that data and it's all fine because its meaningless without associated data.

The other information is "using Atom".

It's still impossible to link that to an individual unless they sold it to another company that has more info on the address.

Or bought the data.

I'm like 99% sure that datasets are available that link IP addresses to all sorts of PII. And then there are third-party cookies and other trackers.

Yes, and that possibility is enough to make this fall under the GDPR.

> Also, IP addresses are considered PII under GDPR.

Not true. They’re only PII if they can be used to connect something to a person. It’s a minor distinction, but it is one nonetheless.

In this case it would not be PII data if it was just an IP address in a webserver log saying someone checked for an update. It would be PII data if it was linked to your GitHub account.