← All posts
Data Privacy Compliance for Small BusinessesNovember 15, 2026 · 5 min read

Your privacy policy should be readable. Here's what it needs to say

Most privacy policies are copy-paste walls nobody reads. A good one is short, honest, and specific about your business — here is what belongs in it.

Open a random small business website and read its privacy policy. Most of the time you will find one of two things: nothing at all, or a wall of dense text copied from somewhere else that describes a business nothing like the one you are looking at.

Neither is good enough. A privacy policy is a promise to your customers about what happens to their information. If it is missing, customers cannot find the promise. If it is copied, the promise is false. A good policy is short, honest, and specific to your business — and writing one is mostly a matter of answering a few plain questions.

This is general guidance, not legal advice. But if you can answer the questions below truthfully, you can write a policy that actually means something.

What do you collect?

List it in plain language. Names, email addresses, phone numbers, addresses, payment information, appointment details, messages sent through your contact form — whatever applies to your business. Be concrete. "Contact information" is vague; "your name, email, and phone number so we can confirm your booking" is a promise a customer can understand.

If your website uses analytics or advertising tools that collect visitor data, say that too, and name the tools. People are not surprised that a website uses analytics. They are surprised when they find out later that nobody told them.

Why do you collect it?

Every item you collect should have a reason, and the reason should be in the policy. "We collect your phone number to confirm and reschedule appointments." "We collect your email to send receipts and appointment reminders." "We collect your address because we deliver to your home."

If you cannot explain why you collect something, that is a sign to stop collecting it — not a reason to write a vaguer sentence.

Who else sees it?

Your customers' data does not only live with you. It passes through your payment processor, your booking system, your email provider, and any other tool that handles it. Name those categories — and the providers, if you are willing to be specific. "We share your information with our payment processor to take payment, and with our booking system to manage appointments. We do not sell your information."

That last sentence matters. If you do not sell customer data, say so plainly. If you do share data for advertising, say that plainly too, and say how someone can opt out. Honesty here builds more trust than any amount of careful wording.

How long do you keep it?

Say how long data stays with you, in terms a customer can follow. "We keep booking records for one year, invoices for as long as our accountant requires, and marketing emails until you unsubscribe." Then actually follow the schedule you wrote down. A retention promise you do not keep is worse than no promise at all, because it shows you wrote the policy and then ignored it.

What rights do people have, and how do they use them?

In many places, customers have the right to ask what you hold about them, to correct it, and to ask you to delete it. Your policy should say how: an email address, a simple instruction, and what will happen next. "Email us at this address and we will send you a copy of the information we hold within a reasonable time." Then make sure someone actually monitors that inbox.

What about cookies and tracking?

If your site uses cookies, analytics, or tracking pixels, say what they do and how a visitor can control them. Most website builders and analytics tools have a simple setting for this. You do not need a long technical explanation — a short paragraph and a link to the tool's own controls is enough.

How do people contact you, and what happens when this changes?

Put a real contact — an email address someone monitors — in the policy. And include a line about changes: "If we change this policy, we will update the date at the top and post the new version here." Then do exactly that. A policy with a date on it is a living document; a policy without one looks abandoned.

Do not copy someone else's policy

A copied policy will describe tools you do not use, data you do not collect, and practices you do not follow. It also tends to be written in language your customers cannot understand, which defeats the purpose. Worse, if a customer or a regulator ever asks you to explain a line in your own policy, "we copied it" is not an answer.

Write your own, in your own words, based on the real answers to the questions above. Shorter is better. If a customer can read it in three minutes and understand what happens to their information, it is doing its job.

Keep it current

A privacy policy goes stale the moment you add a new tool, start a new kind of marketing, or change how you take payments. Review it whenever your business changes how it handles data — and at least once a year. Put the review on the calendar, next to the other maintenance that keeps a business running.

A readable privacy policy is not a legal shield. It is a sign that a business knows what it holds, why it holds it, and who it answers to. Customers notice that, even if they never read the whole page.

We help small businesses get audit-ready for SOC 2, HIPAA, and ISO 27001. Compliance Readiness starts at $995 for a first engagement ($1,500 standard).

Get help getting audit-ready →