And 64 years ago, GECOS was released, with a dedicated field for a users real name, location, phone number and email. That was implemented in UNIX shortly after, as a field in /etc/passwd, which means all Linux distros and other UNIX-like OS's like MacOS have and had fields for all of that forever. So if you don't want the option to store personal information in your OS, use TempleOS.
Yeah, with GECOS introducing the GECOS field, they normalized name verification, phone number verification, email address verification as well as location verification. So soon we should see those becoming mandatory and controlled.
Oh wait, that was 64 years ago, so by now we should already be in literally 1984, actually?!
Or is it that no one actually gives a fuck about a handful of programs trying to read user data that no one set, and if they set it, set it to a nonsencial/false value without any component verifying anything?
The problem isn't libraries adding more optional field to their capabilites, but management systems (such as a distros installer) making them mandatory against user will. That is what users should actually object to. No installer or component I know actually sets the location field. However, some are already planing to require the birth of date field, which is the actual start to pushing any boundaries. So start protesting there.
Or, if you actually think that simple standards for how user data is stored is already malicious verification, your only option is probably, unironically, TempleOS, as even DOS stores user information, Country + TZ, available for other programs to fetch.
I hope she gets mauled sooner or later. Preferably sooner.