Privacy

California's Delete Act: The $200/Day Fine Data Brokers Can't Ignore

By LowerPlane Team
March 21, 2026
10 min read
⚖️

California Delete Act — Enforcement Begins January 31, 2026

TL;DR: Quick Takeaways

  • California's Delete Act (SB 362) penalties went live January 31, 2026. Data brokers that fail to honor deletion requests now face $200 per consumer per day — with no cap on the accrual period.
  • A "data broker" under the Act is any business that knowingly collects and sells or shares personal information about consumers with whom it has no direct relationship — far broader than many companies expect.
  • Registration with the California Privacy Protection Agency (CPPA) was required by January 31, 2024. Unregistered brokers face a separate $200/day penalty per day of non-registration.
  • The Delete Act intersects directly with CCPA/CPRA — companies with existing Data Subject Request infrastructure must extend it to cover the CPPA's centralized deletion mechanism.
  • LowerPlane's CCPA and GDPR DSR management modules automate intake, tracking, and fulfillment workflows so compliance teams can honor deletion requests at scale without manual overhead.

On January 31, 2026, California's Delete Act enforcement clock started ticking — and it costs $200 per day for every consumer deletion request left unfulfilled. For the thousands of companies operating as data brokers under California law, the era of treating deletion requests as optional compliance theater is definitively over. The California Privacy Protection Agency has the authority to audit, investigate, and fine without waiting for a consumer complaint to trigger action.

The Delete Act — formally Senate Bill 362, signed into law in October 2023 — represents the most aggressive state-level privacy enforcement mechanism in American history. It created a centralized deletion framework through the CPPA, requiring data brokers to honor deletion requests submitted through a single consumer portal rather than requiring consumers to individually contact hundreds of companies. The operational demand on data brokers is substantial: automated deletion pipelines, verified identity workflows, and audit-ready documentation of every request handled.

This guide covers who qualifies as a data broker under the Act, the registration requirements that were due in 2024, the mechanics of the $200/day fine structure, how the Delete Act interacts with CCPA and CPRA obligations, and the practical compliance steps your organization needs to implement now. We also explain how LowerPlane's DSR management tooling helps privacy teams handle deletion requests at scale across both California and GDPR frameworks simultaneously.

What Is the California Delete Act — And Why Did California Pass It?

California's existing privacy landscape — the California Consumer Privacy Act (CCPA) and its 2023 expansion under the California Privacy Rights Act (CPRA) — already gave consumers broad rights over their personal information, including the right to request deletion from individual businesses. But the CPPA identified a structural gap: when a consumer wanted to exercise their right to deletion against data brokers specifically, they faced a fragmented, burdensome process. A California resident seeking to remove their data from the data broker ecosystem would have to individually contact hundreds of companies, each with their own request portal, verification process, and response timeline.

SB 362 addressed this gap by mandating the CPPA build and operate a centralized "data deletion mechanism" — a single portal through which consumers can submit one deletion request that is then distributed to all registered data brokers simultaneously. Data brokers must honor those requests within 45 days and must delete the consumer's data from their databases as well as from the databases of service providers processing data on their behalf.

The law also introduced a comprehensive registration regime. Every data broker operating in California must register annually with the CPPA, pay a registration fee, and disclose specific information about their data practices — including the categories of personal information they collect, the purposes for which it is used, the length of time it is retained, and whether the broker collects data on minors. This registry is public, creating both transparency for consumers and an audit baseline for regulators.

Delete Act Key Dates Timeline

  • Oct 2023Governor Newsom signs SB 362 into law. Initial registration requirements take effect.
  • Jan 2024First registration deadline. Data brokers operating in California must register with CPPA and pay the annual fee. $200/day non-registration penalties begin accruing.
  • Jan 2026CPPA deletion portal goes live. Data brokers must begin honoring centralized deletion requests within 45 days. $200/day penalties for unfulfilled requests take effect.
  • OngoingAnnual registration renewal required. CPPA may conduct audits of data broker deletion compliance at any time without a consumer complaint triggering the investigation.

Who Qualifies as a Data Broker Under California Law?

The definition of "data broker" in the Delete Act mirrors the definition in the California Data Broker Registration Act (Civil Code Section 1798.99.80): a business that knowingly collects and sells or shares the personal information of consumers with whom it does not have a direct relationship. That last clause — "with whom it does not have a direct relationship" — is the operative phrase, and it catches far more companies than leadership teams typically anticipate.

