What you would build
- Standardization for six lists. Email, phone, name with date of birth and ZIP, name with VIN, mobile ad IDs and connected-TV IDs, each with its own rules, plus composite values joined before hashing.
- Hashing that matches DROP exactly. SHA-256, Base64-encoded, tested against every worked example in the documentation. One wrong rule and nothing matches, silently.
- Batch handling. Download through the API or the portal, keep the ZIP because it is not sent again, parse each list and the removed-request file.
- Status logic. One match deletes (3), several matches opt out (4), exempt records need a basis (2), the rest are not found (5).
- Response files. Id,Status CSVs named the way DROP expects, at most ten files and 100 MB per request, with DROP's errors handled.
- Deadlines. The clock from the day after download, the switch from 45 to 30 days on 1 January 2027, and reminders.
- Records. A log of every step that an auditor can trust, kept six years.
- A suppression list to keep DROP consumers deleted between batches.
What you would run
The code is the smaller part. Someone has to download every batch, watch the dates, confirm the deletions and answer DROP's errors, every cycle, with a backup person for holidays. When DROP changes its documentation, the code has to change with it. The change log shows how often that has happened in 2026.
When each makes sense
| Build | Buy | |
|---|---|---|
| You already run data pipelines | Good fit | Still saves the upkeep |
| Nobody owns compliance engineering | Risky | Good fit |
| You need deletion across many systems | Build it into your pipeline | An enterprise platform, not a DROP-only tool |
| You want to start this cycle | Unlikely | Same day |
Either way, the hash checker and response file checker are free to use against your own build. CalDrop Compliance costs $99 to $499 a month; see pricing.
Questions
How long does it take to build a DROP processor?
For an engineer who knows your data, a first version is a matter of weeks: the hashing and status rules are well documented. Testing every list against DROP's examples, handling errors and building the records an auditor wants takes longer than the matching itself.
Is there open-source code for DROP?
We found no maintained open-source DROP processor as of November 2026. DROP's own documentation includes worked hashing examples to test against.
Can we build matching and buy the rest?
Yes. Our screening API and evidence log work with hashes you make yourself, provided you follow DROP's standardization rules.
Related
Sources
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).
