Not sure what your site’s policy has to say? The core privacy policy requirements are what data you collect, why, who gets it, and what choices users have. Which laws apply depends on where your visitors live.
This page sits within the wider topic of business data privacy.
| Item | Value |
|---|---|
| CalOPPA effective date | July 1, 2004 |
| CalOPPA amended to address online tracking | 2013 |
| CCPA revenue threshold | Over USD 26,625,000 gross annual revenue |
| CCPA consumer threshold | 100,000 or more California residents or households |
| CCPA share of revenue from selling personal information | 50 percent or more of annual revenue |
These figures come from Usercentrics’ CalOPPA guide, published in December 2024, and Cookiebot’s CCPA privacy policy guide. Thresholds and rules can change, so check the source before you rely on them.
Why does your website need a privacy policy?
A privacy policy is a public statement of what personal information your business collects and what it does with it. The California Attorney General says most businesses, both brick-and-mortar and online, are required to provide this information, and that it goes on the website homepage or, for an app, on its download or landing page (California Attorney General).
For websites, the law that set this in motion is CalOPPA. Usercentrics describes it as the first US law to require privacy policies on websites, and it took effect on July 1, 2004 (Usercentrics).
CalOPPA is not limited to businesses based in California. It applies to operators located anywhere in the world if they collect personally identifiable information (PII) from California residents, and it covers sites, apps and online services run for commercial purposes.
The same guide says third parties that only operate, host or manage a site on the owner’s behalf are not held responsible for CalOPPA compliance. The operator, meaning the owner, carries the duty.
What a privacy policy should cover
The California Attorney General’s guidance says a policy should answer a set of basic questions. Treat them as the backbone of your own document.
- What is collected: the categories of personal information, such as name, email address, IP address or advertising ID.
- How it is collected: the categories of sources, for example information you provide, data a device generates automatically, or data bought from another business.
- Why it is collected: the specific purpose for each kind of data.
- How it is used: only to complete the transaction, or for extra uses such as selling it or sharing it for targeted ads.
- Who has access: the categories of third parties to whom information was disclosed, sold or shared.
- What choices people have: an easy way to opt out, such as a “Do Not Sell or Share My Personal Information” or “Your Privacy Choices” link, a toll-free number or an email address.
- How people can review or correct their data: where California law gives these rights, an explanation of how to ask to know, delete or correct.
- How it is protected: a general description of the security measures.
Specific beats vague. The Attorney General’s page notes that a name, address and card number may be needed to ship a purchase, while household income and hobbies are not, so any extra data you ask for needs a clearly stated purpose.

What counts as personal information is broad. CalOPPA’s own list of PII includes an e-mail address, a telephone number and a social security number, plus any other identifier that permits contacting a specific person (Termly).
CalOPPA items and Do Not Track
On top of the basic questions, Usercentrics lists what CalOPPA says an operator’s policy must contain (Usercentrics).
- Information collected: the types of PII collected and any third parties it may be shared with.
- Review process: if consumers can review and request changes to their PII, how that works.
- Notification of changes: how you will tell users about significant changes to the policy.
- Effective date: when the policy goes into effect.
- Do Not Track response: how you handle “Do Not Track” browser signals.
- Third-party collection: whether third parties can collect PII about users’ online activities on your site or service.
The Do Not Track rule trips people up. Usercentrics says CalOPPA was amended in 2013 to address online tracking (Usercentrics). Even so, Termly explains that it does not require you to honor Do Not Track requests, only to say clearly whether you do or do not (Termly).
If you collect data about visitors’ activity across different sites, Usercentrics says you can meet the requirement by linking to a page that explains how you handle those requests. Publishing a “last updated” date is not required by CalOPPA, but it is advisable.
When CCPA and other laws add more
CalOPPA is only the baseline. The CCPA adds duties for larger or data-heavy businesses, and Cookiebot says a for-profit business that does business in California must comply if it meets any one of these:
- gross annual revenue of over USD 26,625,000;
- buying, selling or sharing the personal information of 100,000 or more California residents or households;
- deriving 50 percent or more of annual revenue from selling California residents’ personal information.
Those figures are as stated in Cookiebot’s guide, so confirm the latest thresholds before deciding. Covered businesses must tell consumers what data is collected, how, for what purposes and who may have access, and explain consumer rights and how to use them.
Those rights include the right to know, delete, correct, opt out and limit the use of sensitive information, plus protection from discrimination. For more on how this plays out for smaller firms, see our guide to ccpa compliance for small business.
Termly’s privacy policy checklist, updated July 15, 2026, maps each clause to the laws that require it and adds extras beyond California (Termly checklist). Examples include:
- stating the legal basis for collecting data where the GDPR applies;
- saying whether you plan to transfer data internationally;
- a “Limit the Use of my Sensitive Personal Information” link under the CCPA/CPRA;
- a working method for users to follow through on their rights.
Where to post it and how often to update it
Placement matters as much as content. Termly says a CalOPPA-compliant policy must be easy to find and read, and Usercentrics says operators must conspicuously post it so that it is easy for visitors to see.
A policy also goes stale. The Attorney General’s guidance says it should be updated at least once a year, and Termly’s checklist suggests a “last updated” date and version number near the top, plus links to related documents such as your terms and conditions or cookie policy.
A practical routine looks like this:
- List every form, analytics tool, ad tool and payment screen on your site.
- Compare that list with what the policy says you collect, share and sell.
- Fix any mismatch, then update the effective or last-updated date.
- Check that the link to the policy is still visible on your homepage.
A policy describes how you handle data day to day. What to do when data is lost or stolen is a separate duty, covered in data breach notification requirements.
This page is general, independent education and not legal advice. Which rules bind your business depends on your visitors, your size and your data practices, so a qualified lawyer can confirm your position.
Frequently asked questions
Does a small website need a privacy policy?
Show answer
If you run a website for commercial purposes and collect PII from California residents, CalOPPA can apply wherever you are based, according to Usercentrics. The CCPA has separate revenue and data-volume thresholds, so a small site may fall under one law and not the other.
Do I have to honor Do Not Track requests?
Show answer
No. According to Termly, CalOPPA requires you to disclose whether you honor them, not to honor them.
Does a policy need an effective date?
Show answer
Yes. Usercentrics says the operator must state when the policy goes into effect, and it advises publishing the last-updated date too.
How often should I review my privacy policy?
Show answer
The California Attorney General’s guidance says it should be updated at least once a year. Update it sooner if you add a new tool or start sharing data in a new way.



