On this page

Establish which California role applies

The California Consumer Privacy Act (CCPA) has defined business, consumer, service-provider and contractor roles. A consumer is a California resident; the business definition includes threshold and certain affiliation conditions. A small first-year operation should establish its actual status, relevant information and exemptions rather than assume that every American vendor contract is governed by these provisions.

For a covered arrangement, the California Privacy Protection Agency (CPPA) regulations require the contract to identify specific business purposes and restrict retention, use, disclosure, sale and sharing. Calling a supplier a processor in a purchase order does not establish the CCPA role. Sale and sharing have defined CCPA meanings; they are not limited to an ordinary sale of a customer list.

Sources: 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 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

Separate improving your service from serving someone else

Section 7050 permits certain reasonably necessary and proportionate internal use to improve the quality of services provided to the business. Its stated boundary prevents using that personal information to perform services on another person’s behalf. Other permitted purposes have their own conditions. It is therefore inaccurate to say that every improvement use is prohibited, or that every product-development clause is permitted.

Fictional proposal: a scheduling vendor wants customer appointment histories both to improve your booking service and to build a separate lead product. Ask it to explain each use, which records it needs and who benefits. Do not treat one broad “analytics” label as the answer.

Proposed useDecision evidence to request
Improve the booking service supplied to your companyActual internal task, needed fields and why the use remains within the permitted purpose.
Market another client’s service to your customersSeparate recipient, commercial purpose and applicable role/sharing analysis.
Create a new product from identifiable historiesData used, intended customers and specialist assessment of the actual permitted route.

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 management one decision for each purpose

Keep the permission file aligned with the actual service description. Record the company receiving the records, the purpose, any combining with other data, and the contract restriction that supports the proposed treatment. If the provider cannot explain a reuse, narrow the supplied data or hold that use for review before relying on service-provider treatment.

The contract also needs the required rights to check use and stop or remediate unauthorised use. A signed agreement is evidence of the promised restriction; it does not prove the records are actually being used that way.

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 role and purpose provisions only. Actual coverage, proposed secondary use, exceptions and other applicable laws require the business facts; no vendor or data use is approved.

Next step

Use Relationship factsheet to describe what the vendor supplies, what your company supplies and the disputed reuse. Keep the detailed purpose-and-contract register in your restricted company files.

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)
Service-provider treatment requires the actual restricted purpose Depends on the facts

Specific contracted purposes and restrictions apply; section 7050 permits bounded internal improvement, not unrestricted work for another person.

When to check: Before agreeing secondary customer-data use. 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.