Step 1 of 10 · Getting Started

Free Website Privacy Policy Template

Your answers save as you go. Legal form tools, not legal advice.

Free template

Download a free website privacy policy template

Free blank form—no account or payment required. The PDF is printable and the Word file is editable. This general version does not include state-specific clauses or disclosures.

Build a guided state-specific version
BusinessLast updated November 14, 20268 min read

What is a website privacy policy?

A website privacy policy is a public statement of how a business handles the personal information it gathers online. It tells visitors what you collect, how you collect it, why you use it, who receives it, how long you keep it, and what choices they have. You post it on your site, link to it from every page, and keep it current as your tools change.

Unlike most documents on LawVault, a privacy policy is not signed. It is a notice. That makes accuracy the whole game: regulators such as the Federal Trade Commission treat a policy that misdescribes your real practices as a problem in its own right. A short policy that tells the truth beats a long one copied from a bigger company's site.

Our builder writes the policy from your answers about your site, your data and the services you use, so each section reflects what you actually do. Anything you don't do stays out.

Key features
  • Five site types with their own wording: business website, online store, blog, mobile app plus website, and SaaS or web app
  • A data checklist covering contact, account, payment, device, location, cookie and user content data, with approximate or precise location
  • Cookie and tool disclosures for analytics, advertising pixels, email marketing and payment processors, including the Google Analytics opt-out link
  • A clear statement on selling data and targeted advertising, with your opt-out link when you share data for ads
  • Children's privacy text for general-audience sites or a COPPA parental consent section for child-directed services
  • Optional California (CalOPPA and CCPA), other-state and EU and UK sections, plus Do Not Track and Global Privacy Control statements
  • No signature lines: the finished policy ends with your contact details, ready to publish

Types of privacy policies

The builder starts by asking what the policy covers, because an online store and a SaaS product collect different things for different reasons.

Business Website Privacy Policy

For a company site with contact forms, newsletters or analytics, where visitors mainly browse and get in touch.

Create

Online Store Privacy Policy

Adds billing and shipping details, order processing, payment processors and cart cookies.

Create

Blog or Content Site Privacy Policy

Covers comments, subscriptions, analytics and advertising on a publishing site.

Create

Mobile App Privacy Policy

Covers the app and the website together, with device identifiers, crash reports and device permissions such as location.

Create

SaaS Privacy Policy

Separates your own visitors’ data from the customer data your business clients store in your product, which their own policies govern.

Create

When you need a privacy policy

You need one as soon as your site or app collects personal information, which happens sooner than most owners think. A contact form collects names and email addresses. A server log records IP addresses. An analytics script or advertising pixel collects browsing data for a third party. Typical triggers:

  • You launch a website with a contact form, newsletter signup or analytics
  • You sell products online or take payments through a processor
  • You publish an app in an app store
  • You run ads that use pixels to retarget visitors
  • You expand to customers in California, another privacy-law state, or Europe

Update the policy whenever you add a tool, start a new use of data, or change who receives it. If the CCPA applies to you, it requires the policy to be updated at least once every 12 months (Cal. Civ. Code § 1798.130(a)(5)).

Privacy policy vs. terms of use

People often post the two side by side, but they do different jobs. A privacy policy is a notice: it describes how you handle personal information and what rights visitors have. Terms of use are a contract: they set the rules for using the site, limit your liability and say how disputes are handled.

You can have a privacy policy without terms of use, and many small sites do. The reverse is rarely wise, because the laws above require the privacy notice whenever you collect personal information.

Selling data and targeted ads

Many site owners answer "no, we don't sell data" without checking their ad setup. Under California law, "sharing" includes letting an advertising platform collect data from your site to target ads across other sites, even when no money changes hands. If you run retargeting pixels, the honest answer is usually that you share data for targeted ads. The builder flags this when you tick advertising pixels, prints your opt-out link, and adds a Global Privacy Control statement that matches your choice.

What a privacy policy should include

California's CalOPPA sets the floor for most U.S. sites, and the builder covers every item it lists for all users, not only Californians.

  • Information collected: the categories of personal information you gather and where they come from.
  • Uses: each purpose, from running the site and processing orders to marketing, analytics and ads.
  • Cookies and tools: the tracking technologies on the site and the outside services that receive data.
  • Sharing: the categories of third parties that receive personal information, and whether you sell it or share it for targeted ads.
  • Retention and security: how long you keep data and the safeguards you use, without promising perfect security.
  • Children: whether the service is directed to children under 13, and what happens if a child's data is collected.
  • Choices and requests: how users unsubscribe, manage cookies, and ask to review or correct their information.
  • Do Not Track: how the site responds to Do Not Track signals, and whether other parties track users across sites.
  • Changes and effective date: how you announce material changes and when the current version took effect.
  • Contact details: who runs the site and how to reach them about privacy.

Sample privacy policy

The sample below shows how a finished policy is organized, from the effective date and the data collected through sharing, rights sections and contact details.

