Writing a privacy policy for my website: what surprised me.
I wrote a privacy policy for my website, and a few things surprised me.
I'm not a lawyer, and this isn't legal advice. It's just what I learned.
What my site actually collects
Not much. But I had to list all of it:
- The contact form: your name, your email and your message
- The newsletter: your email, and a city if you want to give one
- Page views: which page, where you came from, your screen size and your country
- A code made from your network address, kept for 24 hours to stop spam, then deleted
What surprised me
The map sends your IP address to someone else
My restaurants page has a map. The map pictures come from OpenStreetMap, so your browser asks their servers for them. That means they see your IP address. I don't, but they do. I had to write that down.
My host sets cookies I didn't ask for
I don't use cookies for tracking. But the network my site runs on sets two technical ones to tell people from bots. They don't identify you, but they're still cookies, so they're in the policy.
Counting email opens is tracking
My newsletter can tell if you opened it and which links you clicked. That's tracking, so it has its own section.
I had to pick how long to keep things
I chose 24 hours for the spam code and 13 months for the daily page totals. There's no single right number. You pick one and say it.
The part that mattered most
A privacy policy has to match what the code really does. If it says one thing and the site does another, that's worse than having no policy.
So I tested it. I wrote checks that confirm things like visit rows get deleted and nobody can be added to my newsletter by anyone but themselves.
What I'd tell someone building their first site
Write down what you collect before you write the policy. You'll probably find something you forgot.
Drafted and created with the help of AI.