[bharani_m]

Can you tell me why it is bad?

I am actually very concerned with the privacy of the app's users. The only communications I send to your email address are the initial onboarding emails and the saved bookmarks. No drip messages, no promotional emails etc.

I guess I need to convey that better in the privacy policy. I'd appreciate any links/resources that can help me draft a better privacy policy.

[CodeWriter23]

Obviously I can't speak for @vmateixeira, but this seems pretty bad to me.

> We may share generic aggregated demographic information not linked to any personal identification information regarding visitors and users with our business partners, trusted affiliates and advertisers for the purposes outlined above.

Especially considering the numerous examples of "anonymous" datasets being de-anonymized.

[ricardobeat]

That would preclude using things like Google Analytics on the website, it's not bad per se.

[tedunangst]

I think the key word is aggregated.

[vmateixeira]

Bellow is just an example of what I consider a big red flag, which mostly represents lack of control over my data.

EmailThis has the discretion to update this privacy policy at any time (...) We encourage Users to frequently check this page for any changes to stay informed about how we are helping to protect the personal information we collect. You acknowledge and agree that it is your responsibility to review this privacy policy periodically and become aware of modifications.

I will not be prompted to read and accept your new privacy policy, which you can update at any point in time without notifying me. I prefer the peace of mind of not needing to visit a website everyday to check on their privacy policy.

I'm not saying that this kind of business model is bad, it's just not what I am looking for. I prefer to give away a couple of bucks a year for some subscription than allowing my data to be used for profit indiscretionary.