Preview the document your answers produce — then build your own in minutes.

Build my privacy policy

Privacy laws that shape your policy

There is no single U.S. privacy law. A policy for a typical small business is shaped by a California notice law that applies to almost everyone, plus other laws that apply only when you cross a threshold or serve a particular audience.

Laws that commonly apply to websites and apps

LawWho it coversWhat it means for the policySource
CalOPPAAny commercial site or online service that collects personally identifiable information from California residentsPost a policy listing data categories, third-party recipients, the review and change process, how changes are announced, the effective date, the Do Not Track response, and whether others track users across sitesCal. Bus. & Prof. Code §§ 22575-22579
CCPA / CPRAFor-profit businesses doing business in California with $26.625 million or more in revenue, or 100,000+ California consumers or households, or 50%+ of revenue from selling or sharing dataDescribe rights to know, delete, correct, opt out of sale or sharing, and limit use of sensitive data; honor Global Privacy ControlCal. Civ. Code § 1798.100 et seq.; cppa.ca.gov
COPPASites and apps directed to children under 13, or that know they collect a child's informationVerifiable parental consent before collection; parents can review and delete a child's data15 U.S.C. §§ 6501-6506; 16 CFR part 312; ftc.gov
CAN-SPAMBusinesses sending commercial emailEvery marketing email needs a working way to unsubscribeFTC CAN-SPAM compliance guide
GDPR and UK GDPRBusinesses offering goods or services to people in the EU or UK, or monitoring their behavior thereState legal bases, user rights, international transfer safeguards and the right to complainRegulation (EU) 2016/679, Arts. 3, 6, 13-22, 46, 77

Thresholds in other state consumer privacy laws

StateLaw applies to a business that, in a year, handles personal data ofSource
Virginia100,000 Virginia consumers, or 25,000 and earns over half its gross revenue from selling personal dataVa. Code § 59.1-575 et seq.
Colorado100,000 Colorado consumers, or 25,000 and earns revenue or gets a discount from selling personal dataColo. Rev. Stat. § 6-1-1301 et seq.
Connecticut35,000 Connecticut consumers (from July 1, 2026), or any amount of sensitive data, or offers personal data for saleConn. Gen. Stat. § 42-515 et seq., as amended by SB 1295 (2025)
Texas and NebraskaAny amount, unless the business is a small business under federal SBA standardsTex. Bus. & Com. Code § 541.001 et seq.; Neb. Rev. Stat. § 87-1101 et seq.
Oregon100,000 Oregon consumers, or 25,000 and earns 25% or more of gross revenue from selling personal dataORS 646A.570 et seq.
Montana25,000 Montana consumers, or 15,000 and earns more than 25% of gross revenue from selling personal data (from October 1, 2025)Mont. Code Ann. § 30-14-2801 et seq., as amended by SB 297 (2025)
Delaware35,000 Delaware consumers, or 10,000 and earns more than 20% of gross revenue from selling personal data (from January 1, 2027: 10,000, or 5,000 and more than 20%)6 Del. C. § 12D-103
Maryland, Rhode Island35,000 state consumers, or 10,000 and earns more than 20% of gross revenue from selling personal dataMd. Code, Com. Law § 14-4702; R.I. Gen. Laws § 6-48.1-1 et seq.
New Hampshire35,000 New Hampshire consumers, or 10,000 and earns more than 25% of gross revenue from selling personal dataRSA 507-H
New Jersey100,000 New Jersey consumers, or 25,000 and earns revenue or gets a discount from selling personal dataP.L. 2023, c. 266
Utah$25 million or more in annual revenue, and 100,000 Utah consumers or 25,000 with over half of gross revenue from selling personal dataUtah Code § 13-61-101 et seq.
Indiana, Iowa, Kentucky100,000 state consumers, or 25,000 and earns over half of gross revenue from selling personal dataInd. Code § 24-15-1-1 et seq.; Iowa Code § 715D.2; KRS 367.3613
Minnesota100,000 Minnesota consumers, or 25,000 and earns over 25% of gross revenue from selling personal dataMinn. Stat. § 325M.10 et seq.

Counts exclude data handled only to complete a payment in several states. Tennessee’s law is not shown. Thresholds change; confirm the current statute before relying on this table.

Two practical points come out of these tables. First, CalOPPA has no size limit, so even a one-person shop with a contact form should have a policy that meets it. Second, the bigger state laws turn on volume, so a small business often has no duty to offer their rights. Many small businesses describe those rights anyway with a "where the law applies to us" qualifier, which is how our template words them.

Describe what you really do

A privacy policy only protects you if it matches your actual practices. Check your plugins, tag manager and email tools before you answer, and update the policy when they change. If your service is aimed at children, handles health or financial data, or sells personal information, have a privacy lawyer review it. LawVault is a document service, not a law firm, and this page is general information, not legal advice. The policy describes your practices; it does not by itself make you compliant with any law.

How to create your privacy policy

