How to Write a Privacy Policy for Your Website in 2026

Most small business owners skip the privacy policy page until something forces the issue. A payment processor asks for the link. A customer emails to ask what happens to their address. Google AdSense refuses the application until the page exists. Then it becomes urgent, and urgent is a bad way to write a legal page. Underneath the legal language, a privacy policy is a simple idea. It is a plain-language promise that tells visitors what information your website collects, what you do with it, and what choices they have. Writing one takes an afternoon. This guide walks through it step by step.
Do You Actually Need a Privacy Policy?
Short answer: if your website has a contact form, a newsletter signup, a chat widget, analytics, or a checkout, then yes. You are collecting personal information whether you think of it that way or not. A name and an email from a form are the obvious cases. An IP address logged by your analytics tool counts too, and so do the cookies your site sets without asking anyone. Most sites collect data the moment a visitor lands, and the owner is often the last to know.
There is no single US federal law that says every website must have one. That is the honest answer, and it is also the answer that misleads people. California's Online Privacy Protection Act, known as CalOPPA, requires a conspicuously posted privacy policy from any commercial website that collects personal information from California residents. There is no size threshold, and a website cannot keep Californians out, so in practice the law reaches nearly every business site in the country. One legal guide puts it plainly: a website without a privacy policy is a website out of compliance.
The tools you use ask for the page too. Google AdSense, the Apple App Store, and most payment processors require a privacy policy before they will work with you. Skip the page and you can lose an ad account or a checkout with very little warning. A policy is also the cheapest trust signal on your site. Visitors who are about to hand over an email address or a card number look for it, even if they never read a word of it.
What the Law Actually Says (and Where It Gets Confusing)
Start with CalOPPA, the law most small business sites actually trip over. It requires your policy to list the categories of personal information you collect, the categories of third parties you share it with, how a visitor can review or change their information, how you will tell them about changes, and the date the policy took effect. It also asks you to say how you respond to browser do-not-track signals. If you are notified that you are out of compliance, you get 30 days to post a policy before you are treated as in violation.
California added a second, heavier layer with the CCPA, as amended by the CPRA. That one only applies above certain lines: annual gross revenue over roughly $25 million (about $26.6 million after the 2025 inflation adjustment), personal information of 100,000 or more California consumers or households a year, or more than half your revenue coming from selling or sharing personal information. Most small businesses sit below those lines, but California is no longer alone: about 20 states had comprehensive consumer privacy laws in effect by August 2026, including Indiana, Kentucky, and Rhode Island, whose laws took effect on January 1, 2026. The lines keep moving, and a policy written to the strictest law you face usually covers the rest.
Then there is Europe. The GDPR applies to any site that offers goods or services to people in the EU or monitors their behaviour, and running Google Analytics on a site that EU residents visit counts as monitoring. Its fines run up to 20 million euros or 4 percent of worldwide turnover, whichever is higher. Those are maximums, but the law still applies to you. Two more rules worth knowing: COPPA covers sites aimed at children under 13 and demands verifiable parental consent, and the FTC can act when a business breaks the privacy promises its own policy makes. Your policy is a promise, and the promise is enforceable. None of this is legal advice. If your site collects health data, financial data, or children's data, get a lawyer involved before you publish.
What Goes in a Privacy Policy
A clear policy answers the questions a visitor would ask about their data. Treat this as the checklist.
- What you collect. Names, emails, phone numbers, payment details, plus the quiet ones: IP addresses, device information, location, cookies, and pages visited.
- Why you collect it. To answer a quote request, to send the newsletter they asked for, to process an order, to see which pages people read.
- How you collect it. Forms, cookies, analytics, and the third-party tools on your pages.
- Who you share it with. Your host, your email provider, your payment processor, your analytics tool. Name categories, not a fantasy list of partners.
- How long you keep it. "Until the job is done, plus the period we keep invoices" is clearer than "indefinitely", and it has to match what your inbox actually does.
- How you protect it. The steps you take, described in plain terms.
- What choices visitors have. How to opt out of marketing, ask for a copy of their data, or ask you to delete it.
- How to contact you. A real email or phone number for privacy questions.
- The effective date. When the policy took effect and when you last updated it.
One section most small sites forget: the tools. A chat widget, a booking form, an embedded map, or a YouTube video can set its own cookies and collect its own data, so if it is on your site, it belongs in your policy. The BBB says the same thing: say what you do and do what you say, and never copy another company's policy. You can read their tips for writing an effective privacy policy for the same checklist in their words. One more line worth adding: the Global Privacy Control browser signal, which tells websites a visitor wants to opt out of having their data sold or shared. California recognises it as a valid opt-out, and over a dozen states now require sites to honour it.
How to Write One, Step by Step
Step 1: map what you collect before you write a word. Walk through your site page by page and list every place information changes hands: the contact form, the newsletter signup, the booking form, the chat widget, the analytics tag, the payment checkout. Note what each one takes and why. This list, often called a data map, becomes the outline of the policy. Our guide to adding live chat to your website covers the setup side. Remember that a chat widget starts collecting data the moment it loads, not when someone types.
Step 2: write the first draft in plain language. Short sentences, everyday words, no legalese. A visitor should be able to read it in five minutes and know what happens to their email address. If a sentence needs a lawyer to decode it, rewrite it. You can write this draft yourself. Most small businesses do.
Step 3: pick your route. A free privacy policy generator asks you a set of questions and produces a document from your answers. For a simple site that collects names, emails, and standard analytics, that is usually enough. A plain template downloaded from the internet is riskier: it does not know what your site collects, and it goes stale the moment the law changes. A lawyer is the third route, and the cost depends on the scope. Published figures put an attorney-drafted policy at around $500 to start, with rates of roughly $200 to $500 an hour and complex policies running $1,000 to $2,500 or more. Some attorneys charge $2,000 to $5,000 for a policy and terms together. The sources disagree because they describe different jobs, and the honest answer is that the price follows the complexity of what you collect. Get a lawyer when you handle health information, financial data, or children's data, or when a generator cannot describe your data flows. For most brochure sites, a generator plus a flat-fee legal review is the sensible middle ground.
Step 4: publish it where people can find it before they hand anything over. CalOPPA's rule is a conspicuously posted policy, and the standard practice is a Privacy Policy link in the footer of every page, plus a link beside every form. When we build a site, the privacy link goes in the footer on every page and next to every form. If you want that handled as part of the build, look at our web design services. A policy buried three clicks deep does not count as conspicuous, and it does not build trust either.
Step 5: set a review date. A privacy policy is a living document, not a one-time task. Review it at least once a year, and update it the same week you add a new analytics tool, change payment processors, or start an email program. Update the effective date every time you change it, so readers can see it is fresh.
Five Mistakes That Undo a Good Policy
These are the slip-ups we see most often.

