Artifact GuideUSContracts Contractors and Service Providers

US CPRA Contracts Contractors and Service Providers

Decide whether each recipient qualifies as a service provider or , then check its written purposes, certification, restricted uses, and subcontractor terms.

Apply the cited California statute and regulations to the actual entity, data flow, system, and recipient role; escalate unresolved legal interpretation.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

A recipient is a service provider or only when both the relationship and the written agreement satisfy the CCPA rules. Classify the actual processing before disclosure. If the recipient does not qualify, analyze it as a third party and determine whether the disclosure is a sale or sharing that requires notice, opt-out handling, and third-party terms.

Section 1

What should teams decide about Contracts Contractors and Service Providers under the US CPRA?

A service provider processes personal information on behalf of a business under a written contract. A is a person to whom the business makes personal information available for a business purpose under a qualifying written contract and certification. Both roles are subject to purpose, use, disclosure, sale, sharing, combination, and direct-business-relationship restrictions.

A person without a contract that complies with regulation section 7051 is not a service provider or for that processing. The same is true when the recipient provides cross-context behavioral advertising services to the business. Contextual advertising based on the page's subject or aggregated demographics can fit a service relationship when the other tests are met; using the business's customer list to identify those people on another platform for cross-context behavioral advertising cannot. If a recipient uses personal information outside the contract, the business and recipient must analyze the consequences under the sale, sharing, and third-party rules.

Subcontracting does not remove the restrictions. A service provider or must bind a subcontractor to a CCPA-compliant agreement and follow the business's contract requirements for engaging it. The original recipient remains responsible for using the data only within permitted purposes.

  • Service provider: record the business, service, specific business purpose, data categories, permitted internal uses, and prohibited uses.
  • : record the business-purpose disclosure, written certification, purpose and use limits, and the same operational controls required for the relationship.
  • Third party: record the limited and specified purpose, sale or sharing status, consumer-choice instructions, same-level-protection terms, and remediation rights.
  • Subcontractor: record authorization or notice, data and purpose, executed downstream terms, request handling, deletion, and monitoring evidence.
Section 2

How should teams make and prove the role decision?

The business owner describes the service and actual uses; privacy or legal classifies the recipient; procurement secures the terms before disclosure; and data, product, and security teams enforce instructions and monitoring. No single contract label should replace that cross-functional decision.

Keep a role memorandum or intake record, executed agreement, data-flow diagram, purpose and category schedule, subcontractor list, opt-out and consumer-request instructions, assessment results, incidents, remediation, and deletion or return evidence. Review the role when the service, purpose, data, advertising activity, or recipient's own use changes.

  • Ask who determines the purposes and means of the recipient's processing and whether the recipient uses the information for its own commercial purposes.
  • Compare every actual use with the specific business purpose in the signed agreement.
  • Check whether the recipient combines the information with data from other businesses or its own consumer interactions and whether a regulatory exception applies.
  • Document how deletion, correction, opt-out, access, security, and subcontractor instructions reach the systems that hold the information.
Section 3

What edge cases should teams check before relying on the decision?

A recipient can have different roles for different processing. Classify each data flow and purpose instead of assigning one permanent label to the company. A compliant service-provider relationship for hosting does not automatically cover the recipient's advertising or product-development uses.

Internal use to improve the quality of services is limited by the regulations and does not permit building or modifying household or consumer profiles for another business or cleaning or augmenting data acquired from another source. For example, an email provider may analyze interactions to improve its email service but may not reuse the original customer list to send another business's marketing; a shipping provider may use delivery experience to identify faulty addresses but may not compile client addresses for advertising or sale to data brokers. Security and fraud-prevention uses also remain subject to the stated purpose and legal limits.

Disclosures directed by the consumer or intentional consumer interactions with a third party may fall outside sale or sharing definitions when statutory conditions are met. Record the consumer action and the recipient identity rather than assuming every integration qualifies.

  • Check whether the rule changes because the recipient is a service provider, , third party, subcontractor, advertising partner, or a business using personal information outside the written contract.
  • 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.
Section 4

How should teams operationalize the decision with proportionate controls?

Use a recipient register with one row per purpose and data flow. Record the California role, sale or sharing result, contract section, consumer-choice dependency, systems, subcontractors, retention, request route, assurance evidence, and review trigger.