Consider the scope: a company that purchases consumer data from a credit bureau and uses it to enrich prospect records for outbound sales is a data broker. A company that aggregates public records — voter registrations, property records, court filings — and licenses that database to insurance underwriters is a data broker. An analytics firm that collects behavioral data from publisher networks and sells audience segments to advertisers is a data broker. In each case, the defining characteristic is the secondary sale or sharing of personal information about individuals who never had a direct commercial relationship with that company.

Business TypeLikely a Data Broker?Key Consideration
People-search / background-check platformsYes — core use caseAggregating public and purchased records about individuals who are not customers
AdTech / audience data platformsYes — if selling segmentsSelling behavioral or demographic segments derived from consumer data
Data enrichment / lead generation SaaSYes — high riskLicensing contact or firmographic data about individuals who are not product users
Credit reporting agenciesYes — with FCRA overlapMust comply with Delete Act in addition to existing FCRA deletion obligations
Marketing analytics platformsPossibly — fact-specificDepends on whether processed data is shared or sold to third parties vs. used solely for contracted services
SaaS companies with direct customer relationshipsLikely notProcessing data of their own users for their own product — but CCPA/CPRA still applies separately
Insurance carriers licensing external risk dataDepends on directionAs a buyer of data broker services, not automatically a broker — but if reselling, yes

The Act carves out certain exemptions. Businesses whose data broker activity is incidental to their primary purpose — for example, a retailer that shares customer data with a contracted fulfillment provider — are not data brokers under this definition. Financial institutions covered by the Gramm-Leach-Bliley Act and covered entities under HIPAA have partial exemptions for data regulated by those federal laws, though not for all data categories they may handle. The CPPA has signaled it will interpret exemptions narrowly, so any company with arguable data broker characteristics should obtain a formal legal opinion before concluding it falls outside the law's scope.

Registration Requirements: What You Had to File — And Still Need to Maintain

The Delete Act's registration requirement was the first enforcement mechanism to take effect, with the initial deadline of January 31, 2024. Data brokers were required to register through the CPPA's online portal and provide a detailed disclosure covering their data practices. The registration is annual — brokers must renew each year and update their disclosures if their practices change materially during the year.

The $200/day non-registration penalty accrues from the day a data broker was required to register and failed to do so. For companies that missed the January 2024 deadline and have still not registered as of 2026, the math is stark: 730 days at $200/day equals $146,000 in accrued penalties before any deletion-related violations are even counted. The CPPA has confirmed it is cross-referencing its new registration database against known data broker operating in the state to identify non-registrants.

Required Registration Disclosures

Each registered data broker must disclose the following information annually to the CPPA:

  • 01.Categories of personal information collected — using the specific category taxonomy defined in the CCPA/CPRA (identifiers, commercial information, biometric data, internet activity, geolocation, professional information, sensitive personal information, etc.)
  • 02.Sources of personal information — whether data is collected directly, purchased from third parties, compiled from public records, or obtained through tracking technologies
  • 03.Third parties with whom personal information is shared or sold — categories of recipients and the purpose of each sharing arrangement
  • 04.Data retention periods — how long each category of personal information is retained and the criteria used to determine retention length
  • 05.Whether the broker collects data on minors — and if so, what processes are in place to identify and handle minors' data with heightened protections
  • 06.Contact information for privacy inquiries — including a designated email address or web form for individual consumer requests outside the centralized portal
  • 07.Security certification — an attestation that the broker has implemented reasonable security measures to protect the personal information it holds

The registration fee is tiered based on the volume of consumers whose data the broker processes. Small brokers pay a minimum annual fee; large-scale operations with data on millions of California residents pay substantially more. The fee structure is designed both to fund the CPPA's enforcement operations and to reflect the greater systemic risk posed by high-volume brokers. The CPPA publishes a searchable registry of all registered data brokers — making non-registration a publicly visible compliance failure.

The $200/Day Fine: Mechanics, Exposure Calculations, and How Enforcement Works

The Delete Act's penalty structure is deliberately designed to scale with the volume and duration of non-compliance. The base penalty of $200 per consumer per day applies separately to: (1) failure to register or renew registration with the CPPA, and (2) failure to honor a deletion request submitted through the centralized portal within the required timeframe. These are two independent penalty streams that can run concurrently.

