California DROP
The Delete Request and Opt-out Platform (DROP) (opens in a new tab) is operated by the California Privacy Protection Agency under the California Delete Act. Starting August 1, 2026, registered data brokers must download consumer deletion requests from DROP, process them against their consumer databases, and report the outcome of every request back to the platform.
The Astralis DROP integration is an erasure-only workflow that automates this entire obligation. Once configured, Astralis:
- Downloads the daily work-item lists (hashed consumer identifiers) from the DROP API.
- Matches each hash against an index of your consumer identifiers built inside your Snowflake warehouse — raw identity data never leaves your warehouse.
- Mints erasure privacy requests for matched consumers, which execute through your existing privacy request infrastructure and connected integrations.
- Records every decision in an authoritative suppression ledger with full change history.
- Uploads a response CSV to DROP reporting the status of every work item, tracking the 45-day deletion SLA.
How it works
Each DROP work item is a hashed consumer identifier (SHA-256, Base64-encoded) belonging to one of six list types:
| List type | Identifiers hashed |
|---|---|
Email | Email address |
Phone | Phone number |
MAID | Mobile advertising ID |
CTVID | Connected-TV ID |
NDZ | First name + last name + date of birth + ZIP code |
NameVIN | First name + last name + vehicle identification number |
Astralis normalizes and hashes your own consumer identifiers with the same recipe (inside your warehouse), then joins the downloaded hashes against that index. Each work item resolves to one of four DROP status codes:
| Status | Meaning | What Astralis does |
|---|---|---|
2 Exempted | The matched consumer is flagged exempt (e.g., CCPA-exempt) | Reported to DROP immediately; no deletion |
3 Deleted | Exactly one non-exempt consumer matched | An erasure privacy request is minted; the status is reported to DROP only after the erasure completes |
4 Opted out | The hash matched multiple consumers (2 or more) | Reported immediately using DROP's official ambiguous-match status; no individual erasure request is created |
5 Not found | No consumer matched | Reported to DROP immediately |
Components
The integration is made up of five cooperating pieces, each documented in its own guide:
- Setup — create the DROP integration, provide the API key, and choose list types, policy, and environment.
- Match index & backfill — build and refresh the in-warehouse identifier index with a gather query you author.
- Suppression cycles — the daily download → match → mint → report loop, including erasure request minting, completion tracking, and the 45-day SLA.
- Create erasures via API — submit DROP-sourced erasure requests directly, for organizations that process their own DROP work items outside Astralis.
- Operations & audit — the append-only audit log, the suppression feed API for downstream systems, manual controls, and troubleshooting.
Environments
The integration connects to DROP's production API by default. You can select an environment when configuring the integration:
| Environment | Base URL |
|---|---|
Production (default) | https://api.drop.privacy.ca.gov |
Sandbox | https://api.drop.privacy.ca.gov/sandbox |