Like @jrlanglois said, how else are developers supposed to aggregate information about how their products are being used, where crashes are happening, etc.?
In a FOSS cupcake world, nothing would be tracked because everyone would be an expert developer who knows every language and has infinite free time so that when they find a bug or want a new feature, they can pull the source, fix it, and contribute back. That’s not how the world works. Analytics are widespread nowadays because software is massive and complex and deployed to thousands or millions of users who are likely running into issues, share trends in usage, or are looking for something that isn’t there.
I feel like you’re confusing usage analytics with user data mining, where personally identifiable information is used to build a profile of a user and use it to sell stuff to them or to give to governments. I think we can all agree that type of data collection is not good. I suppose this “evil” version could be built using JUCE’s analytics module, but that’s basically a 1:1 analogy with @jrlanglois’s point that JUCE can be used to build viruses.
Even many (most?) FOSS Linux distros use some form of analytics to automatically track and aggregate issues and usage trends.