The 45-day response window for deletion requests begins the moment the CPPA's portal transmits the request to the data broker. Extensions of up to 45 additional days are permitted — but only if the broker notifies the consumer and the CPPA within the initial period and provides a specific reason for the extension. Simply failing to respond within 45 days triggers the $200/day clock, which then accrues on a per-request basis until the deletion is completed, the request is resolved through a documented exception, or the CPPA takes enforcement action and imposes a fixed penalty.

Fine Exposure Calculator: Illustrative Scenarios

Scenario A: Mid-Size Data Broker, 60-Day Response Failure

500 consumers submit deletion requests through the CPPA portal. The broker's systems are not configured to receive and process portal requests automatically. After 60 days (15 days past the deadline), the broker completes deletion. Penalty: 500 consumers × 15 days × $200 = $1,500,000.

Scenario B: Unregistered Broker, 18 Months of Non-Registration

A data enrichment company failed to register by the January 2024 deadline. The CPPA identifies the company in March 2025 — 420 days after the deadline. Non-registration penalty: 420 days × $200 = $84,000 before any deletion-related penalties are calculated.

Scenario C: Large Broker, Systematic Deletion Failures

A people-search platform receives 10,000 deletion requests in the first 90 days of portal operation. Due to a technical integration failure, 2,000 requests go unfulfilled for 30 days past the deadline. Penalty: 2,000 consumers × 30 days × $200 = $12,000,000 for a single processing cycle.

The CPPA may investigate compliance proactively — without waiting for a consumer to file a complaint. The agency has authority to access data broker systems, review deletion request logs, and audit the technical implementation of a broker's deletion pipeline. CPPA enforcement staff has stated publicly that the agency intends to conduct random audits of registered brokers beginning in 2026 to verify that the deletion infrastructure is operational and that requests submitted through the portal are being processed correctly.

Unlike many regulatory regimes that offer lengthy cure periods before penalties are imposed, the Delete Act's $200/day penalties accrue automatically from the moment a deadline is missed. Companies cannot retroactively argue they "intended to comply" — the penalty is statutory and accrues regardless of intent. The CPPA does have discretion over whether to pursue enforcement action and can negotiate settlements, but there is no mechanism to zero out accumulated daily penalties once they have begun accruing. This makes proactive compliance far more economical than reactive remediation.

How to Handle Deletion Requests at Scale: The Operational Reality

The centralized portal model creates a fundamentally different operational challenge than handling individual consumer requests through a company-owned intake form. When the CPPA portal distributes a deletion request, data brokers receive a structured data payload they must process automatically at volume. Manual review workflows — the kind that many companies built for initial CCPA compliance — will not scale to the portal's throughput without creating systematic 45-day deadline violations.

The operational requirements for compliant at-scale deletion processing include: an automated API integration with the CPPA portal to receive requests in real time; a reliable identity matching system capable of linking an incoming deletion request to all records associated with the consumer across internal databases and subprocessor systems; a documented deletion workflow with system-level controls ensuring data is removed within the required window; a verification and confirmation system that sends completion acknowledgment back to the CPPA portal; and an audit log maintaining a complete record of every request received, processed, and completed for regulatory review purposes.

Identity Matching Challenges

The CPPA portal submits deletion requests using the consumer's self-reported identity information. Data brokers must match this against their own records — which may use different identifier schemas, contain data from multiple sources with varying quality, or store the consumer under multiple entries. Robust identity resolution logic is required to ensure deletion requests are matched comprehensively, not just literally.

Subprocessor Deletion Cascade

A deletion request does not only require removing data from a broker's own databases. It must cascade to all service providers and contractors processing that data on the broker's behalf. This requires brokers to have contractual deletion obligations flowing through their vendor agreements and a technical mechanism to instruct subprocessors to delete within the same 45-day window.

Backup and Archive Handling

Deletion requests must cover backup and archival copies of data, not just production databases. Companies that maintain long-term backups for disaster recovery must have a process for flagging deleted consumer records so that data is not inadvertently restored from backup. The "right to deletion" under both the Delete Act and CCPA/CPRA requires that backup data be addressed within reasonable timelines consistent with backup restoration schedules.

Exception Documentation

