What a privacy policy is for
A privacy policy tells people what personal information you collect, what you do with it and who you share it with. Many laws, app stores, ad networks and payment providers expect one wherever you collect even a contact form email.
Who needs one
Almost every site that has a contact form, newsletter sign-up, account, analytics tool, shop or embedded service needs one. If your site collects nothing at all and sets no cookies, you may not, but that is rarer than people think.
What your privacy policy covers
What the wizard asks you
These are the kinds of questions. Each one explains why we ask it, and you can skip what does not apply.
- Question 1What does your site do, and where are your visitors?
- Question 2Which details do you collect, and from whom?
- Question 3Which outside tools handle that data (email, analytics, payments, chat)?
- Question 4Do you use cookies or similar technologies?
- Question 5How can people contact you about their data?
A sample clause
Your real text is built from your answers. This is an example of the plain style we aim for, with the parts you fill in shown in brackets.
When you send us a message through our contact form, we collect your name, your email address and the text of your message. We use them only to reply to you and to keep a record of our conversation. We keep messages for [12] months, then delete them. Our form is provided by [form provider], who handles the data for us.
Sample text for illustration. Your page is written from your own answers.
Mistakes we see most
- Copying another company's policy. It describes their tools, not yours, and can promise things you do not do.
- Listing tools you stopped using, or missing ones you added. Review the policy whenever your tools change.
- Saying you never share data while using an analytics or email service. Those are sharing, and the policy should say so.

