California Privacy and Automated Decisionmaking Rules

CCPA Updates, Cybersecurity Audits, Risk Assessments, Automated Decisionmaking Technology (ADMT), and Insurance Regulations

United States • California

RAI-US-NA-DECISIO-2025
Effective: 1 Jan 2026
In Force(In Force)

California Privacy and Automated Decisionmaking Rules is In Force in United States, according to privacy.ca.gov. We have not yet been able to confirm the status.

RegulationData Protection and PrivacyRisk ManagementCybersecurity and Model Security
Export PDF

California updates CCPA rules with cybersecurity audits, risk assessments, automated decisionmaking rights, and insurance clarifications.

Summary

California's regulations update CCPA rules, require risk assessments and annual cybersecurity audits for certain businesses, establish ADMT access and opt-out rights, and clarify insurance-company coverage. They took effect January 1, 2026, with additional compliance time for some requirements.

Full article

Read full text ↗

Overview

The California Privacy Protection Agency's regulation package updates existing California Consumer Privacy Act regulations and introduces requirements addressing risk assessments, cybersecurity audits, and automated decisionmaking technology. It also clarifies when insurance companies must comply with the CCPA. The Agency Board adopted the package on July 24, 2025. The Office of Administrative Law approved the regulations on September 22, 2025, and they were filed with the Secretary of State that day. The regulations became effective January 1, 2026. These milestones are recorded on the official regulation page.

The package is a California agency regulation, not a federal statute or a separate general-purpose artificial intelligence act. Its connection to AI governance arises through businesses' use of automated decisionmaking technology that processes personal information. Its scope is broader than automated decisions alone: it combines privacy-rule amendments, consumer rights, risk assessment obligations, cybersecurity assurance, and insurance-sector coverage clarification. The effective date is distinct from the compliance schedule for some new requirements.

Definitions and Scope

Automated decisionmaking technology, or ADMT, means any technology that processes personal information and uses computation to replace human decisionmaking or substantially replace human decisionmaking. The approved regulations text is the operative source for this definition. The definition connects three elements: technology, processing of personal information, and computational replacement or substantial replacement of human decisionmaking. ADMT is therefore not simply a synonym for every form of AI or every computational tool.

The package implements risk assessments and annual cybersecurity audits for certain businesses. This differentiated scope matters when assessing applicability: the package does not describe these requirements as applying universally to every business. Consumer access and opt-out rights address businesses' use of ADMT within the CCPA framework. The insurance component clarifies when insurance companies must comply with that framework, rather than establishing an independent AI insurance regime.

A practical classification process can inventory relevant systems, identify their personal-information inputs, and describe the role of human decisionmakers. This is a preparation method rather than a separate regulatory requirement. Applicability analysis should distinguish the ADMT definition from the conditions governing particular rights, assessments, and audits; identifying a technology as ADMT does not by itself resolve every compliance question.

Governance and Institutional Framework

The California Privacy Protection Agency is the issuing institution, and its Board adopted the regulations. The Office of Administrative Law subsequently approved the package, after which it was filed with the Secretary of State. Board adoption, administrative approval, filing, and entry into force are distinct procedural milestones. The Agency's official rulemaking record identifies the rulemaking as complete.

The regulatory process included preliminary written comments, pre-rulemaking stakeholder sessions, public hearings, and an opportunity to comment on modified text. The formal record contains proposed regulations and supporting materials, modified text, final approval materials, the approved regulations, a final statement of reasons, responses to comments, and an economic and fiscal impact statement. These materials document the development of the package and the reasons for regulatory choices.

The approved regulations establish the final operative wording. Proposed and modified versions document earlier stages of the process and should not be treated as interchangeable with the approved text. Statements of reasons and responses to comments can assist interpretation while remaining distinct from the provisions that establish obligations. Maintaining this distinction helps organizations avoid implementing superseded draft language.

Principal Regulatory Components

