Check operational readiness for California DROP

Record the supported account, access, deletion, identifier and service-provider controls after data-broker coverage has been confirmed.

USData protection and privacy
$29.99verified launch price. Checkout closedAbout 10 minutes6 working filesStart this tool

Launch price verified. Checkout remains closed until the final payment and recovery tests pass. Entries and files stay in this browser. Sources reviewed 31 July 2026.

Inspect a real output

Built from fictional sample information using the same exporter as the tool.

California DROP readiness report sample

What’s included

Orient the programme

Keep the supported scope, sequence and review boundary with the readiness work.

  • Start Here PDF
  • Sources and assumptions record

Review readiness

Inspect each supported control and the evidence recorded for its current state.

  • Readiness report PDF
  • Evidence register CSV

Manage actions

Retain owners, due dates and structured control responses for follow-up.

  • Control and action register XLSX
  • Structured readiness record JSON
View every output and format
  • Start Here PDF
  • Readiness report PDF
  • Evidence register CSV
  • Control and action register XLSX
  • Structured readiness record JSON
  • Sources and assumptions record

Who this tool is for

Privacy, operations and technical teams preparing internal DROP readiness evidence. Turn confirmed operating facts into a visible readiness record with owners, evidence, tests and follow-up actions.

Supported use

  • An organisation whose California data-broker status has already been decided by a responsible person
  • Supported account, access, deletion, identifier, suppression and service-provider controls
  • A readiness report, evidence register, action register and structured record

Have ready

  • Organisation, owner, reference and the recorded data-broker status
  • Account and operating status, access method and relevant operational dates
  • Status, owner, evidence, test result, action and due date for each supported control

Needs separate review

  • Whether the organisation is a data broker or must register
  • Submission of information or deletion requests to DROP or another regulator
  • Consumer identifiers, production deletion execution or controls outside the supported readiness fields

How it works

  1. Record the operating routeConfirm the recorded broker status, organisation, owner and account or access position.
  2. Assess each controlRecord the current status, exact evidence, owner and most recent test for each routed readiness subject.
  3. Assign the gapsAdd a follow-up action and due date wherever the evidence is missing, uncertain or incomplete.
  4. Export the readiness recordDownload the report, evidence register, action workbook, structured record and source manifest.

Where does this task apply?

Choose the guidance set this tool should use. The interface and outputs stay in English.

Available guidance sets

Using California, United States guidance.

Build a defensible California DROP readiness record

Record the account, retrieval, matching, deletion and reporting controls a reviewer should be able to inspect before live processing.

No consumer information is needed

Do not enter identifiers or deletion-list content. Answers and evidence references remain in this browser.

Set the assessment scope

Use the organisation’s documented coverage decision. This tool records that decision but does not make it.

Record the implementation evidence

Choose the current state and name the exact policy, test, ticket or record a reviewer should inspect.

Confirm the organisation’s California data broker status first. If coverage is not confirmed, the report will fail closed and record why no readiness assessment was made.

No consumer identifiers or deletion-list content should be entered.

Processing under the final regulations begins on 1 August 2026. The date prompts are based only on the recorded facts and must be checked against the live DROP account.

This tool does not determine coverage, connect to DROP, process deletion requests or verify that a named control operated.

What this tool checks

The scope stays narrow so the result is clear and reproducible.

  • Checks account, access, deletion-list selection and retrieval-cadence evidence after coverage is confirmed.
  • Checks supported identifier standardisation, hashing, deletion, suppression and service-provider records.
  • Reports missing and uncertain readiness evidence without processing consumer identifiers or connecting to DROP.

From official material to a working record

Official material sets the basis

Official California material describes the operational duties and processes relevant to DROP.

The tool prepares the operational record

The preflight converts recorded operating facts into a control-by-control evidence and action record without connecting to DROP.

Official sources stay visible

Each supported check shows its jurisdiction, source title, source version and review date beside the result. Unsupported cases are rejected rather than estimated.

View this product's official sources

Questions before you use the tool

Scope, files, evidence and browser-local handling.

Does the preflight decide whether we are a data broker?

No. The organisation records that decision before the routed readiness check begins.

Does the tool connect to DROP?

No. It does not submit information, retrieve deletion lists or process consumer identifiers.

Where are readiness details processed?

The control responses, evidence references and generated files remain in this browser.

What does the evidence pack contain?

It contains a Start Here PDF, readiness report, evidence register, action workbook, structured record and sources and assumptions record.

Check the DROP readiness record

Record the operating route, evidence and owners, then review every unresolved control before export.

Open the DROP preflight