What a Small Business Website Privacy Policy Must Say
Short answer: A privacy policy for a small business website should say what personal information you collect, why you collect it, who receives it, how long you keep it, what rights people have and how to contact you about their data. The most reliable way to write it is to start from an inventory of every tool on the site, such as contact forms, analytics, payment services and email software, and describe each one in plain words. Check the current guidance from your data protection regulator, because the exact wording depends on where you operate and who your visitors are. Review the policy whenever you add or remove a tool.
Start with an inventory, not a template
Most privacy policy templates are written for a generic site. They describe cookies, newsletters and online purchases in broad terms, and they often claim things your site does not do. Begin instead by listing every point where personal data enters or leaves your website.
A yoga studio in Bristol, Still Point Studio in this example, runs a class booking form, a newsletter sign-up, a payment provider for memberships and an analytics tool. The owner lists each one in a spreadsheet, with columns for what data is collected, where it is stored, who processes it and how long it is kept. That spreadsheet becomes the source for the policy, and it also helps answer questions from clients.
The sections your policy should contain
A clear structure makes the policy easier to read and easier to update. A typical small business policy includes these sections.
- Who we are. The legal name of the business, its address and a contact email for privacy questions.
- What we collect. Names, contact details, booking preferences, payment references, device and usage data, and anything else from your inventory.
- How we collect it. Directly from the person through a form, automatically through the site, or from a third party such as a booking platform.
- Why we use it. Each purpose, such as replying to an enquiry, taking a payment, sending a newsletter or measuring site traffic.
- Who we share it with. The categories of service providers, such as payment processors and email platforms, without needing to list every vendor.
- How long we keep it. A period or the rule used to set it, such as "enquiries are deleted after twelve months if no client relationship follows".
- Your rights. How people can access, correct or delete their data, and how to object to marketing.
- Cookies and similar technology. What is set, why and how to change the choice.
- Changes to this policy. How updates are published and the date of the latest version.
Explain purposes in plain language
The most common weakness in small business policies is vague purposes. "We may use your data to improve our services" tells a reader almost nothing. Write each purpose as a specific action: "We use your booking details to confirm your appointment and send one reminder by email." That sentence says what happens, to whom and why.
Be exact about marketing. If a customer books a class, you can usually use their details to manage that booking. Sending a newsletter is a separate purpose, and the policy should explain how people opt in or out.
Name the third parties in categories
You do not have to name every software tool in the policy, but you should describe the kinds of organisations that receive data. For a studio, that might be "our booking platform", "our email provider" and "our payment processor". Where a service is located outside the United Kingdom, say so and explain the safeguard that applies in general terms. Check the official guidance on international transfers before you publish that statement.
If your analytics tool sets cookies, the policy must match what the cookie banner says. Mismatches between the two are easy to spot and are a common reason for complaints.
Retention periods that you can keep
A retention period is a promise, so it must be realistic. Decide how long each category of data is needed, then set a routine to delete it. For example, you might keep booking records for the period needed for tax and client care, and delete an unsuccessful enquiry after a set number of months. Put the schedule in your calendar, and ask whoever manages the site to confirm that deletion happens.
Link to the policy and keep it current
Put a link to the privacy policy in the site footer, on every form and next to any sign-up button. Make the link readable on a phone. Once a year, or when you add a tool, review the policy against your inventory spreadsheet and update the date at the top.
The ICO publishes guidance for organisations on privacy notices, and that guidance is a good reference when you draft or check your wording. Treat any template as a starting point, not a finished document. Check that the link works after every site update too, because a broken link in a footer is easy to miss and hard to defend.
A short review checklist
- [ ] Every form, tool and integration appears in the inventory
- [ ] Each purpose is written as a specific action
- [ ] Third-party categories listed and locations stated
- [ ] Retention periods match real deletion routines
- [ ] Rights and contact route for privacy questions are clear
- [ ] Cookie policy matches the cookie banner
- [ ] Policy linked from the footer and forms, with a date
FAQ
Do I need a privacy policy if my site only has a contact form?
Yes, because a contact form collects personal data. The policy can be short, but it should still explain what you collect, why and how long you keep it.
Can I copy a privacy policy from another website?
You can use it as a reference, but it will describe that business's tools and purposes, not yours. Copying it is a common cause of inaccurate policies.
How often should I update it?
Review it whenever you add or remove a tool and at least once a year. Update the date at the top each time you change the wording.
A tool inventory is the hardest part of a privacy policy to do alone, so if you get stuck, the enquiry form will reach us.