Reference
Glossary
| Term | Definition |
|---|---|
| Batch | The consumer deletion list(s) that a data broker is currently processing. A new batch cannot be generated until a data broker returns response codes for all of the work items in the current batch. |
| DROP | Delete Request and Opt-out Platform — the platform created by CalPrivacy for consumers to submit deletion and opt-out requests and for data brokers to retrieve and respond to them |
| Delete Act | California law requiring data brokers to process consumer deletion requests through DROP (see Civ. Code § 1798.99.80 et seq.) |
| CPPA / CalPrivacy | The California Privacy Protection Agency — the state agency responsible for DROP |
| API key | The credential sent in the X-API-KEY header to authenticate API requests |
| Data broker ID | The unique identification number assigned to each data broker after it has successfully created its DROP account, used in file naming |
| Consumer deletion list(s) | A list containing one or more type of consumer identifier for every consumer that has submitted a deletion request through DROP. When made available to a data broker through DROP, the consumer deletion list includes the applicable identifier in a hashed format and the work item Id. |
| Work item | The pair of a unique Work Item Id and a hashed identifier |
| Work item Id | An alphanumeric character string that represents a single consumer identifier assigned by DROP, identified by its Id in a CSV file |
| NDZ | Name + Date of Birth + ZIP — a composite-hash list type |
| MAID | Mobile Advertising Identifier |
| VIN | Vehicle Identification Number |
| CTVID | Connected TV Identifier — covers smart TVs, streaming players, and gaming consoles |
| NameVIN | Name + VIN — a composite-hash list type |
| New upload | Submission of new status responses |
| Amend upload | Correction or update to previously submitted status responses |
| Composite hash | A multi-step hash where individual fields are hashed first, concatenated, then hashed again (used by NDZ and NameVIN) |
Status code reference
| 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 |
Reference codes 0 and 1 are unused.
For more information on the legal requirements based on match outcomes, see Civil Code section 1798.99.80 et seq. and CCR, title 11, section 7600 et seq.
Documentation map
| Document | Audience | Contents |
|---|---|---|
| Processing DROP requests | All | Step-by-step guide to the download-process-upload cycle |
| Technical documentation | All | Introduction page, current version updates |
| Operations and API documentation | Technical | API key generation, endpoints, file schema, hashing and standardization rules, notifications (email and webhook), request examples, error handling, rate limits |
| Reference | All | This page — glossary, status codes, versioning, links |
| OpenAPI Spec | Developers | Machine-readable API definition for OpenAPI-compatible tools |
Contact and support
Use the form provided in your DROP account to contact us.
When reporting an issue, include:
- Data Broker ID
- Timestamp (Pacific Time)
- Endpoint and HTTP status code
- File name involved
- Upload response payload or error message
Version history
| Version | Date | Notes |
|---|---|---|
| 1.3.0 | November 19, 2026 |
|
| 1.2.0 | July 2, 2026 |
|
| 1.1.0 | June 3, 2026 | General release on privacy.ca.gov/drop-for-data-brokers
|
| 1.0.0 | April 2, 2026 | Initial release in DROP
|