I agree, most companies conduct feedback in a completely impersonal way. I tell my customers that my software doesn't contain any tracking or telemetry, and that human-to-human feedback (direct email) from users is the only way I can know of problems. I also make it very clear that I am open to all kinds of feedback. This is great because I get bug reports directly, can understand how people are using the program in their workflow, and can contextualize feature requests and build solutions that fit for everyone.
Users like this because they are actually being listened to by the software's author, there is no overhead to fixing problems, and they aren't being shoehorned into a database.
Of course direct feedback is good. But it's not scalable and you risk of running a very real case of bias towards whoever you're asking. Running telemetry on your software is not "evil" or "stampedes over civil liberties". You can most certainly run telemetry in a way that protects people's privacy and gives you insightful data on how your users operate and interact with your software. I know this, I've worked on an analytics service serving hundreds of millions of users. I'm building right now a feature-flagging/configuration/core metrics service that does exactly that: preserve user privacy and allow developers to learn about their users (not easy and there are some trade offs, like accuracy).
Users like this because they are actually being listened to by the software's author, there is no overhead to fixing problems, and they aren't being shoehorned into a database.