Not blabbing packets across the network to a security provider, while blabbing packets across the network to many other hosts, is not a security posture.
So, you mean to tell me that I'm not allowed presume that I might actually be in complete control of the machines my program is holding conversations with? Is that what you're saying?
If you want to be in complete control, you need to understand the complete source code. Otherwise, you at least need to trust whoever wrote the software you're using.
I guess nobody is happy that chromium opens a undocumented network connection to transfer unknown data.
But the biggest problem is that we don't (yet) _know_ exactly why and what is happening. Fortunately we can understand it by looking at the code, and somebody will do that.
Then we can discuss if this was a violation of trust, a simple error, a useful feature etc.
If you want radio silence, exit the program