When the recipient cannot comply, stop the affected disclosure or use, investigate the scope, preserve evidence, remediate the data and contract position, and reassess notices and consumer instructions. The CCPA contract right to remediate must be usable in practice.

  • Before disclosure: complete the role, sale-or-sharing, notice, consumer-choice, and contract reviews.
  • At onboarding: configure data access, permitted purposes, retention, request instructions, subcontractors, and monitoring.
  • During service: compare actual use with the contract and investigate deviations or inability-to-comply notices.
  • At termination: revoke access and retain verified return, deletion, or documented lawful-retention evidence.
Primary sources

References and citations

cppa.ca.gov5 citations
Referenced sections
  • Supports CPRA contracts, contractors, and service-provider guidance with final contract requirements in section 7051.
  • CPPA regulations source for service-provider and contractor status, permitted uses, contract requirements, and subcontractor clauses.
  • Binding CPPA regulations for contract clauses and audit rights, including examples of regular monitoring and testing.
Show 2 more
  • CPPA regulations source for boundary rules when recipients are not service providers or contractors.
  • Operational source for service-provider and contractor contract clauses, subcontractor requirements, and audit evidence.
"Contract Requirements for Service Providers and Contractors"
More quoted passages
"A person who does not have a contract that complies with section 7051"
"regular internal or third-party assessments, audits, or other technical and operational testing"
"may be considered a sale or sharing of personal information"
"shall have a contract with the subcontractor that complies with the CCPA"
nist.gov5 citations
Referenced sections
  • Background source for privacy governance crosswalks; retained only for evidence-organization context, not as the CPRA contract authority.
  • Voluntary, non-binding NIST crosswalk material for organizing privacy-governance evidence; it does not establish CCPA recipient roles or contract duties.
  • NIST privacy framework crosswalk background for organizing privacy governance evidence; it does not supersede CPRA contract clauses.
Show 2 more
  • NIST privacy framework crosswalk background for privacy governance terminology; use CPRA sources for binding contract terms.
  • NIST privacy framework crosswalk background for operational privacy governance evidence; CPRA sources control the contract requirements.
"Organizations should not assume implementation of these Privacy Framework activities or outcomes means that they have met the"
leginfo.legislature.ca.gov4 citations
Referenced sections
  • Supports CPRA contracts, contractors, and service-provider guidance by setting statutory agreement terms for disclosures, sales, and sharing.
  • California statutory source for contracts with third parties, service providers, and contractors when personal information is sold, shared, or disclosed for a business purpose.
  • California statutory source for same-level-protection, monitoring, notification, and remediation clauses.
Show 1 more
  • Operational source for mapping service-provider and contractor contracts to statutory purposes, monitoring rights, notice, and remediation.
"shall enter into an agreement with the third party, service provider, or contractor"
More quoted passages
"provide the same level of privacy protection as is required by this title"
"take reasonable and appropriate steps to stop and remediate unauthorized use"
cppa.ca.gov3 citations
Referenced sections
  • Binding current regulations used to verify service-provider and contractor contract text.
  • Binding current regulations used to verify service-provider and contractor contract requirements.
  • Binding current regulations on service-provider, contractor, and third-party boundaries.
"Contract Requirements for Service Providers and Contractors"
More quoted passages
"Contract Requirements for Third Parties"
leginfo.legislature.ca.gov
Referenced sections
  • Supports CPRA contractor and service-provider role analysis by defining permitted processing and use restrictions.
"A person who processes personal information on behalf of a business"
Show all related guides (39)

California CPRA Risk Assessments, Cybersecurity Audits, and ADMT Guide

Apply the separate California trigger tests, duties, phase-in dates, evidence, and consumer rights for risk assessments, cybersecurity audits, and ADMT.

California Data Broker Deletion Workflow Guide

California Delete Act and CPRA-adjacent guidance for data broker deletion workflows, with practical decisions, evidence, edge cases, and official citations.

California Data Broker Registry and DROP Guide

California Delete Act guide to data-broker scope, annual registration, DROP processing from August 1, 2026, deletion, opt-out fallback, metrics, and audits.

CCPA vs CPRA: What Changed in California Privacy Law

Compare the original CCPA with the CPRA amendments, including scope thresholds, new rights, contracts, retention, enforcement, and implementation steps.

CPPA Regulations Tracker | CCPA and CPRA

Track the in-force 2023 and 2026 CCPA regulations, their legal status, affected processing, and phased risk, audit, and ADMT deadlines.

CPRA vs Colorado Privacy Act: Practical Comparison

Compare California and Colorado privacy law on scope, consumer rights, opt-outs, sensitive data, contracts, assessments, and enforcement.

CPRA vs Virginia VCDPA: Practical Comparison

