Skip to content

DROP deletion requests vs CCPA deletion requests

A DROP request arrives as a hashed identifier in a batch you download from CalPrivacy, which has already checked the consumer's residency. You match it, report a status code to DROP, and keep that person deleted from then on. A CCPA request to delete comes from the consumer directly: you verify them yourself and answer them within 45 days.

Comparison · Published · By the CalDrop Compliance team · How we check facts

The nine differences

Section numbers are to the California Civil Code (Civ. Code) and Title 11 of the California Code of Regulations (11 CCR). We read the CCPA regulations and the DROP regulations in the versions effective 1 January 2026, and checked every cell against them on 22 November 2026.

QuestionDROP request (Delete Act)CCPA request to delete
Who sends it, and what arrivesThe consumer submits one request through DROP, and it reaches every registered broker they did not exclude. You download a batch of work items, each an Id and a SHA-256 hash of one identifier (email, phone, name with date of birth and ZIP, and others). You match by standardizing and hashing your own records the same way.Civ. Code §1798.99.86(a)(2)–(3); 11 CCR §§7612, 7613(a)(1); DROP technical documentationThe consumer, or an authorized agent, sends it to your business through the methods you offer: at least two, including a toll-free number unless you operate only online. It names the person with whatever details they choose to give, in plain text.Civ. Code §1798.130(a)(1)(A); 11 CCR §7063
Identity, and a match you cannot pin downCalPrivacy verifies the consumer's California residency before they can submit, and you must not contact the consumer to verify. If one identifier matches several consumers in your records, opt all of them out of sale and sharing and report status 4 (opted out).11 CCR §§7620(a), 7616(c), 7613(a)(2)(B), 7614(b)(2)(B); Civ. Code §1798.99.86(c)(1)(B)You verify the requester with a documented, reasonable method, free to them, matching their details against data you already hold before asking for more. If you cannot verify, you may deny and must tell them. If you sell or share and they have not opted out, ask whether they want to.11 CCR §§7060(a), (c)(1), (e), 7062(d), 7022(a), 7022(g)
Time to actDownload at least every 45 calendar days and process each request within 45 days of receiving it. From 1 January 2027 CalPrivacy says downloads move to at least every 30 days. It has not said whether the 45-day processing window also becomes 30, so we plan to 30 days, the cautious reading.Civ. Code §1798.99.86(c)(1), (c)(1)(A); 11 CCR §7612(a); CalPrivacy, DROP for data brokersConfirm receipt within 10 business days. Respond within 45 calendar days of receipt, counted from the day it arrives however long verification takes. You may extend once by up to 45 more days (90 in total) if you tell the consumer, with a reason, inside the first 45.Civ. Code §1798.130(a)(2)(A); 11 CCR §7021(a)–(b)
Exemptions, and how you show themThe CCPA deletion exceptions and its carve-outs (FCRA, GLBA, HIPAA and CMIA, DPPA, legal claims and others) apply. Report status 2 (exempted) only when all of the matched consumer's personal information is exempt; otherwise delete the rest and report 3 (deleted). First-party data need not be deleted. Exempt data may be used only for the exempt purpose.Civ. Code §1798.99.86(c)(2)–(3); 11 CCR §§7613(b)(1)(A), 7614(b)(2)(A), (C)The same exceptions and carve-outs. Deny in whole or in part with a detailed explanation of the basis, delete what the exception does not cover, use the rest only for that purpose, and instruct your service providers and contractors to do the same.Civ. Code §§1798.105(d), 1798.145; 11 CCR §7022(f)
After the first deletionThe duty continues. Delete the consumer's personal information at least once every 45 days and do not sell or share new personal information about them. For requests with no match, keep the deletion list and check newly collected records against it before you sell or share; report a later match at your next access session.Civ. Code §1798.99.86(d)(1)–(2); 11 CCR §§7613(c), 7614(a)(1)Each request gets one response; the regulations set no repeating cycle. You, your service providers and your contractors may keep a record of the request so that the data stays deleted.11 CCR §7022(e)
Service providers, contractors and third partiesDirect all service providers and contractors to delete, or to opt out where you reported status 4. You may share with them the minimum personal information needed to keep the consumer suppressed. The section's deletion duties name service providers and contractors, not third parties you sold to.Civ. Code §1798.99.86(c)(1)(C)–(D); 11 CCR §7613(d)–(e)Notify service providers and contractors to delete, and notify every third party you sold or shared the data with, unless that proves impossible or involves disproportionate effort. If you rely on that, give the consumer a detailed, factual explanation.Civ. Code §1798.105(c)(1); 11 CCR §7022(b)(2)–(3)
What you report, and to whomTo CalPrivacy, through DROP: one status code per work item, 2 (exempted), 3 (deleted), 4 (opted out) or 5 (not found), at your next access session, and before your next download if you upload by hand. The consumer sees the status in DROP; you do not write to them.11 CCR §7614(a)–(c); DROP technical referenceTo the consumer: whether you complied, and that you will keep a record of the request. Any denial needs a detailed explanation. Nothing goes to CalPrivacy.11 CCR §7022(e), (f)(1)
Records to keepFrom 1 January 2028 an independent audit every three years; keep the audit report and related materials for at least six years. Keep the minimum personal information needed to keep each DROP consumer deleted. Whether the CCPA's 24-month log rule also covers DROP requests is not stated.Civ. Code §1798.99.86(e)(1)–(3); 11 CCR §7613(b)(1)(B)Keep a record of each request and your response for at least 24 months, as a ticket or log with the request date, its nature, how it was made, your response date, the response and any basis for denial. Use that log for nothing else.11 CCR §7101(a)–(b), (d)
PenaltyAn administrative fine of $200 for each deletion request for each day the data broker fails to delete information as required, plus CalPrivacy's reasonable investigation and administration costs.Civ. Code §1798.99.82(d)An administrative fine of up to $2,663 per violation, or $7,988 per intentional violation or one involving a consumer known to be under 16 (CalPrivacy action); the same amounts as civil penalties in an Attorney General action. These are the 2025 CPI-adjusted figures; the statute says $2,500 and $7,500 and is adjusted every odd-numbered year.Civ. Code §§1798.155(a), 1798.199.90(a), 1798.199.95(d); CalPrivacy CPI notice, effective 1 January 2025

