Why you need one
After you delete a consumer under a DROP request, Civil Code §1798.99.86(d) requires you to keep deleting their personal information at least every 45 days, and not to sell or share new personal information about them. Data brokers buy and refresh data constantly, so the same person will come back in next month's feed. A suppression list is how you catch them.
AB 883 shortens DROP access to every 30 days from 1 January 2027. Whether the re-deletion interval in §1798.99.86(d) also moves to 30 days is not clear from the sources we have read; deleting on every 30-day cycle meets either reading.
Step by step
- Record each confirmed deletion. For every work item reported 3 (Deleted), 2 (Exempted) or 4 (Opted out), keep the work item ID, the list and the hashed identifier DROP sent.
- Keep only what you need. 11 CCR §7613(b)(1)(B) lets you keep the minimum personal information necessary to make sure the consumer stays deleted, until they amend or cancel their DROP request. The DROP hash is usually enough.
- Screen new data before you use it. Standardize and hash each new record the way DROP does, and compare it with the list before you sell, share or append it.
- Re-delete matches. If a new record matches, delete it (or never ingest it) and do not sell it.
- Re-run on every cycle. Compare your whole database against the list at least every 45 days, and every 30 days once AB 883 applies.
- Log it. Keep a record of each screening run; auditors are expected to test suppression. See Delete Act audits.
Unmatched requests count too
A request you reported as 5 (Not found) still matters. Under 11 CCR §7613(c), you save the deletion list and compare newly collected records against it before you sell or share them. If someone you had no data on turns up in a feed later, you must not sell their data. CalPrivacy's proposed rules of 13 November 2026 would formally define the “suppression list” and say that a match found before the data is taken in needs no status change; those rules are not final.
Removals and status changes
- When a consumer amends or cancels their request, the work item appears in a Removed CSV in a later batch. Delete that entry from your suppression list.
- If you later find a consumer you reported as 5 (Not found) and delete them, report the new status (for example 3) at your next access session through DROP's amend endpoint (11 CCR §7614(a)(1)).
Retention and minimisation rules
| Rule | What it requires |
|---|---|
| 11 CCR §7613(b)(1)(B) | Keep only the minimum personal information needed to keep each DROP consumer deleted, until they amend or cancel |
| 11 CCR §7613(c) | For unmatched requests, keep the deletion list and screen new records before sale or sharing |
| 11 CCR §7616(a) | Never sell or share data you received from DROP |
| 11 CCR §7616(b) | Protect DROP data with reasonable security |
| 11 CCR §7616(c) | Do not contact the consumer to verify their request |
| 11 CCR §7613(e) | Share only the minimum personal information service providers need to suppress |
Your suppression list is itself DROP data: it may not be sold, shared or used for anything except keeping consumers deleted. Keep it separate from marketing systems.
If you stop being a data broker
A business that stops being a data broker must delete the DROP data it holds within 30 days after its final registration or audit (11 CCR §7615(a)(2)).
Questions
What is a DROP suppression list?
A record of consumers who made DROP deletion requests, kept so a data broker can stop their data coming back and never sell new data about them.
What can a suppression list contain?
Only the minimum personal information needed to keep the consumer deleted, under 11 CCR §7613(b)(1)(B). The hashed identifier from DROP is usually enough.
Do I suppress consumers I could not find?
Yes. Under 11 CCR §7613(c) you keep the deletion list and screen new records against it before any sale or sharing.
When do I remove someone from the suppression list?
When their work item appears in a Removed CSV because they amended or cancelled their DROP request.
Related
Sources
- Civil Code §1798.99.86
- Data broker regulations, 11 CCR §§7613–7616 (CalPrivacy PDF)
- CalPrivacy: processing DROP requests
- CalPrivacy: DROP technical reference
- Proposed data broker and DROP audit regulations, 13 November 2026 (PDF)
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).
