Unfortunately, "that would be bad for me" does not imply "that is not happening"

Telemetry is awesome for devs but totally opaque to end users. It's very difficult to know what your applications are really doing on the backend. You have to start packet sniffing, and that's a pretty deep rabbit hole.

An application could:

* send telemetry in URL parameters when it checks for updates

* send telemetry data exactly one time after, say, an hour of use.

* send telemetry data during a time when you are already sending a lot of traffic, and send it to an amazon web service endpoint (good luck plucking that out of normal network activity based on IP data alone, when so much software communicates with most likely the same AWS endpoints.)

My point is that there is probably < 5 people on the planet who scrutinize every scheduled task, every Wireshark trace, and everything else well enough to know for certain that nothing is going on. The only people who know for sure that no telemetry is going on are those who airgap their PC from any network at all.