
Most people ask this question right after they add a contact form or install analytics and wonder whether anything changed. It did. The moment a stranger can type an email address into your site, you are holding personal data.
This guide walks through how to check your own site in about ten minutes, with three common examples so you can see what a real policy needs to say.
The short answer
If your site has a contact form, newsletter sign-up, login, shop, comments or analytics, it collects personal data, and you almost certainly need a privacy policy. Many laws expect one, and platforms such as app stores, ad networks and payment providers usually require a link to it.
What counts as personal data
An email address, a name, an IP address, a cookie identifier or a message all count. You do not need to run a big business for this to apply.
When you may not need one
A static page that collects nothing, sets no cookies and embeds nothing may not need a policy. That is rarer than people expect, because fonts, maps and videos loaded from other services can collect visitor data.
What goes in it
Who you are, what you collect, why, who receives it, how long you keep it and how people can use their rights. Name the tools you use, such as your email service and analytics.
What to do next
Write it from your own setup instead of copying another site. Review it whenever your tools change.
A ten minute check
Open your site in a private window and click through it like a visitor. Note every form, login, comment box, shop and booking button. Then open your browser's developer tools, look at the network tab and write down the outside domains that load, such as analytics, fonts, chat widgets and video players. Each line on that list is something your policy may need to name. Do the same for your email service and any form tool, because they receive whatever visitors type.
Three examples
A freelancer's portfolio with a contact form collects names, email addresses and messages. A small shop collects delivery addresses and order history, and passes some of it to a payment provider and a courier. A newsletter collects email addresses and often tracks opens and clicks. The three policies look different because the data, and the people who receive it, are different. That is why a copied policy rarely fits.
Where visitors expect to find it
Put a link in the footer of every page and next to any form or checkbox where someone gives you data. Call the page Privacy Policy so people and app stores can find it. If you run a shop, link it at checkout as well. A policy that sits three clicks deep does very little.
When things change
A policy is not carved in stone. When you add a tool, remove one or start collecting something new, change the page and update the date. Keep old versions if you can, so you can show what you said and when.
A quick checklist
- Every form and login on your site is on your list.
- Every outside service that loads on your pages is on your list.
- Your policy says who you are and how to reach you.
- There is a footer link on every page.