Where the rules overlap

The Delete Act borrows its exemptions from the CCPA, so one exemption analysis can serve both. Section 1798.99.86(c)(2) points to the deletion exceptions in §1798.105(d) and the carve-outs in §§1798.145 and 1798.146. What differs is how you show the result: a status code to DROP, or a written explanation to the consumer. More on status 2 in DROP exemptions.

Both sets of rules count deidentifying or aggregating data as deletion, and both let you wait on backups until the backup is restored or next used for a sale, disclosure or commercial purpose (11 CCR §§7022(d), 7613(b)(1)(C)(i)). They differ on first-party data. A DROP request does not require you to delete information you collected directly from the consumer as a first party (11 CCR §7613(b)(1)(A)), and CalPrivacy tells consumers the same. A CCPA request to delete covers personal information the business collected from the consumer (Civ. Code §1798.105(a)).

Can one consumer send both?

Yes. Nothing in the Delete Act or the CCPA stops a consumer who has a DROP request open from also writing to you under §1798.105. One reason they might: CalPrivacy's consumer pages say a DROP request does not reach data a business collected from them directly. Either request can also come through an authorized agent (11 CCR §§7063, 7621).

Treat them as two requests with two clocks. The DROP work item gets a status in its batch. The direct request gets a receipt within 10 business days and an answer within 45 days, whatever the DROP batch is doing.

Does a DROP deletion satisfy a CCPA request?

This is unsettled. We found nothing in the Delete Act, the CCPA, either set of regulations or CalPrivacy's DROP pages that says one request counts for the other. The rules also differ in ways that make a straight swap hard to defend. A DROP match need not reach first-party data, DROP forbids contacting the consumer while the CCPA requires a response to them, and only the CCPA rules set a 24-month request log.

The cautious reading, which we use: answer the CCPA request in full on its own clock. If your DROP cycle has already deleted the person's data, you can say so in your response, after checking that nothing new about them has arrived since. Log the request under 11 CCR §7101 either way.

