Freeframe

Do You Need a Privacy Policy on Your Website?

Almost certainly yes. A contact form, analytics or an ad pixel is enough. What US law and your tools require, what to put in it and where to link it.

By
· 9 min read

Almost certainly, yes. If your website has a contact form, a newsletter sign-up, a booking request or a checkout, it collects names, email addresses or phone numbers. California's online privacy law requires any commercial website that collects that kind of information from California residents to post a privacy policy, and since you can't stop Californians from visiting, that covers nearly every US business site. On top of the law, the tools you probably use require one too: Google Analytics, the Meta pixel and the App Store all make a privacy policy a condition of use. A site with no form, no analytics and no third-party scripts may not legally need one, but a short, honest policy costs an hour and removes the question. This is a practical guide, not legal advice. If you handle health, financial or children's data, talk to a lawyer.

The quick answer by situation#

Your site has… Privacy policy needed? Why
A contact, quote or booking form Yes California's CalOPPA covers names, emails and phone numbers collected online
A newsletter sign-up Yes Same reason: an email address is personal information
Google Analytics Yes Google's Analytics terms require a policy that mentions cookies and Analytics
A Meta (Facebook) pixel Yes Meta's Business Tools Terms require a prominent notice on each page with the pixel
An app in the App Store Yes Apple's review guidelines require a link in the app and in App Store Connect
No forms, no analytics, no embeds Probably not by law Still a good idea, and some hosts or embeds set cookies anyway

California's law reaches almost every site#

The California Online Privacy Protection Act, usually called CalOPPA, is Business and Professions Code section 22575. It says the operator of a commercial website that collects personally identifiable information from California consumers must "conspicuously post its privacy policy on its Web site". The law doesn't have a size threshold: a one-person plumbing business is covered the same way as a chain.

"Personally identifiable information" is defined in section 22577 as individually identifiable information about a consumer collected online, and its examples are a first and last name, a home address, an email address and a telephone number. That's exactly what a contact form asks for.

The policy has to cover six things, according to section 22575(b):

  1. The categories of personal information you collect, and the categories of third parties you may share it with (your form service, email provider, analytics).
  2. How people can review and ask you to change their information, if you offer a way.
  3. How you'll tell people about material changes to the policy.
  4. The policy's effective date.
  5. How you respond to browsers' "Do Not Track" signals, if you collect information about people's activity over time and across other sites.
  6. Whether other parties (an ad network, an analytics provider) may collect information about people's activity across sites when they use yours.

"Conspicuously post" has a specific meaning too. A text link on your home page that contains the word "privacy" counts, as does any other link "so displayed that a reasonable person would notice it". In practice that means a Privacy link in the footer of every page.

A site breaks this rule only if it fails to post a policy within 30 days of being told it's out of compliance, so there's no reason to panic if you don't have one today. Just add it.

The bigger state privacy laws probably don't apply to you#

You may have read about the California Consumer Privacy Act (CCPA) or the newer laws in other states. Those come with much heavier duties (rights to delete data, "Do Not Sell or Share" links, data protection assessments), but they only apply above a size threshold.

The CCPA covers a for-profit business doing business in California only if it meets at least one test, according to the California attorney general: annual gross revenue over the threshold, buying, selling or sharing the personal information of 100,000 or more California residents or households, or earning half or more of its revenue from selling their personal information. The revenue threshold is adjusted for inflation every other year and is $26,625,000 since January 1, 2025, at the time of writing.

Other states use similar tests, usually based on how many of their residents' data you process. Four more states passed laws in 2026, according to a July 2026 summary by Morgan Lewis:

State Takes effect Applies if you (any one of)
Louisiana Jan 1, 2027 Have revenue over $25 million; handle data of 75,000+ Louisiana consumers, households or devices; or earn 50%+ of revenue selling personal data
Oklahoma Jan 1, 2027 Process data of 100,000+ Oklahoma residents a year; or 25,000+ and earn over 50% of revenue selling data
Alabama May 1, 2027 Process data of more than 25,000 Alabama consumers (not counting payment-only data); or earn more than 25% of revenue selling data
Vermont Jan 1, 2028 Process data of 35,000+ Vermont consumers, sensitive data of 3,000+, or sell data of 3,000+

A local bakery, salon or contractor is very unlikely to reach those numbers. An online store or an app with a large national audience might, and that's when to get proper legal advice. For everyone else, the simple CalOPPA-style policy below is the right size.

Your tools require one, even where the law doesn't#

Read the terms of the services on your site and you'll find privacy policy requirements in most of them.

  • Google Analytics. The Google Analytics terms say: "You must post a Privacy Policy and that Privacy Policy must provide notice of Your use of cookies." You must also disclose that you use Google Analytics and how it collects and processes data. Google says a prominent link to its page on how Google uses information from sites that use its services does the job.
  • The Meta pixel. Meta's Business Tools Terms require "a clear and prominent notice on each web page where our pixels are used". That notice has to link to an explanation that third parties may collect information from your site for measurement and ad targeting, and how people can opt out.
  • Apps. Apple's App Store Review Guidelines (5.1.1) say all apps must link to their privacy policy both in App Store Connect and inside the app. The policy has to say what data the app collects, how and why; that third parties you share data with protect it as well as you do; and how long you keep data and how someone can ask for it to be deleted.

