Identifier Configuration

The DROP registry distributes separate lists for each identifier type. Before DataGrail can begin receiving and processing deletion requests, you need to select which DROP list types are relevant to your organization based on the personal information your systems hold.

Prerequisites

Before starting, ensure you have completed the Quickstart.

DROP List Selections

DataGrail subscribes to DROP registry lists on your behalf based on your selections. You must enable every list type that matches the personal information your organization holds — subscribing to a list means you will receive deletion requests for that identifier type and are responsible for processing them.

To configure your list selections:

1. Navigate to DROP Compliance in the left sidebar.
2. Select the List Selections tab.
3. Toggle on each identifier type that matches personal information held in your connected systems.
4. Select Save.

Supported Identifier Types

The following identifier types are available for DROP list selection:

Code	Identifier Type
NDZ	First Name + Last Name + DOB + ZIP
Email	Email address
Phone	Phone number
MAID	Mobile Advertising ID
NameVIN	First Name + Last Name + VIN
CTVID	Connected TV identifier

Select All Applicable Lists

You are required to subscribe to all list types that match the personal information you hold. Failing to subscribe to a relevant list type — and therefore not processing deletion requests for that identifier — may expose your organization to penalties under SB 362.

Ingesting Identifiers for Matching

Once your list selections are saved, your engineering team needs to deliver your consumer identifiers to DataGrail so they can be matched against incoming DROP registry requests. DataGrail recommends the pre-hashed ingestion path — you apply the DROP standardization and hashing rules to your identifiers before sending, and DataGrail stores and matches the hashes directly. This ensures raw PII never leaves your environment.

See Hashing Algorithm for the exact standardization and hashing rules, and Ingestion Format for file format and delivery specifications.

Clear identifier ingestion is available

DataGrail can also accept clear (unhashed) identifiers and handle standardization and hashing on your behalf — but this option requires prior discussion before implementation. Contact support@datagrail.io if you'd like to explore this path.

Next Steps

• Ingestion Format — deliver your consumer identifiers to DataGrail
• Testing & Validation — run test deletion requests to confirm your setup is working correctly before go-live