| > The site’s author already agrees with you and has committed to making a better privacy policy. It’s on the list Because, my friend, there are some things that go on to-do lists and some things that do not. Launching something that collects personal data AND forwards it to a third party API ? Nah mate, that's NOT something where you can justifiably put "Privacy Policy" on your nearest To-Do list. In addition, if you are potentially dealing with users in Europe who are covered by GDPR, a real Privacy Policy is NOT an option, it is MANDATORY. I'm tired of software developers, irrespective of size, thinking it's a-ok to to take liberties with the personal information of others and/or not be transparent in what they do with your personal information. The fact you are a mom 'n' pop shop and not Google does not make it any more ok. Privacy cannot be an afterthought. |
Additionally, the existing privacy policy is a real policy. Just because it was generated doesn’t mean it’s not applicable. Not every policy needs to be handcrafted with love.
What, exactly, is wrong with the current policy? Have you even read it?
Finally, what exactly is the purpose of your comment? You may think it’s required, and that’s great, but so what? What does that change? Even remotely? Is the author going to get in a Time Machine and go back to before they created their project to make sure a Privacy Policy is the first thing they make? No.
Once again, it’s on the list, the author will appease you eventually. Until then, don’t use the service. Problem solved.