Not every deletion request must be honored. Legal retention obligations, fraud prevention necessity, security incident investigation, and other enumerated exceptions permit brokers to retain certain data even following a deletion request. But exceptions must be specifically documented — the broker must record which exception applies, why it applies to the specific consumer's data, and what the expected retention period is under that exception. Blanket exception policies will not satisfy CPPA scrutiny.

Technical Infrastructure Checklist for Delete Act Compliance

  • CPPA portal API integration tested and operational — requests received automatically without manual intervention
  • Identity resolution logic documented and validated against test consumer records
  • Deletion workflow covers all internal databases including analytics, CRM, data warehouse, and archival storage
  • Subprocessor deletion instruction mechanism in place with contractual backing in all vendor agreements
  • SLA monitoring dashboard tracking 45-day deadline status per request in real time
  • Automated confirmation sent to CPPA portal upon deletion completion
  • Audit log capturing request receipt timestamp, identity match outcome, deletion actions taken, and completion timestamp
  • Exception workflow with per-request documentation and approval chain for retained data

Automate Your DSR and Deletion Request Workflows

LowerPlane's CCPA and GDPR DSR management modules handle intake, identity verification, deadline tracking, subprocessor cascades, and audit documentation — so your team can honor deletion requests at scale without building custom infrastructure. Book a demo to see how compliance teams use LowerPlane to stay ahead of California's enforcement timeline.

The Delete Act and CCPA/CPRA: How the Frameworks Intersect

California's privacy regulatory landscape now involves three overlapping frameworks: the original CCPA, the CPRA amendments that expanded consumer rights and created the CPPA as an independent enforcement agency, and the Delete Act's data-broker-specific obligations. For companies that qualify as data brokers and also have direct consumer relationships — for example, a credit monitoring service that both sells consumer data and offers direct consumer products — all three frameworks apply simultaneously.

The CCPA/CPRA already gave California consumers the right to request deletion from businesses that collect their data directly. The Delete Act adds a parallel deletion channel through the CPPA portal specifically targeting the data broker ecosystem. Importantly, a consumer who submits a deletion request through the centralized portal does not waive their right to submit a separate direct deletion request to the same company under the CCPA/CPRA. Data brokers must be prepared to handle both channels and ensure both sets of obligations are tracked and fulfilled within their respective deadlines.

DimensionCCPA/CPRA Right to DeleteDelete Act Centralized Portal
Who can submitAny consumer with a direct relationshipAny California consumer via CPPA portal
Who must respondAny covered business under CCPA/CPRARegistered data brokers only
Response deadline45 days (extendable 45 days)45 days (extendable 45 days)
Penalty for failureUp to $7,500 per intentional violation (CPRA)$200/day per consumer request
Enforcement triggerConsumer complaint or CPPA investigationCPPA audit, proactive enforcement, or complaint
Subprocessor obligationMust instruct service providers to deleteMust instruct all service providers to delete

One significant CPRA interaction affects how data brokers handle opt-out of sale and sharing. Under CPRA, consumers can opt out of the sale or sharing of their personal information with third parties. For data brokers, this opt-out right effectively prevents the core business activity of reselling consumer data to new buyers. While an opt-out does not require deleting existing records the same way a deletion request does, it does require the broker to suppress the consumer from future sale or sharing activity — creating a separate suppression list obligation that must be maintained indefinitely.

The Delete Act and CPRA together create a compliance matrix where data brokers must simultaneously manage deletion requests (removing data), opt-out requests (suppressing data from future sales), and access requests (providing a copy of data). Each right type has its own workflow, deadline, and documentation requirement. Companies that have built these as separate standalone processes risk gaps at the intersections — for example, processing a deletion request without also checking and honoring any existing opt-out preference, or honoring an opt-out without verifying whether a pending deletion request has also been submitted through the portal.

Practical Compliance Steps for Data Brokers in 2026

If your organization is a data broker — or believes it may qualify — the immediate priority is assessing your current registration and operational status against both the registration obligations that have been in effect since January 2024 and the deletion processing obligations that activated January 31, 2026. Below is a structured compliance action plan organized by urgency.

Immediate (Within 30 Days): Register or Confirm Registration