Compare California and Virginia privacy law on scope, rights, sale, advertising, sensitive data, contracts, assessments, and enforcement.

US CPRA Compliance Guide

Build a CCPA/CPRA compliance program for scope, notices, consumer rights, opt-outs, vendor contracts, retention, security, and phased 2026 duties.

US CPRA Consumer Rights Workflow Guide

Run California CCPA and CPRA requests to know, delete, correct, opt out, limit, and access or opt out of covered ADMT, with deadlines, verification, exceptions, and evidence.

US CPRA Contract Terms Guide

Required CCPA/CPRA contract terms for service providers, contractors, and third parties, with role tests, clause checks, and evidence.

US CPRA Correction Rights Guide

Handle CCPA correction requests: verification, accuracy review, documentation, system and vendor updates, response timing, denials, and records.

US CPRA Cyber Audit Readiness Workflow Guide

Prepare a California cybersecurity audit: calculate section 7120 scope, set the phased audit period, appoint an independent auditor, collect evidence, and submit certification.

US CPRA DSAR and Correction Workflow Guide

US CPRA guidance for DSAR and Correction Workflow, with practical decisions, evidence, edge cases, and external source citations.

US CPRA GPC Handling Guide

How businesses subject to the CCPA must detect, apply, test, and document Global Privacy Control opt-out signals.

US CPRA GPC Handling Workflow Guide

A California GPC workflow for signal detection, browser and profile scope, conflicts, downstream suppression, 15-business-day completion, and test evidence.

US CPRA Retention Guide

How to set, disclose, implement, and review personal-information retention periods under the California CCPA and CPRA.

US CPRA Risk Assessment Intake Workflow Guide

Screen the six CPPA risk-assessment triggers, record exceptions and evidence, hold covered launches for approval, and track review and submission dates.

US CPRA Risk Assessment Template Guide

A California risk-assessment template covering section 7150 triggers, required report fields, contributors, approval, three-year review, material changes, retention, and submission.

US CPRA Risk Assessments and Cybersecurity Audits Guide

Apply the separate CPPA trigger tests for processing-level risk assessments and entity-level annual cybersecurity audits, with phase-in dates and evidence.

US CPRA Sensitive Personal Information Guide

Classify California sensitive personal information, distinguish category status from the right to limit, and apply notices, assessments, controls, and deadlines.

US CPRA Sensitive Personal Information Limits Guide

Decide when California's right to limit applies, map uses to section 7027(m), implement the 15-business-day restriction, and preserve evidence.

US CPRA Sharing and Cross-Context Behavioral Advertising Guide

How to classify advertising data flows as sharing for cross-context behavioral advertising under the California CCPA and CPRA.

California Delete Act data broker registry and DROP guide

California Delete Act guidance for the data broker registry and Delete Request and Opt-Out Platform (DROP), with owners, evidence, and official sources.

CPRA enforcement advisories: CPPA investigations, fines, and risk mitigation

US CPRA guidance for Enforcement Advisories, with practical decisions, evidence, edge cases, and external source citations.

CPRA Global Privacy Control (GPC): opt-out requirements and enforcement FAQ

US CPRA guidance for GPC, with practical decisions, evidence, edge cases, and external source citations.

What counts as sharing under the California CPRA?

How to identify sharing for cross-context behavioral advertising and implement California notice, opt-out, preference-signal, contract, and recordkeeping duties.

What should teams do about ADMT under the US CPRA?

Decide whether California's ADMT rules cover an automated decision, then apply the 2027 notice, access, opt-out, appeal, and evidence requirements.

What should teams do about Contract Terms under the US CPRA?

Classify California data recipients and check the required service-provider, contractor, third-party, subcontractor, monitoring, and remediation terms.

What should teams do about Correction Rights under the US CPRA?

Handle California correction requests with proportionate verification, 10-business-day confirmation, 45-calendar-day response, accuracy review, and downstream corrections.

What should teams do about Cybersecurity Audits under the US CPRA?

US CPRA guidance for Cybersecurity Audits, with practical decisions, evidence, edge cases, and external source citations.

What should teams do about retention under the California CPRA?

California CPRA guidance for retention, including data minimization, privacy policy disclosures, evidence records, and official source citations.

What should teams do about Sensitive Personal Information Limits under the US CPRA?

US CPRA guidance for Sensitive Personal Information Limits, with practical decisions, evidence, edge cases, and external source citations.

When is a CPRA risk assessment required?

When California businesses must conduct CPRA risk assessments, what each report must contain, and the review, retention, and filing deadlines.