What DROP is
The Delete Act (Senate Bill 362, codified at California Civil Code §§ 1798.99.80 to 1798.99.89) told the California Privacy Protection Agency, which now calls itself CalPrivacy, to build one place where a Californian can ask every registered data broker to delete their personal information at once. That place is DROP, the Delete Request and Opt-out Platform. Consumers sign up on the public side. Brokers have a separate portal and an API.
A consumer gives DROP whatever identifiers they choose: email addresses, phone numbers, their name with date of birth and ZIP code, mobile advertising IDs, vehicle identification numbers, connected TV device IDs. DROP standardizes and hashes each one and puts it on a consumer deletion list for that identifier type. Brokers never see the plain values; they see SHA-256 hashes and must hash their own records the same way to find matches.
Scale matters here. CalPrivacy counted 581 registered data brokers in June 2026, a record at the time, and the Governor's office reported more than 475,000 Californians signed up by 13 August 2026. A first download can hold a very large number of rows.
Who has to use it
Every business that meets California's definition of a data broker and is registered with CalPrivacy. In short, a data broker is a business that knowingly collects and sells to third parties the personal information of a consumer with whom it has no direct relationship. Some data is carved out: to the extent a business is covered by the federal Fair Credit Reporting Act, the Gramm-Leach-Bliley Act, California's Insurance Information and Privacy Protection Act or certain health privacy laws, that part of its business is not data brokering.
If you are not sure whether the definition fits you, start with Am I a data broker? Registration itself, the annual January window and the fees are covered in data broker registration in California.
A broker that holds none of the six identifier types still has to take part. CalPrivacy's help pages say it must select at least one list and report every row on it as not found.
What a broker must do
The statute and the DROP regulations (Title 11, California Code of Regulations, §§ 7600 to 7622) come down to seven duties:
- Hold one DROP account for the legal entity, keep its contact details current and select every deletion list whose identifier type you hold.
- Access DROP on time: at least once every 45 calendar days from 1 August 2026, and every 30 days from 1 January 2027 under AB 883.
- Match properly: standardize your records with DROP's published rules, hash them the same way and compare like with like, in every system where the identifier lives.
- Act on matches: delete all non-exempt personal information of a single matched consumer, including inferences, and direct your service providers and contractors to do the same. Where one identifier matches several consumers, opt all of them out of sale and sharing instead.
- Report a status of 2, 3, 4 or 5 for every work item in the batch, inside the reporting window.
- Keep suppressing: do not sell or share new personal information of those consumers, and check newly collected records against the lists before you sell or share them.
- Keep records that let an independent auditor confirm all of the above, for at least six years.
One cycle, step by step
Every cycle has the same shape, whether you use the DROP portal by hand or the API.
| Step | What happens | Where it goes wrong |
|---|---|---|
| 1. Download | DROP builds a ZIP with one Id,Hash CSV per selected list, plus a removals file when requests were withdrawn. | A lost ZIP cannot simply be downloaded again while the batch is open. |
| 2. Standardize and hash | Your records are cleaned with the per-list rules and hashed with SHA-256, output as standard Base64. | Small differences (a phone extension, a ZIP+4) produce a different hash and a missed match. |
| 3. Match | Exact comparison of hashes, list by list, across every system that holds the identifier. | Checking only the main database and not the warehouse, CRM or vendor feeds. |
| 4. Act | Delete, or opt out where one identifier matches several people; instruct service providers. | Deleting without a record of who confirmed it and when. |
| 5. Report | Upload Id,Status files, one row per work item, before the window closes. | Header errors, duplicate file names and rejected rows that nobody re-uploads. |
| 6. Suppress | Keep the hashes of unmatched requests and screen new data against them before any sale. | Buying a new list next month and selling a deleted consumer again. |
The full walk-through, with file names and the upload checks DROP runs, is in how to process DROP requests.
Key dates
| Date | What happens |
|---|---|
| 1 January 2026 | The DROP regulations take effect. |
| 1 August 2026 | Brokers must start accessing DROP, then at least every 45 days. |
| 1 January 2027 | Under AB 883, brokers must download their lists at least once every 30 days. |
| 1 to 31 January, every year | Annual data broker registration and fee. |
| 1 July, every year | Request metrics for the previous year go in your privacy policy (Civ. Code § 1798.99.85). |
| From 1 January 2028 | Independent audit of DROP compliance, then every three years. |
How the 45 days are counted, with worked dates, is in DROP deadlines. What AB 883 changes, and what it leaves unclear, is in AB 883 and the 30-day cycle.
The four statuses
Every work item gets exactly one status code. Codes 0 and 1 are not used.
- 2 Exempted: a match was found and all of that consumer's personal information is exempt.
- 3 Deleted: a match was found and the non-exempt personal information was deleted.
- 4 Opted out: the identifier matched more than one consumer, and all of them were opted out of sale and sharing.
- 5 Not found: no match after the full matching process.
The edge cases, such as a consumer whose data is only partly exempt, are in DROP status codes 2 to 5. Exemptions themselves are covered in DROP exemptions.
Between batches
Reporting a batch does not end the duty. After deleting a consumer, a broker may not sell or share new personal information about them, and must keep deleting what it collects later. For requests that matched nothing, the regulations say to keep the consumer deletion list and compare newly collected records with it before selling or sharing them. In practice that means a suppression list, kept up to date as later batches add requests and the removals file withdraws them. See the DROP suppression list.
If a request you reported as 5 later matches data you acquired, the status changes. You report the new status through the amend route at your next access, not by uploading the old batch again.
Records and the audit
From 1 January 2028, and every three years after, a broker must have an independent third party audit its compliance with the deletion duties. The audit report is kept for at least six years and must be handed to CalPrivacy within five business days of a written request. CalPrivacy started formal rulemaking on the audit rules on 13 November 2026. The proposal includes a first audit period from 1 August 2026 to 1 August 2028, with the report due 1 November 2028, but that is still a proposal.
An auditor can only confirm what you can show: when each batch was downloaded, how many rows each list had, what you matched, who confirmed each deletion, which files you uploaded and what DROP answered. Start keeping that now. More in Delete Act audits.
Fees and penalties
Registration for 2026 cost $6,000 plus a card fee of up to 2.99%. CalPrivacy adopted a $9,500 fee for 2027. A broker that fails to process deletion requests is liable for an administrative fine of $200 for each deletion request for each day, plus the costs of the investigation. Failing to register carries its own $200 a day. Because the fine counts requests, a late batch with thousands of work items is a large number quickly; the penalty calculator shows the arithmetic, and Delete Act penalties explains how exposure is counted.
A working checklist
- One DROP account for the legal entity, with a shared mailbox as a contact so validation emails are not missed.
- Every list selected that matches an identifier type you hold, and a written note of why any list is not selected.
- A calendar with the next download date and each open batch's report-by date, and a named person for each.
- A matching routine that follows the published standardization rules and passes CalPrivacy's test vectors.
- An inventory of every system and vendor that holds each identifier type.
- A written basis for every exemption you rely on.
- A suppression list checked before any new data is sold or shared.
- An evidence log of downloads, matches, confirmations, uploads and DROP's responses, kept six years.
You can run all of this with spreadsheets and scripts, or with a tool. How a batch runs in CalDrop Compliance shows one way; build or buy weighs the options.
Questions
What is DROP?
DROP is the Delete Request and Opt-out Platform run by the California Privacy Protection Agency (CalPrivacy). Consumers use it to send one deletion request to every registered data broker. Brokers download hashed identifiers from it, match them, act on matches and report a status for each request.
How often must a data broker access DROP?
At least once every 45 calendar days from 1 August 2026. From 1 January 2027, under AB 883, at least once every 30 days.
Do I have to use the DROP API?
No. CalPrivacy says integration via API is not required. You can download batches and upload status files in the DROP portal. The deadlines and file formats are the same either way.
What if none of my data matches the DROP lists?
You still select at least one list and report status 5, not found, for every row in each batch, inside the deadline.
What is the penalty for not processing DROP requests?
The Delete Act sets an administrative fine of $200 for each deletion request for each day the broker fails to process it, plus the costs of the investigation.
When is the first Delete Act audit?
The statute requires an independent audit from 1 January 2028 and every three years after. Proposed rules published in November 2026 would set a first audit period of 1 August 2026 to 1 August 2028, with the report due 1 November 2028. Those rules are not final.
Is CalDrop Compliance part of CalPrivacy?
No. CalDrop Compliance is an independent product by Preptics LLC. It is not affiliated with or endorsed by CalPrivacy or the State of California.
Related
- How to process DROP requests, step by step
- DROP deadlines and how the clock counts
- DROP hashing and standardization
- Delete Act audits
- Try the live demo
Sources
- CalPrivacy: DROP for data brokers
- CalPrivacy: Processing DROP requests
- CalPrivacy: DROP technical reference (status codes)
- CalPrivacy: Account creation, fees and annual registration
- CalPrivacy: DROP help for data brokers
- DROP regulations, 11 CCR §§ 7600–7622 (PDF)
- California Civil Code § 1798.99.86
- CalPrivacy: Data brokers (penalties)
- CalPrivacy: DROP audits
- 2027 registration fee regulation, final text (PDF)
- CalPrivacy, 2 June 2026: registered data brokers hit a record high
- Office of the Governor, 13 August 2026
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).
