On this page

The request type changes the verification question

The California Consumer Privacy Act (CCPA) rules require reasonable documented identity verification for requests to know, correct or delete covered consumer information. The California Privacy Protection Agency (CPPA) regulations prohibit requiring identity verification for sale/sharing opt-outs or sensitive-information limit requests; necessary fulfilment information must not become a burdensome substitute.

These rules concern actual covered California businesses and consumer information. Establish coverage, exceptions and any authorised-agent arrangement before treating this article as your complete process. A generic “privacy request” queue should not force all request types through one identity-document demand.

Sources: California Privacy Protection Agency: Selected source provisions read across the data-owner guides: Sections 7050(a)–(f) and 7051(a)–(c), printed pages58–62; allowed internal improvement, other-client boundary, specific contracts and oversight | Sections 7012(g),7050(d)–(g),7051 and7053; multiple collection businesses and distinct recipient contracts | Sections 7002(a)–(f) and7012(a)–(f); necessity, reasonable expectations, new purposes and notice content/placement | Section 7022(d)–(f); request-specific backup delay and retained-exception limits, used only to distinguish that mechanism | Sections 7060(a)–(h),7061(a)–(b),7062 and7063; verification principles, account/non-account and authorised-agent distinctions | Sections 7022(a)–(h),7050(c),7051(a)(8)–(9),(b); deletion, downstream notices, backups, exceptions, response and contract support | Sections 7023(a)–(k),7060(h); full correction provision, persistent accuracy, source notification, alternative deletion and disputed-field verification | Section 7024(a)–(l), full request-to-know provision including restricted identifiers, delivery, period, vendor assistance and categories | Sections 7025(a)–(f),7026 and7060(b); qualifying signals, browser/profile scope, conflicting settings/incentives and verification prohibition | Section 7027(a)–(m), full sensitive-information limit provision including methods, 15-business-day fulfilment, downstream instructions and permitted purposes | Sections 7050(a)(2),(c)–(f),7051(a)–(c); permitted subcontracting and required downstream terms California Legislature; California Privacy Protection Agency official consolidation: Selected source provisions read across the data-owner guides: Sections 1798.140(d),(i),(j),(ag) and1798.145 selected scope/role/exemption provisions | Sections 1798.140(d),(i),(j),(ag),1798.100(d) and1798.145 selected business/consumer/role and exemption provisions | Sections 1798.100(a)–(c),1798.140(d),(i) and1798.145 selected scope/exemption provisions | Section 1798.100(a)(3),(c) and1798.140(d),(i); retention notice/necessity and coverage | Sections 1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.105,1798.140(d),(i) and1798.145 selected coverage/exemption provisions | Sections 1798.106,1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100,1798.110,1798.130(a)(2),1798.140(d),(i); access and portable/readily usable format provisions within coverage | Sections 1798.120,1798.140(d),(i),(ad),(ah); sale/sharing and coverage definitions | Sections 1798.121,1798.140(ae),(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100(d),1798.140(d),(i),(j),(ag) and1798.145 selected coverage/role/exemption provisions

Start with existing evidence

Section 7060 directs the business to match identifying information against information already maintained before requesting more, or use a compliant verification service. It considers data sensitivity and value, harm from a wrong response, likely fraud, robustness of evidence, interaction method and available technology. For an existing password-protected account, section 7061 permits its authentication practices under the stated conditions and requires re-authentication—verifying the signed-in person again—before the data action.

The original worksheet below records a decision, not a prescribed technical verification method. A specialist should design the actual method.

Request featureDecision to record
Access to sensitive recordsWhy the evidence and delivery route are appropriate for the disclosure risk.
Correction of a disputed addressOther identity information used; do not verify using the address being disputed.
An existing customer accountHow the approved account verification and required re-authentication are applied.
Sale/sharing opt-outOnly information needed to complete it; no identity-verification condition.

Sources: California Privacy Protection Agency: Selected source provisions read across the data-owner guides: Sections 7050(a)–(f) and 7051(a)–(c), printed pages58–62; allowed internal improvement, other-client boundary, specific contracts and oversight | Sections 7012(g),7050(d)–(g),7051 and7053; multiple collection businesses and distinct recipient contracts | Sections 7002(a)–(f) and7012(a)–(f); necessity, reasonable expectations, new purposes and notice content/placement | Section 7022(d)–(f); request-specific backup delay and retained-exception limits, used only to distinguish that mechanism | Sections 7060(a)–(h),7061(a)–(b),7062 and7063; verification principles, account/non-account and authorised-agent distinctions | Sections 7022(a)–(h),7050(c),7051(a)(8)–(9),(b); deletion, downstream notices, backups, exceptions, response and contract support | Sections 7023(a)–(k),7060(h); full correction provision, persistent accuracy, source notification, alternative deletion and disputed-field verification | Section 7024(a)–(l), full request-to-know provision including restricted identifiers, delivery, period, vendor assistance and categories | Sections 7025(a)–(f),7026 and7060(b); qualifying signals, browser/profile scope, conflicting settings/incentives and verification prohibition | Section 7027(a)–(m), full sensitive-information limit provision including methods, 15-business-day fulfilment, downstream instructions and permitted purposes | Sections 7050(a)(2),(c)–(f),7051(a)–(c); permitted subcontracting and required downstream terms

Give newly collected verification information an end point

If existing information cannot verify the person, any permitted additional collection has restricted uses: verification, security or fraud prevention. The regulations require deletion as soon as practical after processing, subject to their request-record requirement. Keep a decision log without automatically retaining a complete document image.

An unsuccessful verification also needs the applicable response procedure, rather than silently closing the ticket. Assign who decides, who communicates the outcome and who controls any newly collected evidence. This is a business process review; it supplies no identity credentials, document-testing instructions or assurance that a particular requester is genuine.

Sources: California Privacy Protection Agency: Selected source provisions read across the data-owner guides: Sections 7050(a)–(f) and 7051(a)–(c), printed pages58–62; allowed internal improvement, other-client boundary, specific contracts and oversight | Sections 7012(g),7050(d)–(g),7051 and7053; multiple collection businesses and distinct recipient contracts | Sections 7002(a)–(f) and7012(a)–(f); necessity, reasonable expectations, new purposes and notice content/placement | Section 7022(d)–(f); request-specific backup delay and retained-exception limits, used only to distinguish that mechanism | Sections 7060(a)–(h),7061(a)–(b),7062 and7063; verification principles, account/non-account and authorised-agent distinctions | Sections 7022(a)–(h),7050(c),7051(a)(8)–(9),(b); deletion, downstream notices, backups, exceptions, response and contract support | Sections 7023(a)–(k),7060(h); full correction provision, persistent accuracy, source notification, alternative deletion and disputed-field verification | Section 7024(a)–(l), full request-to-know provision including restricted identifiers, delivery, period, vendor assistance and categories | Sections 7025(a)–(f),7026 and7060(b); qualifying signals, browser/profile scope, conflicting settings/incentives and verification prohibition | Section 7027(a)–(m), full sensitive-information limit provision including methods, 15-business-day fulfilment, downstream instructions and permitted purposes | Sections 7050(a)(2),(c)–(f),7051(a)–(c); permitted subcontracting and required downstream terms

Scope

  • Selected CCPA verification rules only; no complete request-response policy, authentication design or finding that a particular identity/request is valid. Actual coverage, request risk and authorised-agent facts require review.

Next step

Use Launch planner to assign a request-verification procedure review and the person responsible for handling exceptions. Keep request evidence in your restricted process, not in ELN.

Sources & review notes

Access dates show when a source was retrieved. Review dates show when its meaning was checked. Editing this guide does not recheck the law.

California Consumer Privacy Act Regulations, effective January 1, 2026

California Privacy Protection Agency

Passage, dates and research notes

regulation · Selected source provisions read across the data-owner guides: Sections 7050(a)–(f) and 7051(a)–(c), printed pages58–62; allowed internal improvement, other-client boundary, specific contracts and oversight | Sections 7012(g),7050(d)–(g),7051 and7053; multiple collection businesses and distinct recipient contracts | Sections 7002(a)–(f) and7012(a)–(f); necessity, reasonable expectations, new purposes and notice content/placement | Section 7022(d)–(f); request-specific backup delay and retained-exception limits, used only to distinguish that mechanism | Sections 7060(a)–(h),7061(a)–(b),7062 and7063; verification principles, account/non-account and authorised-agent distinctions | Sections 7022(a)–(h),7050(c),7051(a)(8)–(9),(b); deletion, downstream notices, backups, exceptions, response and contract support | Sections 7023(a)–(k),7060(h); full correction provision, persistent accuracy, source notification, alternative deletion and disputed-field verification | Section 7024(a)–(l), full request-to-know provision including restricted identifiers, delivery, period, vendor assistance and categories | Sections 7025(a)–(f),7026 and7060(b); qualifying signals, browser/profile scope, conflicting settings/incentives and verification prohibition | Section 7027(a)–(m), full sensitive-information limit provision including methods, 15-business-day fulfilment, downstream instructions and permitted purposes | Sections 7050(a)(2),(c)–(f),7051(a)–(c); permitted subcontracting and required downstream terms

Accessed: 2026-11-16T20:11:01.264168+00:00 · Meaning reviewed: 2026-11-16T20:24:54.728906+00:00 · Next review target: 2026-12-16

AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.

California Consumer Privacy Act, effective January 1, 2026

California Legislature; California Privacy Protection Agency official consolidation

Passage, dates and research notes

statute · Selected source provisions read across the data-owner guides: Sections 1798.140(d),(i),(j),(ag) and1798.145 selected scope/role/exemption provisions | Sections 1798.140(d),(i),(j),(ag),1798.100(d) and1798.145 selected business/consumer/role and exemption provisions | Sections 1798.100(a)–(c),1798.140(d),(i) and1798.145 selected scope/exemption provisions | Section 1798.100(a)(3),(c) and1798.140(d),(i); retention notice/necessity and coverage | Sections 1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.105,1798.140(d),(i) and1798.145 selected coverage/exemption provisions | Sections 1798.106,1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100,1798.110,1798.130(a)(2),1798.140(d),(i); access and portable/readily usable format provisions within coverage | Sections 1798.120,1798.140(d),(i),(ad),(ah); sale/sharing and coverage definitions | Sections 1798.121,1798.140(ae),(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100(d),1798.140(d),(i),(j),(ag) and1798.145 selected coverage/role/exemption provisions

Accessed: 2026-11-16T20:11:01.263663+00:00 · Meaning reviewed: 2026-11-16T20:24:54.728906+00:00 · Next review target: 2026-12-16

AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.

Detailed rule records (1)
Verification must fit the request and avoid unnecessary new collection Depends on the facts

Document a reasonable method, use existing information first and apply the restricted-use/deletion terms to new verification data.

When to check: Before releasing, changing or deleting covered records for a requester. Source review: 2026-11-16.

California Consumer Privacy Act Regulations, effective January 1, 2026 California Consumer Privacy Act, effective January 1, 2026
Your learning

Bookmark this guide or mark it as read.

Learning library
Progress privacy

Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.

This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.