Independent California DROP readiness tool
Prepare to Process California DROP Deletion Requests
Answer a few questions about your data, systems, and workflows. Get a personalized DROP readiness assessment with clear implementation steps.
Free initial assessment · 7 questions · No login
Detailed assessment and implementation packages available from $195.
DROP processing is now live
Beginning August 1, 2026, California data brokers must access DROP at least once every 45 days to process deletion requests. The workflow can involve selecting and downloading relevant deletion lists, standardizing and hashing corresponding identifiers, matching records, taking required internal actions, reporting processing status, and maintaining an ongoing process for future records.
See official sources →What the assessment checks
Your DROP setup
Account status, registration stage, list selection, ownership, and processing approach.
Your data
Identifiers, systems, normalization, hashing, matching, and record relationships.
Your workflows
Deletion handling, opt-outs, status reporting, amendments, and recurring processing.
Your extended systems
Service providers, contractors, downstream data, and ongoing request handling.
Get a useful answer before you pay
Your result will be based on your answers — not a generic checklist.
Check your DROP readinessPreliminary finding
Your highest-priority area may be record matching.
You indicated that email and phone records are spread across multiple systems but do not currently use one standardized matching workflow.
Next step
Map which DROP list types correspond to each system before finalizing your processing workflow.
Go deeper when you need to implement
No subscription. One-time pricing.
Free
DROP Readiness Check
$0
- 7-question assessment
- Personalized preliminary result
- Top likely issue
- Immediate next step
- Relevant official resources
Detailed DROP Assessment
Understand your gaps and priorities.
$195 once
- Complete readiness analysis
- Category-by-category findings
- Prioritized action plan
- Candidate deletion-list review
- Workflow gaps
- Matching/hashing assessment
- Source-linked recommendations
- Questions for engineering
- Questions to verify with counsel
- Downloadable report
DROP Implementation Pack
Most completeTurn your assessment into an implementation plan.
$695 once
- Everything in the $195 assessment, plus:
- System and identifier mapping
- Tailored standardization/hashing specification
- Matching workflow design
- Manual vs. official DROP API recommendation
- First-cycle operating procedure
- Ongoing request-handling plan
- Service-provider action checklist
- Status/amendment workflow
- Engineering implementation backlog
- Recurring operating calendar
- Editable implementation tracker
DROP reference guide
Plain-language operational explanations of the DROP requirements data brokers ask about most, with official requirements kept separate from our recommendations.
- California DROP for Data BrokersDROP is California's centralized mechanism for consumers to submit a single deletion request that reaches registered data brokers. This page covers the operational shape of that obligation.
- How to Process DROP Deletion RequestsA single DROP processing cycle has a predictable shape. Getting it written down is what makes it repeatable across staff changes and 45-day cycles.
- The DROP 45-Day Access RequirementThe 45-day cadence turns DROP from a project into a recurring operating obligation. It is the single most useful constraint for planning your implementation.
- DROP Identifier Standardization and HashingMatching is only as good as standardization. Identical consumers produce different hashes when normalization rules differ, and the failure is silent.
- DROP Consumer Deletion ListsList selection should follow an identifier inventory, not the other way around. Choosing lists you cannot match wastes cycles; missing lists leaves requests unprocessed.
- DROP API vs. Manual ProcessingBoth approaches can work. The right choice depends on record volume, cycle frequency, system count, and how much manual handling your team can sustain every 45 days.
- DROP Suppression and Ongoing Request HandlingProcessing a request once is not the end state. Records acquired later that match a prior request generally require continued handling.
- DROP, Service Providers, and ContractorsYour internal processing can be correct while downstream copies remain untouched. Vendor handling is usually the least-mapped part of a DROP workflow.
- DROP Status Reporting and AmendmentsReporting is where a processing cycle becomes evidence. Outcome categories need consistent internal definitions before staff start applying them.
- DROP Registration and Access FeesRegistration and access are administrative gates with lead time. Sequencing them ahead of engineering work avoids a ready pipeline with no access.
- The California Delete Act and Data BrokersThe Delete Act is the statutory source of the DROP obligation. Understanding the structure helps separate legal requirements from implementation choices.