Does a small business site need a privacy policy, and who should write it
What your site is quietly collecting right now
"The booking software just asked me to paste a link to my privacy policy, and I don't have one." That's the moment this usually starts. Not a compliance deadline. A dropdown menu that won't let you continue.
Most brochure sites collect more than the owner realizes. A contact form stores a name, an email, sometimes a phone number, in a database or an inbox somewhere. An analytics script drops a cookie and logs an IP address.
A chat widget from a third party can see everything a visitor types before they hit send. None of that required anyone to flip a switch labeled "collect data." It came bundled with tools a designer installed to make the site work.
An embedded video player, a social media follow button, and a newsletter signup box each work the same way. Each one is a small outside company with its own eyes on part of what happens on your page, quietly, in the background, whether anyone reads the fine print or not.
The starting point for a policy isn't legal language. It's an honest list of what actually touches a visitor's information. Walk every page. Check every embedded script, form, and widget. Write down what you find before you write a word of the policy itself.
A form is also where the collecting happens directly, and what a form should say when someone gets something wrong is a related but separate design question worth reading once you've mapped out the rest.
A policy only works if it's actually true
A privacy policy is a description, not a decoration. It has to say, plainly, what gets collected, why, who sees it, and how long it sticks around. If the policy says data is never shared and a booking tool quietly forwards names to a payment processor, the policy is wrong the moment it's published.
That gap is the real risk here. Not the absence of a document, but a document that describes a site you don't actually run. A reader can tell the difference, and so can a regulator.
Three things belong in nearly every policy for a small business site. What's collected through forms and cookies. Which outside tools receive any of it. How a visitor can ask what's on file about them.
Skip the legal padding. A visitor reading it wants a straight answer, not a wall of text copied from a company ten times your size.
Generators and templates, and what they get wrong locally
A generator or a template built for small sites will get the shape right. Sections for contact data, cookies, third-party tools, and a contact method for privacy questions. For a site that's genuinely simple, a form and an analytics script and nothing else, that's often close enough with a few blanks filled in honestly.
Where generators fall apart is anything specific to how your site actually works. They don't know which booking platform you use. They don't know whether it stores cards. They don't know whether a chat tool routes conversations through a server outside the country you operate in.
A generated policy that lists cookies you don't use and skips the ones you do isn't a safety net. It's a document that contradicts your own site the first time anyone checks. Fill in every blank yourself, or the generator is just guessing on your behalf.
The point where the answer is a lawyer rather than a template
There's a point where the honest move is to stop editing a template. Get a professional read before you sign anything else off. That point looks specific, not vague.
You're collecting payment information directly. You operate somewhere with its own particular disclosure rules. You handle anything sensitive, health information, anything about children, biometric data of any kind. Any one of those is enough on its own.
None of that is common for a brochure site with a plain contact form. It shows up the day you add booking, deposits, or an account system. A short conversation with someone who knows privacy law in your jurisdiction, at that point, saves more trouble than guessing ever will.
Keeping the policy honest after you add a booking tool
A policy written before you added a booking tool describes a site that no longer exists. This is the part owners miss. The policy isn't a one-time task. It's a document tied to what the site currently does, right now, not what it did a year ago.
Every time a new form, a new plugin, or a new payment step gets added, the honest move is to open the policy and check whether it still describes reality. Five minutes with the document, each time something changes, beats a rewrite from scratch later.
The same discipline applies to the terms of use page, which is a different document doing different work but needs to stay in step with the same changes. If a booking flow changes, both documents deserve a look, not just whichever one happens to be top of mind.
Where the link belongs and who has to be able to reach it
The policy has to be reachable from anywhere a visitor might want it. Not just the footer of the homepage. The checkout flow. The booking form. Any page that collects an email address.
A booking platform that asks for a policy URL during setup is checking that the link resolves and says something real. It isn't checking that the document exists in principle somewhere on the internet.
If a QR code on a printed flyer sends someone straight to a booking form, that same form still needs the link nearby, not just the homepage three taps away. A visitor who scanned a code in a hurry won't go looking for it.
Consent for cookies is a related but separate mechanism from the policy itself, and whether your site needs a cookie banner depends on which tools you're running. Once that's sorted, the policy stops feeling like an isolated chore. It becomes one piece of why accessibility and this kind of housekeeping sit in the same cluster.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go