The reverse question is open too. CalPrivacy has not said which status code fits a DROP work item for a consumer you already deleted after a direct CCPA request. Every work item still needs a status, so settle the rule with counsel and write it down.

What to change in your process

  1. Run two intake tracks, each with its own clock: DROP batches on the download cycle, and direct requests through the methods your privacy policy names.
  2. For direct requests, diary three dates on arrival: day 10 (business days) for the receipt, day 45 for the answer, and day 90 if you send an extension notice.
  3. Keep DROP data out of your CCPA workflow. Information you receive through DROP may be used only to comply with §1798.99.86 (11 CCR §7616(a)), so on our reading you should not use DROP hashes to look up or verify a direct requester. Verify them against your own records under §7060.
  4. Never contact a DROP consumer to verify (11 CCR §7616(c)). For an identifier shared by several people, opt them all out and report 4.
  5. Use one notice list for service providers and contractors, and add third parties you sold or shared data with for direct requests, which the CCPA requires and the DROP section does not mention.
  6. Write one exemption memo per data set, citing the §1798.105(d) or §1798.145 ground. Use it for status 2 decisions and for CCPA denial letters alike.
  7. Keep a CCPA request log with the six fields in 11 CCR §7101(b) for at least 24 months. Keep DROP cycle evidence for at least six years, the period the statute sets for audit materials (§1798.99.86(e)(3)).
  8. Have counsel confirm the points this page marks as open: whether a DROP deletion answers a later CCPA request, and which status fits a consumer deleted earlier under the CCPA.

One gap on our side: CalDrop Compliance runs the DROP cycle and keeps the evidence for it. It does not take in or answer direct CCPA requests, so that track needs its own tool or process.

Questions

Is a DROP request the same as a CCPA request to delete?

No. A DROP request is made under the Delete Act, Civil Code §1798.99.86, and processed under 11 CCR §§7610–7616. A request sent straight to your business is made under CCPA §1798.105 and handled under 11 CCR §7022. The Delete Act borrows the CCPA's deletion exceptions, but verification, timing, reporting and record-keeping differ.

Do I reply to the consumer for a DROP request?

No. You report a status code for each work item to CalPrivacy through DROP, and 11 CCR §7616(c) says a data broker shall not contact a consumer to verify a DROP request. The consumer sees the status in DROP.

How long do I have to answer each kind of request?

For DROP, download at least every 45 days and process each request within 45 days of receiving it; downloads move to at least every 30 days from 1 January 2027. For a CCPA request to delete, confirm receipt within 10 business days and respond within 45 calendar days, with one extension of up to 45 more days if you give notice.

Can I use DROP data to verify a CCPA requester?

On our reading, no. 11 CCR §7616(a) limits personal information received through DROP to complying with Civil Code §1798.99.86. Verify a direct requester against your own records under 11 CCR §§7060–7062.

More from the blog

Sources

  1. California Civil Code §1798.99.86 (Delete Act: DROP duties)
  2. California Civil Code §1798.99.82 (Delete Act penalties)
  3. California Civil Code §1798.105 (CCPA right to delete)
  4. California Civil Code §1798.130 (CCPA response times and methods)
  5. California Civil Code §1798.145 (CCPA exemptions)
  6. California Civil Code §1798.155 (CCPA administrative fines)
  7. California Civil Code §1798.199.90 (CCPA civil penalties)
  8. CCPA regulations, 11 CCR §7000 and following, effective 1 January 2026 (CalPrivacy PDF)
  9. DROP regulations, 11 CCR §§7600–7622, effective 1 January 2026 (CalPrivacy PDF)
  10. CalPrivacy: updated monetary thresholds in the CCPA (effective 1 January 2025)
  11. CalPrivacy: DROP for data brokers
  12. CalPrivacy: DROP operations and API documentation
  13. CalPrivacy: DROP technical reference (status codes)
  14. CalPrivacy: how DROP works (for consumers)

Written by the CalDrop Compliance team at Preptics LLC and last reviewed 22 November 2026. This guide explains the rules; it is not legal advice. CalDrop Compliance is an independent product of Preptics LLC. It is not affiliated with, endorsed by or operated by the State of California or the California Privacy Protection Agency (CalPrivacy).