The package has four principal components. First, it updates existing CCPA regulations. Second, it implements requirements for certain businesses to conduct risk assessments and complete annual cybersecurity audits. Third, it implements consumer rights to access and opt out of businesses' use of ADMT. Fourth, it clarifies when insurance companies must comply with the CCPA. Together, these components place the instrument primarily within data protection, risk management, and cybersecurity governance.

ADMT access and opt-out rights bring automated decisionmaking into the consumer privacy framework. They address a business's use of technology that processes personal information and computationally replaces or substantially replaces human decisionmaking. These rights should be treated as the rights established by the package, rather than automatically relabeled as an appeal against an automated decision.

Risk assessments and cybersecurity audits are separate compliance components. An assessment addresses processing-related risk, while the package expressly identifies annual cybersecurity audits as an audit obligation for certain businesses. Their separate treatment means that completing one should not automatically be treated as satisfying the other. Insurance-company coverage is likewise a distinct issue: the clarification concerns CCPA compliance, not the purchase of AI liability insurance, a coverage limit, or a compensation fund.

Implementation and Compliance Timing

Implementation should use the approved regulations as the controlling version. The rulemaking record distinguishes the November 2024 proposal, the May 2025 modifications, and the September 2025 final materials. An implementation plan can identify changes to existing CCPA procedures and separately assess whether relevant processing falls within the risk assessment, cybersecurity audit, and ADMT provisions. Privacy, security, technology, and legal teams can coordinate this analysis; this allocation is an operational recommendation rather than an additional organizational structure imposed by the package.

The official finalization announcement identifies additional time for businesses to comply with cybersecurity audits, risk assessments, and ADMT requirements. January 1, 2026 is therefore the regulations' effective date, not a universal first deadline for every new obligation. An implementation schedule should distinguish entry into force from applicable provision-specific compliance dates and transition rules.

A practical work plan can map each regulatory component to affected systems, existing policies, consumer-facing processes, responsible teams, and implementation milestones. It can also distinguish obligations from voluntary preparation measures. Using a single project plan may improve coordination, but applicability and timing should remain specific to each component rather than being assumed identical across the package.

Monitoring and Evaluation

Annual cybersecurity audits provide a recurring assurance mechanism expressly identified in the package. Risk assessments form a separate obligation for certain businesses. These mechanisms should remain distinct in compliance planning, with each connected to its own applicable provisions. The annual character of the cybersecurity audit requirement is particularly relevant to ongoing planning: it is a recurring obligation, not merely a one-time implementation exercise.

Recommended management practices include documenting applicability decisions, assigning responsibility for audit planning, tracking changes in relevant processing, and reviewing whether consumer-facing ADMT access and opt-out procedures operate as intended. These activities support implementation but should not be confused with independently established requirements concerning a particular security framework, auditor qualification, reporting format, or assurance standard.

Monitoring arrangements can connect privacy and security work without treating assessment and audit outputs as interchangeable. A business can organize records around the processing activity, the relevant regulatory component, the responsible function, and the applicable schedule. For organizations with existing assurance programs, the approved provisions should guide how those programs are adapted to this package rather than assuming that an existing assessment or audit automatically satisfies California requirements.

Rights, Liability, and Insurance Coverage

The consumer-rights component implements access and opt-out rights concerning businesses' use of ADMT. Operationally, these rights belong within the organization's privacy compliance processes, alongside the applicable updates to existing CCPA regulations. Consumer communications and internal procedures should use the terminology and scope of the final provisions rather than importing labels from unrelated automated-decision regimes.

The package operates within the CCPA framework. Compliance analysis should distinguish substantive duties, consumer rights, enforcement routes, and remedies rather than treating them as identical concepts. Access and opt-out rights should not automatically be characterized as a right to appeal an underlying decision, and a regulatory obligation should not automatically be characterized as creating a private lawsuit. Enforcement and legal exposure are separate parts of a legal compliance analysis.

