The four codes
These are the meanings in CalPrivacy's technical reference, with the wording the DROP regulations use (11 CCR § 7614(b)(2)) alongside.
| Code | Label | Meaning | Regulation wording |
|---|---|---|---|
2 | Exempted | A match was found and all of the consumer's personal information is exempt. | Record exempted |
3 | Deleted | A match was found and the non-exempt personal information was deleted. | Record deleted |
4 | Opted out | Several consumers are linked to the same identifier and all were opted out of sale or sharing. | Record opted out of sale |
5 | Not found | No match was found after completing the matching process. | Record not found |
The code goes in the Status column of your response file, next to the work item's Id. DROP rejects any other value. How to build and upload that file is in how to process DROP requests.
Choosing a code
Work out the code per work item, not per consumer or per hash. Start from how many distinct consumers in your records have the same hash for that list:
| Consumers matched | Their data | Action | Code |
|---|---|---|---|
| 0 | n/a | Keep the hash on your suppression list | 5 |
| 1 | Some or all non-exempt | Delete the non-exempt data, keep only what is exempt | 3 |
| 1 | All exempt | Keep it, use it only for the exempt purpose | 2 |
| 2 or more | Any | Opt every matched consumer out of sale and sharing | 4 |
Code 4 exists because a broker cannot tell which of several people with a shared phone number or email address made the request, and the regulations forbid contacting the consumer to find out. The law treats such a request as an opt-out of sale and sharing for everyone it matches.
In every matched case, also direct your service providers and contractors to delete (for 3) or opt out (for 4). The status you upload is a statement that this has been done.
Edge cases
Part of the data is exempt
Report 3, not 2. Code 2 is only for a consumer all of whose personal information is exempt. If you deleted anything, the record is deleted. The proposed regulations of November 2026 spell this out. What counts as exempt is in DROP exemptions.
Two work items with the same hash
Two consumers who share an identifier arrive as two work items with the same hash and different IDs. Report each one. If your records hold one person with that identifier, both work items point at the same match; if they hold several, both get 4.
A composite list nearly matches
NDZ and NameVIN match only on the full composite hash. A person with the right name and date of birth but a different ZIP code is not a match, and there is no partial-match status. If you hold several ZIP codes or name spellings for one person, hash each combination before you decide on 5.
The same hash is on the removals file and a list
A hash can appear in the Removed file (one consumer withdrew) and in a deletion list for a different consumer in the same batch. Removed rows get no status. CalPrivacy says the work item on the deletion list must be processed and reported as opted out of sale and sharing in that case, and the hash stays suppressed for the remaining consumer.
You hold no data of that type at all
Report 5 for every row. A broker that holds none of the six identifier types still selects at least one list and answers 5 throughout, within the deadline.
A match arrives before the data enters your systems
The proposed regulations would let a broker that catches a suppressed consumer while screening incoming data, before it is accepted into its systems, leave the existing status as it is. That is a proposal, not yet a rule.
What the consumer sees
Consumers can see how each broker answered. CalPrivacy's July 2026 explainer lists the results they may see: record deleted, record exempted, record opted out of sale, record not found, or pending while the broker has not answered. It also warns that updates can take up to 90 days to appear. A long run of pending answers is visible to the public and to CalPrivacy.
Changing a status later
A status is not final. If a request you reported as 5 later matches data you acquire, delete the data and report the new status at your next access through the amend route (POST /data/amend or the Amend button in the portal). Amend files may mix work items from several earlier batches of the same list, and amending does not restart any deadline.
Amend is only for statuses DROP already accepted. Rows DROP rejected were never accepted; upload those again through the normal upload, in a new file with a new suffix.
Common mistakes
- Reporting 2 because one field (say, a transaction record) is exempt, when the rest of the consumer's profile could be deleted.
- Reporting 3 for an identifier shared by several consumers, after deleting only one of them.
- Reporting 5 after checking only the main database, when the identifier also sits in a warehouse or vendor feed.
- Sending a status for a Removed row, which DROP will reject.
- Using 0 or 1, which are reserved and unused.
CalDrop Compliance proposes a code for each work item from the match count, lets you mark exemptions with a written basis, and records who confirmed each deletion. Try it on a practice batch.
Questions
What are the DROP status codes?
2 Exempted, 3 Deleted, 4 Opted out and 5 Not found. Codes 0 and 1 are unused. Each work item in a batch gets exactly one of them in the Status column of your Id,Status response file.
When should I use status 2, Exempted?
Only when a match was found and all of that consumer's personal information is exempt. If you deleted anything, report 3.
When should I use status 4, Opted out?
When the identifier matches more than one consumer in your records. You cannot tell which one made the request, so you opt all of them out of sale and sharing and report 4.
What do I report if I have no data of that type?
Status 5, Not found, for every row. A broker with no matching data still selects at least one list and reports 5 for each row within the deadline.
Can I change a DROP status after uploading it?
Yes. Use the amend route at your next access, for example to change 5 to 3 after you acquire data about the consumer. Amending does not restart the deadline.
Do I report a status for Removed rows?
No. Removed rows are withdrawn requests. DROP expects no status for them.
Related
Sources
- CalPrivacy: DROP technical reference (status codes)
- CalPrivacy: Processing DROP requests
- CalPrivacy: DROP help for data brokers
- CalPrivacy, July 2026: DROP data broker deletions, how do they work?
- DROP regulations, 11 CCR §§ 7600–7622 (PDF)
- California Civil Code § 1798.99.86
- CalPrivacy: DROP audits (proposed regulations)
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).
