What a website privacy policy should explain
A privacy policy tells visitors what information a website collects, why, and what happens to it. A generated template is only accurate if it matches what your site really does. This guide explains the usual sections and how to find out what your own site collects first.
Please note: This page is general education, not legal advice. Laws differ by state and change over time. For your own situation, talk to a licensed attorney.
Start with an audit, not a template
The most common privacy policy mistake is describing a site that does not exist. A template might say you collect nothing when your site loads several tracking scripts, or list ten kinds of data when you collect almost none. Before writing a word, find out what the site actually does.
- Open your browser’s developer tools and load each type of page with the Network tab open. List every domain other than your own that receives a request.
- Check the Application or Storage tab for cookies and local storage your site sets.
- List every form: contact, sign-up, checkout, comments. Note each field.
- List every service that touches visitor data: hosting, email, payment, analytics, ads, embedded videos or maps, chat widgets.
- Ask where data ends up: an inbox, a spreadsheet, a database, a mailing list tool.
The usual sections
| Section | What to say |
|---|---|
| Who is responsible | The person or organisation running the site and how to contact them. |
| What is collected | Information people give you, and information collected automatically. |
| Why | The purpose for each kind of data, such as replying to messages or processing orders. |
| Cookies and similar tools | What they are for, and how visitors can control them. |
| Sharing | Which kinds of service providers receive data, and whether data is sold. |
| Retention | How long each kind of data is kept. |
| Security | The general measures used to protect data. |
| Choices and rights | How someone can access, correct or delete their information, or opt out. |
| Children | Whether the site is aimed at children and how their data is handled. |
| Changes | How updates to the policy are announced. |
Write it in plain language
A policy that visitors can understand is more useful than one written to sound legal. Compare:
Unclear: “We may collect certain information to enhance user experience and for other legitimate purposes.”
Plain: “When you use the contact form, we receive your name, email address and message. We use them only to reply to you. We delete messages after twelve months.”
Use the second style. Name categories of providers (“our email provider”, “our payment processor”) and keep the wording consistent with what your audit found.
Laws differ by place
Several US states and other countries have privacy laws that give people specific rights or require particular disclosures. Whether a law applies can depend on where your visitors live, the size of your business and what you do with the data. A template or generator cannot decide that for you. Check official guidance from your state attorney general or the FTC, and ask a licensed attorney if you are unsure which rules apply.
Common mistakes
- Copying another site’s policy, including services you do not use.
- Forgetting third-party embeds, which can set their own cookies.
- Promising things you do not do, such as deleting data on request when you have no process for it.
- Never updating the policy after adding a new tool or form.
- Hiding the link where nobody can find it. A footer link on every page is normal.
Keep it current
Treat the policy as part of the site, not a one-off document. Whenever you add a script, form, plugin or service, repeat the audit for that change and update the policy the same day.
Questions
Does a site that collects nothing need a privacy policy?
A short page that states what the site does and does not collect is still helpful to visitors, and the audit often reveals data you did not realise was collected.
Can a generator make my site compliant?
No tool can guarantee compliance. A generator gives a draft; accuracy depends on your audit, and legal obligations depend on your situation.