The insurance provisions clarify when insurance companies must comply with the CCPA. This coverage clarification belongs to privacy regulation; it is not a requirement to purchase liability insurance for AI systems or establish a compensation mechanism. Insurance businesses should assess the final coverage clarification together with the package's other applicable privacy requirements, rather than assuming that insurance-sector status alone determines the applicability of every provision.

Relationship to Other Instruments and Cross-Jurisdictional Compliance

The package updates and implements the CCPA regulatory framework rather than replacing the CCPA with a new legislative instrument. Its privacy amendments, assessments, audits, and ADMT rights form part of that framework. The insurance component addresses when insurance companies must comply with the CCPA. The instrument should therefore be understood as an implementing and amending regulation with several connected compliance components.

The rulemaking documents have different functions. The Notice of Proposed Rulemaking records the formal proposal stage, while the Notice of Modifications records changes opened for further comment. The approved text supplies the final obligations. Interpretive documents can explain regulatory choices but should not replace the operative provisions when specifying requirements.

For organizations operating across jurisdictions, a shared inventory of personal-information processing and automated decision systems may support coordinated compliance work. This is a practical management approach, not an international obligation created by the package. Similar subjects in other privacy and AI regimes do not make their requirements interchangeable. California-specific definitions, scope conditions, rights, and schedules should remain distinct, and existing assessments or audits prepared for another regime should be evaluated against the California provisions.

Implementation Timeline

MilestoneDateDetails
Preliminary written-comment invitation2023-02-10The Agency invited preliminary comments on the package's topics.
Preliminary comment period closed2023-03-27The preliminary written-comment period ended.
Los Angeles stakeholder session2024-05-13Pre-rulemaking session on draft ADMT, risk assessment, and cybersecurity audit regulations.
Fresno stakeholder session2024-05-15Additional pre-rulemaking stakeholder session.
Additional stakeholder session2024-05-22A third pre-rulemaking stakeholder session took place.
Formal rulemaking notice2024-11-22Proposed regulations and supporting materials were published.
Comment-period extension notice2025-01-13A notice extended the comment period and added a hearing date.
Initial public hearing2025-01-14The Agency held a public hearing.
Additional public hearing2025-02-19The Agency held an additional public hearing; the record includes a transcript and webcast.
Notice of proposed modifications2025-05-09Modified text was opened for comment.
Modified-text comment period closed2025-06-02The comment period on modified text ended.
Agency Board adoption2025-07-24The Board adopted the regulations.
Approval and filing2025-09-22The Office of Administrative Law approved the regulations, which were filed with the Secretary of State.
Finalization announcement2025-09-23The Agency announced final approval.
Regulations effective2026-01-01The regulations entered into force, with additional compliance time for cybersecurity audits, risk assessments, and ADMT requirements.

Compliance Checklist

The checklist combines the package's principal obligations with practical implementation steps. Applicability and timing should be assessed separately for each component.

CheckAction
Controlling versionUse the approved regulations rather than superseded proposed or modified language.
Business applicabilityAssess the business and relevant processing against the scope of each applicable provision.
Existing CCPA updatesIdentify applicable amendments and update affected privacy compliance procedures.
ADMT classificationEvaluate relevant technology against the definition and applicable scope conditions.
ADMT access rightsImplement applicable consumer access rights concerning the business's use of ADMT.
ADMT opt-out rightsImplement applicable opt-out rights and review their operation under the final provisions.
Risk assessmentsConduct required assessments for covered processing under the applicable requirements and schedule.
Annual cybersecurity auditsComplete annual audits where applicable and plan for recurring compliance.
Insurance-company coverageApply the clarification of when insurance companies must comply with the CCPA.
Transition scheduleDistinguish the effective date from provision-specific compliance dates and additional implementation time.
Management coordinationAs a practical measure, assign responsibilities across privacy, security, technology, and legal functions.
Enforcement reviewEvaluate applicable enforcement routes, remedies, and review procedures as a separate legal compliance task.

Sources and References

© Regulations.AI — created on 7 Nov 2026 using Gemini 3.6 Flash