Artifact GuideUSNotice at collection

US CCPA Notice at collection

Notice at collection decisions under the US CCPA should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.

This guide converts official requirements into scope, evidence, ownership, and review decisions for practical implementation, supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation.

Back to main artifact Review sources

Author

Sorena AI

Published

May 9, 2026

Updated

May 9, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published May 9, 2026

Updated May 9, 2026

Overview

A Notice at Collection must tell consumers, at or before collection, what categories of personal information the business will collect, what purposes it will use them for, whether the information is sold or shared, how long it will be retained, and where the privacy policy and opt-out notice can be found. This page maps those requirements to trigger conditions, accountable owners, required deadlines, evidence records, and review paths that product, legal, privacy, security, and compliance teams can apply.

Section 1

What should teams decide about Notice at collection under the US CCPA?

Start by deciding whether the business is collecting personal information from consumers and must give the Notice at Collection at or before the point of collection. The notice must identify the categories of personal information to be collected, the purposes for which the information is collected and used, whether each category is sold or shared, the retention period or retention criteria, and the link to the privacy policy and, if applicable, the opt-out notice.

If the business collects online, the notice can be provided through a direct link to the specific section of the privacy policy. If it collects offline, the notice can be given on paper, by signage that points to the online notice, or orally when collection happens by phone or in person.

Define the exact Notice at Collection trigger and the business process it affects.
Record which role, product, system, customer group, or data flow is in scope.
Attach the source-linked rule, the owner, and the evidence field before approving the control.
Escalate uncertainty when the facts depend on thresholds, exemptions, cross-border activity, vulnerable users, or enforcement-sensitive wording.

Sources for this answer

California CCPA statute and regulations effective January 1, 2026

Official CPPA text for the notice-at-collection duty, including timing at or before collection and required disclosure categories.

California Consumer Privacy Act Regulations (March 2023)

CPPA regulations page used to confirm the approved CCPA regulations and link implementation teams to the official rule text.

Section 2

Who should own Notice at collection, and what evidence should prove the decision?

Ownership should sit with the team that can change notices, request intake, ad-tech settings, vendor contracts, data retention, or consumer-facing controls, with privacy/legal review for ambiguous cases.

Evidence should show threshold calculations, notice-at-collection placement, privacy-policy disclosures, rights request logs, opt-out/GPC handling, vendor restrictions, and enforcement-response readiness.

Name one accountable owner and one reviewer for the Notice at collection workflow.
Keep source screenshots or source links, decision notes, implementation tickets, and approval records together.
Use dated evidence for deadlines, notices, risk assessments, contracts, user journeys, and regulator-facing records.
Review the evidence after product changes, new markets, new vendors, enforcement updates, or material changes in the source text.

Sources for this answer

California CCPA statute and regulations effective January 1, 2026

Official CPPA text for the notice-at-collection duty, including timing at or before collection and required disclosure categories.

California Consumer Privacy Act Regulations (March 2023)

CPPA regulations page used to confirm the approved CCPA regulations and link implementation teams to the official rule text.

CPPA enforcement advisory on dark patterns

CPPA advisory used for notice and choice design quality, especially clear language and symmetry in consumer controls.

Section 3

Which edge cases should teams check before relying on a Notice at collection decision?

Most CCPA mistakes happen at the boundary between a business, service provider, contractor and third party, or between selling, sharing, financial incentives, minors, GPC, and data-broker obligations.

Apply this section before launching a collection point, ad-tech flow, rights workflow, vendor onboarding, financial incentive, minor-focused journey, or data-broker process.

Check whether the rule changes for minors, consumers, business users, public-sector bodies, regulated sectors, high-risk services, or cross-border transfers.
Separate binding law, regulator guidance, consultation material, standards, and enforcement commentary in the evidence record.
Do not rely on a previous answer if the data categories, user interface, vendor role, or contractual flow changed.
Track unresolved assumptions in an open-questions section and route legal interpretation points for review.

Sources for this answer

California CCPA statute and regulations effective January 1, 2026

Official CPPA text for the notice-at-collection duty, including timing at or before collection and required disclosure categories.

California Consumer Privacy Act Regulations (March 2023)

CPPA regulations page used to confirm the approved CCPA regulations and link implementation teams to the official rule text.

CPPA enforcement advisory on dark patterns

CPPA advisory used for notice and choice design quality, especially clear language and symmetry in consumer controls.

Section 4

How should teams operationalize Notice at collection with proportionate controls?

Use a CCPA workflow that captures threshold status, data category, collection point, consumer right, opt-out or GPC trigger, vendor role, evidence, owner, and review date.

The output should be a threshold note, notice update, DSAR decision, opt-out/GPC record, vendor clause map, dark-pattern review, or enforcement evidence pack.

Create a short intake question that identifies the Notice at collection scenario.
Map the answer to a required action, evidence field, owner, reviewer, and review date.
Link related artifact pages with descriptive anchors so users can move from scope to deadlines, controls, penalties, and templates.
Update the workflow when official source material changes or when internal evidence shows recurring exceptions.

Sources for this answer

California CCPA statute and regulations effective January 1, 2026

Official CPPA text for the notice-at-collection duty, including timing at or before collection and required disclosure categories.

California Consumer Privacy Act Regulations (March 2023)

CPPA regulations page used to confirm the approved CCPA regulations and link implementation teams to the official rule text.

Recommended next step