Earlier quoted context omitted.
> I wonder what the comfortable medium between privacy and letting developers get feedback about how well their code works is. I consider the nut of the problem to be informed consent. If you have user's informed consent to get the feedback, then there is no problem. If you don't, then the whole operation is unacceptable. And no, mentioning it in the privacy policy or terms of use don't count as "informed consent".
This would be a real challenge for some companies. Having a clear privacy policy creates a hard dependency between it and the code. And developers are notorious for not even being able to keep comments updated along with their code changes. It's not impossible at all, just in the current state of the industry there's a good reason we have vague agreements (also including good old-fashioned laziness, of course). It'd…
Tough. If a company can't do it the right way, they shouldn't do it at all.
> in the current state of the industry there's a good reason we have vague agreements
Well, I guess that depends on your point of view. I see no good reason for this, but I have no doubt that the various companies do see a good reason by their definitions.
You're right about the current state of the industry, but the current state of the industry is a travesty.