You can download the free blank template and fill it in yourself, or answer guided questions and let the builder assemble the policy. The builder adds the right wording for your site type and prints only the sections that apply.

  1. Pick your site type and stateChoose business website, online store, blog, mobile app plus website, or SaaS, then the state where the business is based.
  2. Enter your business detailsAdd the legal name, any brand or app name, the site address, the effective date, and a privacy contact email.
  3. List the data and purposesTick the kinds of personal information you collect, how exact any location data is, and each purpose you use it for.
  4. Name your tools and sharingTick analytics, advertising pixels, email and payment services, choose who receives data, and say whether you sell it or share it for targeted ads.
  5. Set retention, security and childrenState how long you keep data and your safeguards, then say whether the service is meant for children and set a minimum age.
  6. Add choices and law sectionsChoose the user controls you offer and how you treat Global Privacy Control, then add California, other-state or EU and UK sections.
  7. Review and publishChoose how you will announce changes, add any extra terms, then download the PDF or Word file and link it from every page of your site.

A good privacy policy is short enough to read, specific about your tools, and honest about what you share. Publish it before you start collecting data, link it from your footer and any signup form, and revisit it whenever you add a new service. If you also share confidential business information with contractors or partners, pair it with a non-disclosure agreement, and set out client work terms in a service agreement.

Common questions

Almost certainly, if the site collects any personal information. California's Online Privacy Protection Act (Cal. Bus. & Prof. Code § 22575) requires any commercial website or online service that collects personally identifiable information from California residents to post a privacy policy, with no size or revenue threshold. Because California visitors can reach nearly any site, most U.S. businesses fall under it. Other laws, such as the CCPA, COPPA and the GDPR, add requirements when they apply.

Yes. The PDF and Word files are free to download without an account. The PDF is a printable blank, not a fillable form; use the Word file or the guided builder to type your terms.

No. A privacy policy is a published notice, not a contract that the business and its visitors sign. Our builder produces a policy with no signature lines. You post it on your site, usually linked from the footer of every page, and CalOPPA expects the link to be conspicuous.

Only if you meet one of its thresholds. The California Privacy Protection Agency lists them as gross annual revenue of $26.625 million or more (the 2025 inflation-adjusted figure), buying, selling or sharing the personal information of 100,000 or more California residents or households, or earning 50% or more of annual revenue from selling or sharing California residents' personal information (cppa.ca.gov). CalOPPA still applies to smaller sites.

As of late 2026, comprehensive laws are in effect in 18 states besides California, including Virginia, Colorado, Connecticut, Texas, Oregon, Montana, New Jersey, Maryland, Minnesota and Indiana. Most apply only above a threshold, such as handling the personal data of 100,000 state residents a year (35,000 in Connecticut, Delaware, Maryland, New Hampshire and Rhode Island). Texas and Nebraska instead exempt businesses that are small under federal SBA standards.

The federal Children's Online Privacy Protection Act covers sites and apps directed to children under 13, and general-audience sites that know they are collecting a child's information. Those operators must get verifiable parental consent before collecting personal information and let parents review or delete it (ftc.gov COPPA FAQs). Our builder prints a parental consent section, but a child-directed service also needs a direct notice to parents and legal review.

If the CCPA applies to you, yes. The California Privacy Protection Agency says businesses must honor opt-out preference signals such as Global Privacy Control as a valid request to opt out of the sale or sharing of personal information. Colorado's attorney general recognizes Global Privacy Control as a universal opt-out mechanism that businesses covered by the Colorado Privacy Act must honor, starting July 1, 2024 (coag.gov/uoom). Our builder lets you state how your site responds.

Add one if you offer goods or services to people in the European Union or the United Kingdom, or monitor their behavior there; the GDPR can reach businesses outside Europe in those cases (GDPR Article 3). The section in our builder covers legal bases, user rights, international transfers and the right to complain to a data protection authority.

Still unsure? Visit the help center.

Ways to get your privacy policy

Answer the questions and preview the finished document free. You pay only when you’re ready to download, print or e-sign it, and you can choose how.

Free 7-day trial subscription Cancel anytime

$49/mo $0 for one week

Unlimited access to 210+ legal documents for 7 days. After the trial it renews at $49 a month unless you cancel at least 24 hours before it ends.

Start 7-day trial

Pro, billed yearly

$9.99/moBest value · Save 80%

Unlimited documents and edits, e-signature for every party, and the freedom to amend and re-issue at any time. Billed $119.88 a year and renews annually. Cancel anytime.

Start annual plan

Single document

$39One-time, no renewal

Unlock just this privacy policy: a permanent PDF download, printing, e-signature for every party and a tamper-evident audit trail, with no subscription.

Build this document

Prices in USD. Free blank templates stay free. Compare plans or read the refund policy.

Build your privacy policy in minutes

Preview the document your answers produce — then review, e-sign, or download it.

State-specific · E-sign ready · Legal form tools, not legal advice