If your organization has not registered with the CPPA as a data broker, do so immediately. Every day without registration is a $200 penalty day. Registration requires disclosing data categories, sources, retention periods, and sharing practices — which means you will need an internal data inventory to complete the process accurately. Rushing registration with inaccurate disclosures creates a different kind of legal exposure, so balance speed with accuracy. If you are genuinely uncertain whether your business qualifies as a data broker under the Act's definitions, retain California privacy counsel to assess the question before either registering or concluding no registration is required.

Short-Term (30–60 Days): Integrate with the CPPA Deletion Portal

The CPPA provides technical specifications for the API integration that data brokers use to receive and acknowledge deletion requests from the centralized portal. Prioritize building or procuring this integration, as it is the core operational mechanism through which the $200/day penalty risk materializes. Test the integration against the CPPA's sandbox environment before going live. Establish a monitoring alert for integration failures so that technical downtime does not silently allow deletion requests to exceed their deadlines.

Medium-Term (60–90 Days): Audit and Update Vendor Agreements

Review all contracts with service providers that process personal information on your behalf. Confirm that each agreement contains a deletion obligation matching the Delete Act's requirements — specifically, that subprocessors must delete consumer data within the same timeframe as the broker's obligation when instructed to do so. Where agreements are missing these terms, issue updated data processing addenda. Prioritize vendors with access to the largest volumes of consumer data and those where data deletion may require a manual workflow on the vendor's side.

Ongoing: DSR SLA Monitoring and Annual Registration Renewal

Establish a real-time SLA dashboard tracking the status of every active deletion request against its 45-day deadline. Assign clear ownership for deletion request fulfillment — someone who receives an alert when a request is approaching deadline without a completion record. Implement a quarterly internal audit reviewing a sample of completed deletion requests to verify that all required steps were taken. Remember that registration must be renewed annually, and disclosures must be updated if your data practices change materially during the year. Treat the annual renewal as an opportunity to revisit your data inventory and confirm disclosures remain accurate.

How LowerPlane Supports CCPA and GDPR DSR Management

LowerPlane was built to eliminate the manual, spreadsheet-driven compliance work that creates systematic risk at scale. Our CCPA and GDPR modules provide purpose-built tooling for every stage of the data subject request lifecycle — from intake to fulfillment to audit documentation.

Multi-Channel DSR Intake

LowerPlane consolidates deletion requests, access requests, and opt-out signals from multiple intake channels — including direct consumer submissions, email, and CPPA portal forwarding — into a single unified queue. Each request is timestamped, categorized by right type, and assigned a SLA deadline automatically. Privacy teams manage the full request pipeline from one interface rather than tracking requests across separate systems.

Deadline Tracking and Escalation Alerts

Every active request in LowerPlane displays a real-time deadline countdown and completion status. Automated alerts notify responsible team members when requests approach defined warning thresholds — for example, at 30 days and again at 40 days for a 45-day obligation. Escalation rules route overdue requests to senior privacy team members automatically, ensuring no request falls through without management visibility.

Audit-Ready Documentation

LowerPlane generates a complete, immutable audit log for every DSR processed — capturing the request receipt timestamp, identity verification steps, deletion actions taken across each system, subprocessor instruction records, and completion confirmation. This documentation package satisfies the CPPA's record-keeping expectations and provides a clear defense record in the event of an audit or enforcement investigation.

Cross-Framework Compliance Overlap

For organizations subject to both CCPA/CPRA and GDPR, LowerPlane's control library maps overlapping obligations across frameworks. DSR workflows configured for GDPR Article 17 erasure requests automatically apply to California deletion requests, reducing duplicated implementation effort. Evidence collected for CCPA DSR compliance also satisfies relevant controls in ISO 27001 and SOC 2, enabling multi-framework efficiency across a single compliance program.