- Copying another company's policy word for word. It describes their business, not yours.
- Promising more privacy than you deliver. Saying "we never share your data" while running ad pixels is the classic version. The gap between what your policy says and what your site does is where enforcement actions are born.
- Hiding the policy where nobody can find it. A link in the footer of every page and beside every form is the standard.
- Forgetting the third-party tools. Your analytics, your chat widget, your booking tool, and your payment processor all touch visitor data. If they are not in the policy, the policy is incomplete. Our guide to securing your website from hackers covers the technical side of protecting that data.
- Writing it once and never touching it again. A policy written in 2024 does not describe a site that has added tools since. Review it yearly at minimum.
If your site is missing the page entirely, or the one you have was copied from somewhere else years ago, talk to us and we will tell you what needs fixing. A website audit is a good place to start: it checks for the missing pages, the broken links, and the gaps a visitor notices before you do.
A privacy policy will never be the most-read page on your site. It is not there to be read cover to cover. It is there so that the one visitor who checks, the one customer who asks, and the one regulator who looks all find the same honest answer: here is what we collect, here is why, and here is how to reach us. Write it in plain language, keep it true, and keep it current. If you would like the page built, linked in the footer, and placed beside every form as part of a site that is set up properly from day one, talk to us. We will get it done.
Frequently Asked Questions
Do all websites need a privacy policy?
Not every website is legally required to have one, but most business sites should. California's CalOPPA requires a conspicuously posted policy from any commercial site that collects personal information from California residents, and there is no size threshold. Add the state privacy laws spreading across the US, the GDPR for EU visitors, and the fact that AdSense, app stores, and payment processors all require one, and the practical answer for a business site is yes.
Can I write my own privacy policy?
Yes. Write a first draft yourself in plain language, starting from a list of everything your site actually collects. For a simple site, a free generator plus your own edits is a reasonable start. Have a lawyer review the draft before you publish if you collect health data, financial data, or children's data, or if your site sells online. A policy is a legal promise, so the wording carries weight.
How much does a privacy policy cost?
It runs from free to a few thousand dollars. A free generator costs nothing but an hour or two of answering questions. The article above quotes the published ranges for an attorney-drafted policy, with links to the sources that publish them. The right spend follows how much data you collect and how sensitive it is.
How often should I update my privacy policy?
Review it at least once a year, and update it the same week your data practices change: a new analytics tool, a new payment processor, a new email program, or a new law in a state where your customers live. Refresh the effective date every time you change it, so readers can see it is current.
Muhammad Usman designs and builds high-converting websites for small businesses — and writes practical guides like this one from real project experience.
Keep Reading
Is Your Website Accessible? What Small Businesses Need to Know About ADA Compliance
How to Secure Your Website From Hackers
What Is a Website Audit? What It Checks and Why Your Site Needs One
Need a Website That Actually Performs?
Fixed pricing, professional build, live in weeks. Tell us about your project — free strategy call, no pressure.