Processing DROP requests
To comply with the Delete Act, data brokers must use DROP to download and process deletion requests.
Note: With the passage of AB 883, data brokers will be required to process deletion requests within 30 days effective January 1, 2027. More information will be available soon.
Before you start
Before you get started, ensure that you:
- Create an account in DROP
- Register as a data broker (when applicable)
- Pay required fees (registration or access fees)
- Select your consumer deletion list(s)
- Choose your integration method (API or manual)
- Understand the requirements and workflow
- Complete your testing in the DROP Sandbox within your DROP account (optional)
Deletion request processing overview
DROP
Your system
DROP
Download consumer deletion lists
Standardize and hash your records
Match and process
Report status
Repeat
at least once every
45 days
DROP
Download consumer deletion lists
Your system
Standardize and hash your records
Match and process
DROP
Report status
Repeat
at least once every
45 days
Ongoing
Direct your service providers to process accordingly
Maintain list of identifiers needed to ensure ongoing compliance for matched and unmatched records
Deletion request processing is an ongoing pull-process-pull respond cycle, not a one-time integration. The steps below summarize that cycle.
- Set up account and register, if applicable (one-time)
- Generate API key (one-time or as needed)
- Generate and download batch
- Extract and read CSV(s)
- Match against your standardized and hashed records
- Take required action for each match (delete, opt out, or no action)
- Upload status CSV(s) to DROP and wait for validation
Repeat steps 3 through 7 to continue processing requests.
For more information on the legal requirements related to deletion request processing, including relevant timelines for ongoing processing, see Civil Code section 1798.99.80 et seq. and California Code of Regulations (CCR), title 11, section 7600 et seq.
Deletion request processing – step by step
1. Set up your DROP account (one-time)
Create an account in DROP, complete registration, if applicable, pay required fees, and select the consumer deletion list(s) you will process.
Access to create a DROP account is limited to data brokers only. Data brokers may authorize a third-party integrator or similar to access their DROP account for purposes of deletion request processing.
Select and download consumer deletion lists
Data brokers must download their selected consumer deletion list(s) at least once every 45 days. You will do this by either API (automated) or manually within DROP. Beginning January 1, 2027, data brokers must download their lists at least once every 30 days.
Consumer deletion lists contain hashed identifiers.
There are six lists:
- First name + last name + date of birth + ZIP code
- Email address
- Phone number
- Mobile advertising ID
- First name + last name + VIN
- Connected TV identifier
Data brokers must select all consumer deletion lists that contain a consumer identifier corresponding to personal information in the data broker’s records. However, a data broker may select fewer lists if the consumer identifiers used across multiple lists would lead to matches with the exact same set of consumers in the data broker’s records. For example, if a data broker collects both email addresses and telephone numbers for every consumer in its records, then the data broker may select only the email address or telephone number consumer deletion list. If, however, a data broker collects email addresses for some consumers and telephone numbers for other consumers, then the data broker must select both lists. (Cal. Code Regs., tit. 11, § 7610(a)(3).)
If you want to change your consumer deletion list(s), you may do so in DROP after your current batch is returned. Changes to your selection will take effect with the next batch you download.
2. Generate your API key (if integrating via API)
Generate an API key in the portal. The key is scoped to your selected consumer deletion list(s). More information about API integration can be found on the Operations and API documentation page.
Note: Integration via API is not required. You may use the manual download/upload option in DROP.
3. Generate and download your batch
To retrieve your consumer deletion lists, you must first generate a batch for download.
Note: You must return all required information for any outstanding batch before you can download a new one.
Request your batch via API or manually in DROP. Generating a batch can take a few minutes. You will be notified via email and API (if applicable) when the batch is ready to download. Your processing clock begins once you completely download the batch.
There is no limit on the number of batches you may download in a given cycle. Choose a processing schedule based on your workflows and needs, provided that your schedule satisfies relevant processing timelines.
If your automated connection with DROP fails for any reason, please let us know as soon as possible. You must notify CalPrivacy in writing through your DROP account no later than 45 days after detecting the failure that is not due to an error from the business. If your automated connection with DROP fails, you may process manually in DROP. (Cal. Code Regs., tit. 11, § 7612.) Processing timelines still apply.
Data brokers must access DROP and download a batch at least once every 45 days.
4. Extract and read
The batch is a ZIP archive containing one CSV file per selected consumer deletion list.
Each CSV contains hashed consumer identifiers included in deletion requests. DROP does not store or make available for download raw consumer identifiers.
Unzip the archive and read each CSV file.
After initial download and completed upload, future downloads will include only new identifiers added to or removed from DROP since your last completed batch. If any previously delivered identifiers have been removed, for example if a consumer cancels their deletion request, the download will also include a CSV file containing those removed identifiers. Read more about cancellations in Removed identifiers file schema.
5. Match records
To match DROP identifiers against your own records, you must standardize and hash the identifiers in your records using the same rules.
You must standardize each value using the rules for its identifier type, in the order listed. Then hash the standardized value using SHA-256 with UTF-8 input encoding and encode the hash using standard Base64, keeping uppercase and lowercase letters, +, /, and the ending =.
Refer to the Hashing and standardization section of our technical documentation for more detailed information about your production implementation of the standardization and hashing requirements. Furthermore, ensure alignment with the specific requirements published in the DROP Transliteration mapping section.
Note: Data brokers are not required to maintain the identifiers in standardized and hashed form within their own database.
Tip: Use the standardization and hashing tool in the DROP Sandbox within your DROP account to verify your implementation of the standardization and hashing rules using fake data.
If you find an exact match to a consumer:
- Delete all non-exempt personal information, including inferences, about the consumer
- Direct all service providers and contractors to delete matching records
If you find a match and multiple consumers are associated with a single matched identifier:
- Opt all associated consumers out of sale and sharing (For more information about opt-outs see Cal. Civ. Code § 1798.120.)
- Direct all of your service providers and contractors to opt out accordingly
Whether or not you find a match:
- Save and maintain a list of DROP identifiers for all consumers who submitted a deletion request via DROP to screen any newly collected records before they are sold or shared to ensure the deletion requests are maintained on an ongoing basis. For more details, review Ongoing processing.
6. Process records based on match outcomes
Use the following status codes when reporting match outcomes:
| Code | Label | Meaning |
|---|---|---|
| 2 | Exempted | Match found and personal information is exempt |
| 3 | Deleted | Match found and non-exempt personal information was deleted |
| 4 | Opted out | Multiple consumers are linked to the same identifier and all were opted out of sale or sharing |
| 5 | Not found | No match found after completing the matching process |
For more information on the legal requirements based on match outcomes, see Civil Code section 1798.99.80 et seq. and California Code of Regulations (CCR), title 11, section 7600 et seq,
Note: You must direct all of your service providers or contractors to process deletions and opt-outs based on the match outcomes above.
7. Upload status response and wait for validation
Within 45 days of your download date, report status to DROP for all records included in your batch.
Uploading
A single upload request can have a maximum of 10 files and total size of 100MB. Uploads for a single batch are limited to a maximum of 100 files. While the system does technically support partial uploads for a given consumer deletion list, we recommend uploading one file per consumer deletion list, for efficient processing. If you reach the upload limit of 100 files for a given batch, please contact us. We can extend the limit, if necessary.
Your batch will not be considered complete until all outstanding records from your batch are uploaded and validated successfully. You will receive an email to confirm the records were all validated.
Records in the “Removed” CSV
During each cycle of processing, there may be records in the “removed.csv”. These records reflect a consumer’s decision to remove identifiers or cancel their DROP request entirely. You are not required to report status codes for the work items in this file. Review Removed identifiers file schema for further guidance about this list type.
Note: Work item Ids are distinct to specific consumer identifiers and distinct to each deletion request. For example, two consumers may share a common identifier, such as a landline telephone, but that same landline would have a distinct work item Id for each separate deletion request. Thus, it is possible for the hashed identifier to appear in both the removed.csv file and a consumer deletion list with different work item Ids that distinguish between consumer preferences. You must process and report the work item Id on the deletion list as opted out of sale and sharing, as referenced in 5. Match records. You are not required to report a status code for those in the removed.csv file.
Validation
Once you upload your file(s), DROP will validate the upload. Validation is a two-step process. Uploads are validated at both the file and record levels.
File level validation
First, DROP validates the file(s).
To pass file validation at this stage:
- API key must be present and valid
- Uploads must use
multipart/form-datawith the field namefiles - Uploaded files must be CSV files
- CSV header must be
Id,Status
You will be notified if a file fails validation immediately as the API returns an HTTP error or a file-level rejection message will be shown on-screen in DROP (for manual uploads). For more information see API error handling.
Record-level validation
DROP also performs record-level validation — i.e. each work item is evaluated for correct instance and accepted status code. Processing times may vary based on system usage and volume. You will be notified via email once record-level validation is complete. If processing is taking longer than usual, check back in 24 hours.
When DROP finishes processing your records, DROP will send an email to the primary and secondary contact email addresses listed on your account. This email will tell you whether or not all of the records were validated. You must read this notification to determine if there are any records that failed validation. The same information can also be found in your DROP account.
In the event any records are rejected, this email will provide you with a link you may use to sign in to your DROP account and download information about the rejected records, including the reason(s) for rejection. Rejected records should be re-uploaded using the upload endpoint.
Once all files are uploaded, verify that your batch is complete. You can verify batch completion by:
- Signing in to DROP and confirming your batch status on your dashboard
- Checking your email notifications – we send an email once your batch is complete
- Verifying via webhook, if configured – we send a webhook notification once your batch is complete
For more information, review Notifications.
Repeat this cycle
The cycle starts when you download a new batch – you must do this at least once every 45 days. You then have up to 45 days to complete the cycle. This includes downloading the next list. Below is an example timeline:
- Initial download date: Download your consumer deletion lists
- Day 1 (the day following the download date): Processing clock begins
- By Day 45: Process and upload your responses
- Day 45: You must begin the next cycle (if you haven’t done so already). You are required to download, process and upload at least once every 45 days on an ongoing basis
Note: Effective January 1, 2027, the processing timeline will be 30 days. More information will be available soon.
Ongoing processing
There are some tasks you must regularly complete to lawfully process DROP requests. Consumers are not required to resubmit requests. You are responsible for maintaining consumer requests on an ongoing basis.
Maintain consumer deletion lists
Data brokers should maintain a list of identifiers needed to ensure ongoing compliance for both matched and unmatched records. Some people refer to this as a “suppression list.” Compare this list against any newly collected records before new personal information is sold or shared.
For this list, you do not have to use our identifiers. Use the identifiers you need to maintain compliance.
Retain only the minimum data necessary to maintain your compliance obligations; this data may not be used for any other purpose.
Amending records
If a data broker detects a change in status for a record that has already been processed, the data broker must update the status in DROP at its next access session.
Amend is used only for changing the status of a record that has been reported on previously in DROP.
Below is an example of when to use Amend:
- A data broker is unable to match a given identifier to a consumer in their records so they report the status for that identifier as “NOT FOUND”
- Several months later, the data broker ingests a new database and is able to match the consumer for which status has already been reported. Now, the data broker must delete all non-exempt personal information for that consumer and report the status as “DELETED”
- The data broker must report back the “DELETED” status to DROP at the next access session
Review Technical documentation for more information on amending records.
Service providers and contractors
Some data brokers work with service providers and contractors to offer their services and, as part of that workflow, share consumer information. As part of processing obligations, data brokers must direct all of their service providers and contractors to take the required action for all personal information associated with DROP requests.
This includes deleting all non-exempt personal information or opting a consumer out of the sale or sharing of their personal information.
CalPrivacy is committed to providing resources to assist businesses with understanding the rights and obligations provided in the Delete Act. These materials are educational tools to help you understand key requirements of the Delete Act and its related regulations.
These materials are not exhaustive, and your business is responsible for complying with all applicable statutory and regulatory requirements. Read the full text of the Delete Act and the full text of the regulations on Laws and regulations.