"Before generating a privacy policy you must register or login".
(a) that's irritating - if you're going to demand registration do it as the very very first thing so I know. I don't care if all I've entered is a domain name.
(b) ironically I can't see your privacy policy to see what you might do with the e-mail address I'm giving you.
And then I seem to be able to cancel the registration login and continue anyway and generally arghhh it's all a bit horrible.
It looks like a nice service, it was just a few rough edges in the first 60 seconds that put my back up.
Make it clear registration is required (or not - am still not clear how long I can duck it for - I'd actually say if it's needed make me do it straight away so I'm clear on that) and show the privacy policy up front and it's would be nice.
Out of interest why do you demand registration? Not being argumentative, just curious.
The reason why we decided to require a registration on the first page is that many visitors started playing with the generator and had no way to register (and to stay up to date) before completing the second step.
This caused confusion and many left the website right after reaching the first step.
So we decided to place the registration on the first generation page, something we did very quickly two days before the launch (happened one week ago).
The fact that it was a quick&dirty move caused part of the issues that you suggested to fix :)
It looks very nice, but I'm a little confused as to what should be included as a service. My website has forums. Do I need to say I collect user comments? Do I need to do that for all user-contributed information? How specific does it needs to be? If users can contribute books, do I need to specify that I collect isbn numbers?
Thank you for the question. You need to inform the user about the personal data collected. Examples of personal data are cookie, email, username, name, date of birth. I suggest you to add everything you recognize as used on your website.
If your website has a blog or a form, I also suggest you to create a different privacy policy just for each of them.
Thank you for asking, and let me know if you have any other question :)
Hacker News has long been ok with people posting their own stuff. If you've worked long and hard on something, be proud of it and show it off, within reason (don't post the same thing day in and day out).
What looks more dubious are all the new accounts signing up just to write pithy comments. That'll get you banned if you're not careful, Andrea.
They are not, you need both. The privacy policy is required by law and needs to state all the personal information you collect from users.
The TOS is a "contract" that states what the users can and can't do with your service, and what you can and can't do with their accounts etc.
Think about it as a usage agreement.
Then
"Before generating a privacy policy you must register or login".
(a) that's irritating - if you're going to demand registration do it as the very very first thing so I know. I don't care if all I've entered is a domain name.
(b) ironically I can't see your privacy policy to see what you might do with the e-mail address I'm giving you.
And then I seem to be able to cancel the registration login and continue anyway and generally arghhh it's all a bit horrible.
Pity, seems like a nice service.