How a DROP batch runs
Every 45 days (30 from 2027), DROP gives you a batch of hashed deletion requests. CalDrop Compliance takes it through five steps: download, match, confirm, report and keep the proof. Your customer file is read in your browser throughout.
Batch of Nov 20, 2026
43 days
to report 3,066 work items
30-day window from Jan 1, 2027 already applied
Download the batch
With an API key, CalDrop Compliance downloads the batch from DROP on schedule (Growth and Scale) or when you press the button. Without one, drop in the ZIP you downloaded from the portal.
The ZIP is stored exactly as received and encrypted, because DROP does not send a lost batch again. The report-by date is set from the day after download: 45 days, or 30 for any window that runs into 2027.
Where the law says so: Civ. Code § 1798.99.86(c); 11 CCR § 7613
20261120_9001_DROP.zipReport by Jan 4, 2027| Work item | List | People | Status |
|---|---|---|---|
WnDUKL8qatXV | 2 | 4 · Opted out | |
0PwrfHuon3KY | NDZ | 1 | 3 · Deleted |
k2RsoV7mQe1T | Phone | 1 | 2 · Exempted |
Xq9m6IHX1Zrm | Phone | 0 | 5 · Not found |
Match it against your file
Your customer file is opened by your browser and read in a background worker. Each value is standardized with DROP's published rules for its list, hashed with SHA-256 and compared with the batch.
A work item that matches one of your people is a deletion. One that matches several is an opt-out of sale and sharing. One that matches nobody is reported as not found.
Where the law says so: 11 CCR § 7613(a)(1); Civ. Code § 1798.99.86(c)(1)(B)
Email from your file
Standardized
DROP hash
OQhS9Ardy54oaPGAtHHvQxWjQGPxRUR9c/UfXlrR70c=
Act and confirm
Download the action list, which names your people by your own IDs, and delete them in your systems. Mark exempt records with their legal basis. Then confirm, and the confirmation is logged with who did it and when.
Nothing goes to DROP until someone with the owner or admin role confirms.
Where the law says so: Civ. Code § 1798.99.86(c)–(d)
WnDUKL8qatXVEmailKA18MT/ph6IH…pOQtkhE=
Matches in your file
cust_10442, cust_10871
Confirmed by you
- Opted out of sale in CRM
- Vendor notified
Report the statuses
CalDrop Compliance writes one Id,Status file per list under DROP's naming rules and sends them through the API, up to ten files per request. Or download them for the portal.
DROP's reply is stored with the batch. If it rejects a file, the reason is shown next to it so you can fix and resend.
Where the law says so: 11 CCR § 7614
Sent to DROP
20261120_9001_Email.csvAccepted20261120_9001_Phone.csvAccepted20261120_9001_NDZ.csvAccepted
Keep the proof, and keep them deleted
Every step is an entry in an append-only log in which each entry carries the hash of the one before. Export it with each batch's statuses as the evidence packet.
Every hash DROP has sent you joins your suppression list, so new records can be checked before they enter, in the app or through the screening API.
Where the law says so: Civ. Code § 1798.99.86(d), (e)(3)
Evidence log · chain intact
- #000410
batch.downloaded3 lists, 3,066 work itemsa41c…07e2 - #000411
batch.matched404 single, 2 multiple (browser)9f3a…c118 - #000412
batch.confirmeddeletions confirmed by M. Ortiz2be7…5d90 - #000413
drop.upload3 files accepted, 0 rejectede06d…41ab
Read next
Questions
Something else? Write to us and a person answers within one working day.
How long does a cycle take?
What if we miss the email reminder?
What if a batch has records we must keep?
Can two people work on the same batch?
Answer your next DROP batch on time
14-day trial on every plan. Run the practice batch first if you like.