I don't. I assume any service I use has the policy that they'll sell any and all data they collect to the highest bidder. (And the lowest bidder, and anyone els

I don't. I assume any service I use has the policy that they'll sell any and all data they collect to the highest bidder. (And the lowest bidder, and anyone else willing to give them a few cents for it.) Reading and parsing 10 pages of legalese (which I can understand but - not being a lawyer - am never sure I understand all the implications of anyway) is just not worth an hour of my time if I'm willing to accept the worst case scenario regardless. I suspect this is also how most internet users solve the problem. A privacy policy is a CYA document for the website/app owner, nothing more. It's vanishingly unlikely that you can make it any sort of selling point or competitive advantage for a website or app unless you're in a tiny niche specifically targeting extremely technically and legally savvy users. If there were an expectation that every privacy policy be prefixed with a bullet point summary in plain simple English, I might take a different approach.