FeaturesCommunityGuidesUse casesCompareToolsBlogPricing
Orlume logo

Does a website need a privacy policy?

If your site collects any personal data, including emails through a form or analytics cookies, privacy laws in many places require a policy. When it applies.

The short answer

Almost certainly yes. If your website collects any personal information, such as names and emails through a contact form, newsletter sign-ups, orders, or data gathered by analytics and advertising tools, privacy laws in many places require a privacy policy explaining what you collect and why. California law and the EU's GDPR are two well-known examples. A purely static site with no forms or tracking is the rare exception.

  • Contact forms, sign-ups, orders and analytics all collect personal data.
  • California requires commercial sites collecting personal information from residents to post a policy.
  • GDPR requires telling people what you collect, why, and their rights.
  • Many third-party tools also require you to have one in their terms.

01When a privacy policy is required

Privacy laws turn on whether you collect personal information, not on your size. A contact form that takes a name and email address counts. So do analytics tools that set cookies or record IP addresses, newsletter sign-ups, orders and account registrations.

Common laws that require privacy notices
LawApplies whenKey requirement
California's online privacy law (CalOPPA)Commercial site collects personal information from California residentsPost a privacy policy conspicuously
EU GDPRYou process personal data of people in the EUExplain what, why, how long, and people's rights
Other US state privacy lawsVaries by state and business sizeDisclosures and rights; check thresholds

02California and the EU in more detail

California's Business and Professions Code section 22575 requires operators of commercial websites that collect personally identifiable information from California residents to conspicuously post a privacy policy describing what they collect and who they share it with. Because a website is visible everywhere, many US businesses outside California follow it.

The EU's GDPR, in Article 13, lists what you must tell people when you collect their data: who you are, why you collect it, the legal basis, who receives it, how long you keep it and their rights, among other things. It applies when you process data of people in the EU, which can include a US business's site visitors.

03What a privacy policy should cover

  • Who you are and how to contact you about privacy.
  • What personal data you collect, including through cookies and analytics.
  • Why you collect it and how you use it.
  • Who you share it with, such as email, payment or analytics providers.
  • How long you keep it.
  • People's rights and how to exercise them.
  • When you last updated the policy.

04How to create one

  1. 1List every data pointForms, analytics, embeds, payment, newsletter tools, ads pixels.
  2. 2List every providerEach service that receives the data.
  3. 3Use a reputable generator or templateThen edit it to match what you actually do.
  4. 4Link it in the footerAnd near forms that collect data.
  5. 5Review it when tools changeAdding a new analytics or chat tool may change what you disclose.

05Common mistakes in small business privacy policies

The usual problems are copying a large company's policy that describes data practices the business does not have, forgetting tools added later (a chat widget, an ad pixel, a booking system), hiding the link where nobody can find it, and never updating it. A policy is a description of what you actually do, so it should change whenever your tools do. Keep a simple list of every service your site sends data to and check it against the policy once or twice a year.

What people who tried it say

Hacker News threads about running a website without legal trouble commonly recommend a clear privacy policy, minimal tracking and honest disclosures, and warn that copied policies describing things a site does not do are a liability of their own.

Looking for more first-hand opinions? Search Reddit for “does a website need a privacy policy”. We link the live threads rather than summarizing them, so you read them in full.

Our take

write a short, honest policy that matches what your site actually does, and collect less data. The easiest privacy policy to keep accurate is one with little to disclose.

Where this falls short

This is general information, not legal advice. Privacy law varies by country and US state, changes frequently and depends on your business size and data practices; consult a lawyer for anything beyond a simple site.

Sources

  1. 1.California Business and Professions Code section 22575 · California Legislature
  2. 2.Art. 13 GDPR: Information to be provided where personal data are collected · gdpr-info.eu

Orlume logoResearched and written by the Orlume team · Updated October 2026

More on small business and portfolios

All 12 small business and portfolios questions →
Questions

People also ask.

More on does a website need a privacy policy, answered briefly.

Do I need a privacy policy if I only have a contact form?

Generally yes. A contact form collects personal information such as names and email addresses.

Do I need a privacy policy if I use Google Analytics?

Analytics tools collect data about visitors, so disclosure is generally needed, and some regions also require cookie consent.

Can I copy another website's privacy policy?

No. Policies are copyrighted, and a copied policy will describe practices that are not yours.

Where should a privacy policy go on a website?

Linked from every page, usually in the footer, and near forms that collect data.

Orlume logoStill stuck? Email us
Orlume logo

Build something that doesn't look AI-made.

Describe the site you want. Watch it get designed, not just generated. Then publish it to its own orlume.site address.

  • Free to start
  • No card required
  • Publish to a live URL
  • You own the code