Guide for US companies
CCPA website requirements: what your site needs if California's privacy law applies
CCPA website requirements, for a business the law covers, come down to five things on the site: a privacy policy with the contents the regulations list, notices at the point of collection, a 'Do Not Sell or Share My Personal Information' link or an allowed alternative if you sell or share data, support for opt-out preference signals such as Global Privacy Control, and working methods for consumer requests.
- Applies if
- Any one of three thresholds is met
- Opt-out signals
- Global Privacy Control must be honoured
- Cookie banner alone
- Not an acceptable opt-out method
- Sign-off
- Your counsel
Updated · By the Codebrix team
The privacy policy: required contents
Section 7011 of the CCPA regulations sets out what the privacy policy must contain and where it must appear. In summary, the policy must:
- Be reachable from a conspicuous link using the word 'privacy' on the homepage; a mobile app should also link to it from its settings menu.
- Be available in a format the consumer can print.
- List the categories of personal information collected in the last 12 months, the categories of sources and the purposes for collecting it.
- List the categories sold or shared in the last 12 months and the categories of third parties involved, or state that none were sold or shared.
- State whether the business has actual knowledge that it sells or shares personal information of consumers under 16.
- List the categories disclosed to service providers or contractors for a business purpose.
- State whether sensitive personal information is used or disclosed beyond the purposes the regulations allow.
- Explain each right, including to know, delete, correct, opt out of sale or sharing and, where relevant, limit the use of sensitive information, plus the right not to be retaliated against for using them.
- Explain how to submit requests and describe how they are verified.
- Show the date it was last updated.
Write it from a real data map, not a template: list every form, script, pixel, analytics tool and integration on the site and what each collects, so counsel's policy describes what the site actually does.
The opt-out link: three ways to meet the rule
A business that sells or shares personal information must give consumers a way to opt out from the site. The regulations allow three set-ups:
| Option | What appears on the site | Notes |
|---|---|---|
| Separate links | 'Do Not Sell or Share My Personal Information' and, if you use sensitive personal information beyond the permitted purposes, 'Limit the Use of My Sensitive Personal Information' | Conspicuous, in the header or footer of the homepage |
| One alternative link | 'Your Privacy Choices' or 'Your California Privacy Choices', with the opt-out icon beside it | Leads to a page explaining both rights, with a way to exercise them |
| Frictionless signal processing | No link, if the business processes opt-out preference signals in the frictionless manner section 7025 describes | The notice of the right to opt out must still appear in the privacy policy |
One rule catches many marketing teams out. Section 7026 states that a cookie banner or cookie controls are not by themselves an acceptable method for opting out of sale or sharing, because cookies concern the collection of personal information, not its sale or sharing. A consent banner can sit alongside the opt-out; it cannot replace it.
The opt-out also has to work technically: when a visitor opts out, the tags that sell or share their data must stop for that browser, which means wiring the opt-out state into your tag manager and testing it.
Global Privacy Control and other opt-out preference signals
An opt-out preference signal lets a person opt out of sale and sharing with every site they visit, set once in the browser. The best known is Global Privacy Control (GPC). The California Attorney General says GPC must be honoured by covered businesses as a valid consumer request, and the CPPA's FAQ says businesses must honour opt-out preference signals that meet certain requirements.
Section 7025 of the regulations sets out what honouring the signal means for a business that sells or shares:
- Treat the signal as a valid opt-out for that browser or device and any profile linked to it, including pseudonymous profiles, and for the consumer if known.
- Do not require more information than the signal itself. You may offer an optional way to give more, but must still process the signal if the person ignores it.
- If the signal conflicts with a setting the person chose earlier on your site, process the signal; you may then tell them about the conflict and ask for consent.
- Where the consumer is known, do not treat a later absence of the signal as consent to opt back in.
- Display on the site whether the signal has been processed as a valid opt-out.
How it is implemented
The GPC specification defines an HTTP request header, Sec-GPC, with the value 1, and a JavaScript property, navigator.globalPrivacyControl. A working set-up reads the header on the server or the property in the browser, sets the visitor's opt-out state before any advertising tag loads, and shows the visitor that the signal was honoured. Test it by switching GPC on in a browser and checking the network panel to confirm the relevant tags do not fire.
Consumer request methods and response times
Consumers can ask a business to tell them what it holds, delete it and correct it. Section 7020 sets the methods for those requests:
- A business that operates exclusively online and has a direct relationship with the consumer need only provide an email address.
- Any other covered business must offer two or more methods, one of which must be a toll-free telephone number; if it has a website, one method must be through the website, such as a webform.
- Opt-outs have their own rule: a business collecting personal information online must at minimum accept opt-out preference signals plus one of the opt-out link, the alternative link, or the privacy policy where signals are processed frictionlessly.
| Step | Deadline |
|---|---|
| Confirm receipt of a request to know, delete or correct | Within 10 business days |
| Respond to a request to know, delete or correct | Within 45 calendar days, extendable by a further 45 days with notice to the consumer |
| Act on an opt-out of sale or sharing | As soon as feasibly possible, and no later than 15 business days |
| Ask an opted-out consumer to opt back in | Wait at least 12 months |
Build the plumbing, not just the form: identity verification for requests to know, delete and correct (not required for opt-outs, per the Attorney General's FAQ), a dated log, and a route to every system holding the data. Consumers cannot be required to create an account just to make a request.
Service providers, contractors and your vendors
Every vendor that handles personal information for you, from hosting and email to analytics and your development agency, needs a contract with the terms section 7051 lists if it is to count as a service provider or contractor. Those terms include:
- A ban on selling or sharing the personal information.
- A specific description of the business purpose, not a general reference to the whole contract.
- Limits on retaining, using or disclosing the data outside that purpose and outside the direct relationship with you.
- A duty to comply with the CCPA and provide the same level of privacy protection the law requires of you.
- Your right to take reasonable steps to check how the data is used, and to stop and remediate unauthorised use.
- A duty to tell you if the vendor can no longer meet its obligations, and to help you handle consumer requests.
The stakes are concrete. Section 7050 says a person without a compliant contract is not a service provider or contractor, so disclosing data to them may be a sale or sharing that triggers the opt-out right. It also says a service provider cannot contract to provide cross-context behavioral advertising; a vendor doing that is a third party. Our software development contract checklist covers the rest of a development contract.
Sensitive personal information
The regulations define sensitive personal information to include, among other things:
- Social Security, driver's licence, state ID card or passport numbers.
- Account log-in, financial account or card numbers together with the code or password that gives access.
- Precise geolocation.
- Racial or ethnic origin, citizenship or immigration status, religious or philosophical beliefs, or union membership.
- The contents of mail, email and text messages, unless the business is the intended recipient.
- Genetic data and neural data.
- Biometric information processed to identify a person, and information about health, sex life or sexual orientation.
If your site collects any of this, ask counsel whether your use goes beyond the purposes the regulations allow. If it does, consumers have a right to limit it, and you need the 'Limit the Use of My Sensitive Personal Information' link or the alternative link. Either way, collect less. Health data may also bring HIPAA into play; see HIPAA app development.
Other states, and the full checklist
California is not alone. Several states now have comprehensive privacy laws with their own thresholds and rules. Two examples from their attorneys general: Colorado has required covered businesses to honour Global Privacy Control as a universal opt-out since 1 July 2024, and Connecticut has required controllers to honour opt-out preference signals since 1 January 2025. Ask counsel which states apply to you; building GPC support once usually serves several of them.
California's rules also keep moving: the CPPA says its regulations on risk assessments, cybersecurity audits and automated decision-making technology took effect on 1 January 2026, with some deadlines phased into 2027 and 2028.
| Item | Where it lives | Who usually owns it |
|---|---|---|
| Coverage, exemptions and whether you sell or share | Internal memo | Counsel |
| Inventory of forms, tags, pixels and integrations | Shared document | Developers with marketing |
| Privacy policy with section 7011 contents and last-updated date | Homepage link containing the word 'privacy' | Counsel drafts, developers publish |
| Notice at collection on every form | At or before the point of collection | Counsel and developers |
| Opt-out link, alternative link or frictionless signal processing | Homepage header or footer | Developers |
| GPC detected, honoured and status shown to the visitor | Site code and tag manager | Developers |
| Opt-out actually stops selling or sharing tags | Tag manager and ad platforms | Developers and marketing |
| Request methods: email, or toll-free number plus webform | Privacy and contact pages | Operations |
| Identity verification and a dated request log | Back office or CRM | Operations with developers |
| Service-provider terms in every vendor contract | Contracts | Counsel |
| Sensitive information reviewed and minimised | Forms and database | Counsel and developers |
We build the website side of this list: the links, GPC handling, tag gating, request forms and logs, alongside accessibility work such as WCAG-based ADA website fixes. We do not certify compliance; your counsel decides what the law requires and signs off. To scope the work, ask for a fixed quote.
Frequently asked questions
Does the CCPA apply to a small business website?
Only if the business meets a threshold. Per the CPPA's guide, a for-profit business doing business in California is covered if it had gross annual revenue over $26,625,000 in the previous calendar year, buys, sells or shares personal information of 100,000 or more consumers or households, or earns half or more of its revenue from selling or sharing it. Figures as of November 2026.
Is a cookie banner enough for the CCPA?
No. Section 7026 of the CCPA regulations states that a cookie banner or cookie controls are not by themselves an acceptable method for opting out of sale or sharing, because cookies concern collection. If you sell or share personal information, you need a real opt-out route, and it must honour opt-out preference signals such as Global Privacy Control.
Do I have to honour Global Privacy Control?
If the CCPA applies and you sell or share personal information, yes. The California Attorney General says GPC must be honoured by covered businesses as a valid request to opt out, and section 7025 of the regulations explains how. Colorado and Connecticut also require businesses within their laws to honour such signals. Counsel should confirm which laws apply to you.
What must a CCPA privacy policy include?
Under section 7011: the categories of personal information collected in the last 12 months, their sources and purposes, what was sold, shared or disclosed and to whom, whether you knowingly sell or share data of under-16s, how sensitive information is used, each consumer right and how to exercise it, how requests are verified, and the date it was last updated.
Do I need a toll-free number for CCPA requests?
Not if your business operates exclusively online and has a direct relationship with the consumers whose data it collects; an email address is then enough for requests to know, delete and correct. Other covered businesses must offer two or more methods, including a toll-free number and, if they have a website, a web-based method such as a form.
What does 'Your Privacy Choices' mean on a website?
It is the alternative opt-out link the CCPA regulations allow instead of separate 'Do Not Sell or Share' and 'Limit the Use of My Sensitive Personal Information' links. It must be titled 'Your Privacy Choices' or 'Your California Privacy Choices', show the opt-out icon, sit in the header or footer, and lead to a page where both rights can be exercised.
Sources
- California Privacy Protection Agency: Does my business need to comply with the CCPA?
- California Privacy Protection Agency: FAQ
- California Privacy Protection Agency: CCPA regulations text (effective 1 January 2026)
- California Attorney General: California Consumer Privacy Act (CCPA)
- Global Privacy Control specification
- Colorado Attorney General: Universal opt-out and the Colorado Privacy Act
- Connecticut Attorney General: The Connecticut Data Privacy Act
Related
United States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read moreAccessibility
ADA website accessibility services: WCAG 2.2 AA audits, fixes and builds
ADA website accessibility services from an India-based team: WCAG 2.2 AA audits, fixes in your own code, and builds tested with real screen readers.
Read moreGuide for US companies
A software development contract checklist for US companies hiring an outside team
A software development contract checklist for US companies: IP assignment, escrow, acceptance, warranty, liability, disputes, data terms and handover.
Read moreMedical practices, US
Medical practice website design for US practices that keeps PHI out of the wrong places
Medical practice website design for US clinics: booking and patient forms planned around PHI, no ad pixels on PHI pages, honest reviews and WCAG 2.2 AA.
Read moreWeb development
A web development company in India that builds on Next.js
Web development company in India building fast Next.js marketing sites and web apps. Fixed quotes, a demo every week, and you own all of the code.
Read moreTechnical SEO
Technical SEO services that fix what stops search engines reading your site
Technical SEO services that fix crawling, indexing, Core Web Vitals, structured data and migrations in your code, with evidence for every fix.
Read more