I've mentioned this before, I've never understood putting a ToS or privacy policy on a website.<p>Is it a legally binding document? They can change at any time and without notice. Who is to say what you just read, and apparently agreed to, didn't change in the few seconds it took you to post something.<p>How can you prove someone has read or not read it when something goes to court?<p>ToS of this comment: If you read this, you owe me 10 dollars.<p>Stupid, isn't it?
I wish it expanded on the first paragraph in the (new) second paragraph.<p><i>For example, we profile your browsing habits and what you're interested in, and sell that to advertisers who attempt to predict your interests in porn, our most lucrative information sharing market. Recent web browser updates have prevented us from directly querying your history, but our statistics indicate that you might be interested in child models.</i>
i kind of expected this to be a more serious attempt at solving the current state of privacy policies being "hidden" behind overly long and complicated documents.<p>i think it's a brilliant idea to have a few standard privacy policies and/or terms of service documents where the service provider just fills in the blanks, a la GPL or BSD licenses.<p>seeing "our privacy policy is FPP" on a web service where FPP is a hypothetical document blessed by a reputable privacy advocacy group would certainly increase the appeal of that service amongst the ones who care.
What would you think about a revolution in the world of "Privacy Policy", spreading the usable approach of Creative Commons?
We are trying to do this all at <a href="http://www.iubenda.com" rel="nofollow">http://www.iubenda.com</a>
Let's discuss, I want feedback to change this world in better (I'm armed with Mockups :P)<p>Andrea
Deployed it on my blog - <a href="http://www.puremango.co.uk/about/privacy-policy/" rel="nofollow">http://www.puremango.co.uk/about/privacy-policy/</a>