If you remove the tool, you remove the requirement. That's one more reason to delete scripts you no longer use.

Two federal rules to know about#

There's no general federal law that makes every website post a privacy policy. Two federal rules still matter.

Keep your promises. Once you publish a policy, the FTC expects you to follow it. Its privacy and security guidance puts it this way: "reread your privacy policy to make sure you're honoring the promises you've pledged." A policy copied from a big company that says you never share data, when your form service and email provider obviously receive it, is worse than a short, accurate one.

Children under 13. The Children's Online Privacy Protection Act (COPPA) applies to sites "directed to children under 13" and to general-audience sites with actual knowledge that they collect personal information from children under 13, according to the FTC's COPPA FAQ. The rule was amended on April 22, 2025. A kids' tutoring center, camp or party venue whose forms are filled in by children (not parents) should read that FAQ before launch.

What to put in a small business privacy policy#

Write it in plain English, for your own site. Here's an outline that covers CalOPPA and the tool terms above for a typical small business:

  1. Who you are and how to contact you about privacy (an email address and your business address).
  2. What you collect: what each form asks for (name, email, phone, address, message), and anything collected automatically (analytics data, cookies, IP addresses in server logs).
  3. Why you collect it: to reply to inquiries, send quotes, take bookings, send the newsletter people asked for.
  4. Who you share it with, by category and preferably by name: your form service, email or newsletter provider, booking or payment provider, analytics provider, web host. Say that you don't sell personal information, if that's true.
  5. Cookies and analytics: which tools you use, what they collect, and how to opt out. If you use Google Analytics, link Google's page on how it uses information from sites that use its services. If you use the Meta pixel, explain ad targeting and the opt-out.
  6. Do Not Track: say how you respond. "We don't currently respond to Do Not Track signals" is an acceptable, honest answer if it's true.
  7. How long you keep data and how someone can ask you to see, correct or delete it.
  8. Children: that the site isn't directed to children under 13, if it isn't.
  9. Changes: how you'll announce updates (a note on the page and a new date, for example).
  10. Effective date at the top or bottom.

Most small business policies fit on one screen. The privacy page in the Pocket template shows one way to lay it out: a short summary first, then numbered sections for what's collected, how it's used, who it's shared with, how long it's kept, your rights and how to get in touch.

Before you write, open your site and list everything that loads: every form, embed (maps, video, booking, chat), script and pixel. Your browser's developer tools (the Network tab) show each third-party domain the page contacts. Each one belongs in your policy, or should be removed.

  • Footer of every page. A text link that says "Privacy" or "Privacy Policy" meets CalOPPA's "conspicuously post" test and is where visitors look.
  • Next to forms. A line under the submit button, such as "We'll use your details only to reply. See our Privacy Policy.", helps people decide to fill it in. The forms guide and the post on adding a contact form to a static website show the form markup to add it to.
  • Newsletter sign-ups. Link it beside the email field; see how to add a newsletter sign-up form.
  • WordPress. Go to Settings → Privacy and click Create New Page (or pick an existing page). The new page includes suggested text, and WordPress's own documentation is clear that it's still your job to make the content accurate and current. WordPress shows the link on its login page; your theme decides whether it appears in the footer, so check it does.

Keep it up to date#

A privacy policy goes stale the moment you add a tool. Make it part of your routine:

  • When you add or remove a form service, newsletter provider, booking widget, chat bubble, analytics tool or ad pixel, update the policy and its date the same day.
  • Read it once a year against what's actually on the site. The website launch checklist is a good moment to check it before going live.
  • If you serve customers in the UK or the EU too, their rules on cookies and consent are different. See do you need a cookie banner in the UK.

The short version: if your site collects anything about the people who visit it, post an honest privacy policy, link it in the footer and next to your forms, and keep it matched to the tools you actually use.

About the author

Founder of Freeframe

Paul Peery runs Freeframe, which publishes complete multi-page website templates in HTML, Next.js, Astro and WordPress, and writes about getting small websites built, launched and kept up to date.

Get new templates by email

An email when new templates come out. Confirm by email, unsubscribe any time. How we use your address

Templates for this

Pocket website template preview

A bright launch site for a mobile app, with phone mockups and a scroll-driven feature tour.

HTML + TailwindNext.js (paid)Astro (paid)Nuxt (paid)WordPress (paid)

HTML free · Next.js, Astro, Nuxt & WordPress $19

9 pages · 330 KB

Documentation
Handy website template preview

Handy

Business

A high-trust home services site with an instant quote calculator and service-area checker.

HTML + TailwindNext.js (paid)Astro (paid)Nuxt (paid)WordPress (paid)

HTML free · Next.js, Astro, Nuxt & WordPress $19

10 pages · 146 KB

Documentation

Keep reading