Key Takeaways

  1. 1

    The Delete Act's $200/day per-consumer penalty for unfulfilled deletion requests activated January 31, 2026. At scale, even moderate processing failures generate seven-figure exposure within weeks — making proactive compliance far cheaper than reactive remediation.

  2. 2

    The data broker definition is broader than most companies expect. Any business that collects and sells or shares personal information about consumers with whom it has no direct relationship qualifies — including data enrichment platforms, audience data providers, background-check services, and many analytics companies.

  3. 3

    Registration with the CPPA was required by January 31, 2024. Unregistered brokers face a separate $200/day penalty that has been accruing since that date — potentially representing tens of thousands of dollars in accrued liability before any deletion request is even received.

  4. 4

    Handling deletion requests at scale requires automated infrastructure — API integration with the CPPA portal, identity resolution logic, subprocessor deletion cascades, and SLA monitoring. Manual review workflows will create systematic deadline failures at volume.

  5. 5

    The Delete Act operates alongside CCPA/CPRA — not instead of it. Data brokers must manage both the CPPA portal deletion channel and direct CCPA/CPRA consumer requests simultaneously, each with its own workflow and documentation requirements.

  6. 6

    CPPA enforcement is proactive, not complaint-driven. The agency has authority to audit registered data brokers without a consumer triggering the investigation — making operational compliance, not just paper compliance, the only viable strategy.

Frequently Asked Questions

Does the California Delete Act apply to companies headquartered outside California?
Yes. The Delete Act applies to any business that qualifies as a data broker and conducts business in California — regardless of where the business is incorporated or headquartered. "Conducting business in California" is interpreted broadly and includes collecting data from California residents, even if the company has no physical presence in the state. Any company that holds and monetizes personal information about California residents is likely in scope.
What is the difference between the Delete Act's deletion obligation and the CCPA right to deletion?
The CCPA right to deletion applies when a consumer submits a request directly to a business they have a relationship with. The Delete Act creates an additional, parallel deletion channel through the CPPA's centralized portal specifically targeting data brokers — who consumers may have no direct relationship with and might not even know hold their data. The Delete Act's centralized mechanism means consumers do not need to identify specific data brokers individually — a single portal submission reaches all registered brokers simultaneously. Data brokers must honor both channels and track each through separate but coordinated workflows.
Are there exceptions that allow data brokers to refuse a deletion request?
Yes, the Delete Act mirrors the CCPA/CPRA exception framework. Data brokers may decline to delete information that is necessary to complete a transaction the consumer requested, detect security incidents, protect against fraud or illegal activity, debug or repair technical errors, exercise free speech or another legal right, comply with a legal obligation, or conduct certain research in the public interest. Each exception must be specifically documented and applied on a per-request basis — a blanket policy of applying exceptions categorically will not satisfy regulatory scrutiny. When an exception applies, the broker must notify the consumer and the CPPA of the grounds for declining to delete.
How does the CPPA's centralized deletion portal actually work technically?
The CPPA operates a consumer-facing web portal where California residents can submit a deletion request by providing their identity information. The CPPA's systems then generate a structured deletion request payload and transmit it to all registered data brokers via a secure API. Data brokers must integrate their systems with this API to receive requests automatically. The CPPA's technical specifications document the API format, authentication requirements, and the acknowledgment format brokers must send back upon completing deletion. Brokers that have not built this integration cannot receive portal requests through any other channel — which means manual check-in processes are not an acceptable substitute.
Can a data broker negotiate a settlement with the CPPA to reduce accrued penalties?
The CPPA has enforcement discretion and has settled cases for amounts below the maximum statutory penalty. However, settling does not mean accrued penalties simply disappear — negotiations typically result in a reduced final penalty in exchange for demonstrated remediation steps, cooperation with the investigation, and enforceable compliance commitments. Companies that approach the CPPA proactively — reporting non-compliance and presenting a remediation plan before the agency discovers the violation — are generally treated more favorably than those investigated reactively. The Delete Act's legislative history reflects an intent to create real financial consequences, so regulators are unlikely to offer settlements that remove the deterrent effect for systemic or willful violations.
Does the Delete Act affect how data brokers handle data about minors?
Yes, and the obligations for minors' data are heightened under the Delete Act and the CPRA. Data brokers must disclose in their registration whether they collect personal information about minors under 16. The CPRA's opt-in requirement for selling or sharing data of consumers under 16 applies to data brokers. Additionally, the CPPA has indicated that enforcement involving minors' data will be treated as a higher priority and may attract larger penalty determinations. Data brokers should implement age-signal analysis to identify records that may correspond to minor consumers and apply heightened protections proactively.

Stay Ahead of California Privacy Enforcement

Join 5,000+ compliance professionals receiving weekly insights on state privacy laws, CCPA enforcement updates, and practical compliance guidance. No fluff — just actionable intelligence delivered to your inbox.

No spam. Unsubscribe anytime.