DROP Matched
Menu

The California Delete Act · broker duties begin August 1, 2026

California’s Delete Act creates a centralized deletion-request workflow for registered data brokers. DROP Matched turns each official DROP batch into a process your team can run.

From August 1, 2026, registered brokers must regularly access official DROP deletion requests and report their responses on the applicable clocks. DROP Matched takes that request list and your customer file, matches them privately in your browser, and builds the response files your operator sends back to the state.

Your customer rows and the state’s identifiers stay in your browser — never sent to DROP Matched. Your team keeps every legal decision, every change to your own systems, and your official state account. Workflow software—not legal advice, and not a guarantee of compliance.

What runs through one batch
California sends The delete list the people who asked
You provide Your customer export the records you hold
In your browser Match · review · prepare

The comparison runs on your own machine, and every stage stays visible.

Your operator sends back Response files + a dated record answers for the state

Upload-ready answers, the deadlines still open, and a record of the batch.

What the law requires

Once the request lands, the work is yours.

DROP — California’s Delete Request and Opt-out Platform — is the state website where a resident files one request for covered registered data brokers to process. The required result can be deletion or an opt-out, subject to the statute’s verification, purpose, and exception rules. The state hands you the list; it doesn’t do the work inside your company.

DROP Matched sits between the state’s list and the answer you send back — it does the matching; your team does the rest.

  1. The request

    One request reaches every registered broker

    A resident files once on DROP. The request reaches the registered data brokers covered by the state workflow and stays active going forward, so new requests keep arriving. Registry counts change; your own registration and DROP account control which requests you must process.

  2. The clock

    A rolling 45-day clock, from Aug 1, 2026

    Starting August 1, 2026, each broker must access DROP on its own rolling clock — at least once every 45 days from its last download — act on each request, and report the outcome. It is not one shared calendar; every broker runs its own.

  3. The stakes

    $200 per request, per day

    California law authorizes an administrative fine of $200 for each deletion request for each day a broker fails to delete information as required by the DROP statute, plus reasonable enforcement expenses. Exceptions and the facts of a request still matter.

The request file is where your work starts, not where it ends.

How it works

Four steps. One controlled batch.

DROP Matched runs the repeatable steps. Your team keeps the credentials, the customer records, the legal calls, and anything that changes inside your own systems.

  1. Retrieve

    Pull the official list

    Your authorized operator — the person on your team who holds your state-account login — signs into your own DROP account and downloads the request lists. DROP Matched checks the batch (broker ID, file types, request IDs, hashes) before any work starts.

    retrieve → validate
  2. Match

    Compare it to your records, in your browser

    Load an approved export of your customer data. DROP Matched standardizes, hashes, and matches the identifiers on your own machine.

    map → hash → match locally
  3. Act

    Do the real work in your systems

    Your team reviews each match and completes the deletion, opt-out, or exemption where the data actually lives, then records what was done.

    human decision + source action
  4. Respond

    Send the answers back and keep the record

    DROP Matched builds the response files. Your operator uploads them through the state’s workflow, confirms the CPPA shows them accepted or processed, and keeps a dated record of the batch.

    respond → confirm → receipt

Where your data stays

An operations tool—not another copy of your customer database.

Your customer export and the state’s request lists are read by software running in your browser. Those rows are never uploaded to DROP Matched’s server.

The account keeps only operational metadata — dates, totals, attestations, and a report fingerprint — so you can review a past batch without storing the records themselves. DROP Matched never deletes customer data for you: it finds the matches and prepares the files, and your team completes the action where the data lives.

The batch record binds the dates, totals, and your operator’s attestations. It does not independently verify the underlying work or that the state processed it.

See the exact data boundary

Stays in your browser

  • Customer CSV rows
  • The state’s request rows
  • Matched record details
  • Generated worklists and responses
browser boundary

Inspect before promises

See how it behaves before you talk to anyone.

The public sample uses generated records and aggregate counts. No customer file or sales call required.

Live sample workflow generated .test records Response example Id,Status · CSV Service status public health surface

It automates the checks. Your team keeps the judgment.

Once your operator supplies the inputs, DROP Matched runs the deterministic checks and makes every human-controlled step explicit.

What DROP Matched checks

  • Batch validationRejects unsupported file types, malformed IDs or hashes, and mixed-broker batches, and asks your operator to attest the export covers the right sources.
  • Response coverageConfirms every active work item has an allowed status and the totals agree before anything is exported.
  • DeadlinesSurfaces the access, response, and amendment dates on each batch’s own clock, and flags what needs review.
  • Spec and service healthFlags official specification changes, failed self-tests, stale backups, or service problems instead of guessing.

What your team keeps

  • Signing into the state’s DROP account and pulling the lists.
  • Confirming your export covers the right systems and records.
  • Every legal decision, deletion, opt-out, and system change.
  • Uploading the responses and confirming the state accepted them.

DROP Matched is not legal counsel, a remote agent into your systems, a holder of your state credentials, or a compliance guarantee. It prepares the batch; it doesn’t decide the law or touch systems it can’t see.

Hosted v1: one operator account and one managed Chromium-based desktop browser profile, bound to one verified California broker registration. Multi-user, system-to-system, and segmented-source workflows are outside this offer.

Founding pilot

Prove one real cycle before billing starts.

The founding pilot is a supervised, one-broker deployment for a verified company and one authorized operator. Creating an account starts evaluation only; it does not grant production access, accept a contract, or create a charge.

  • Customer rows, official DROP files, response files, and credentials stay with your operator.
  • Your team makes the legal decisions and completes actions in its own systems.
  • Production access requires broker verification and signed customer terms.

Founding offer · August 18, 2026

$0through supervised setup and the first production DROP Matched batch accepted or processed by official DROP
Then$2,388/year

The billing gate closes only after every response file generated for the first production DROP Matched batch is accepted or processed by the official DROP workflow, your operator verifies that result, and Seaside records a non-row-level evidence reference and hash. Sandbox or partial-batch acceptance never opens billing. No card is required before that Success Gate.

Enrollment is private, not self-serve. Scope, term, renewal, payment, support, and legal terms are controlled by the signed order and customer agreement.

See the buyer checklist

See if it fits

Bring one real batch. We’ll walk it through.

Tell us how your team pulls the lists, where your customer records live, and who does the work. We’ll confirm whether the browser-local model fits and run a representative batch with you. Don’t send customer records, DROP files, or credentials — the review doesn’t need them.

Private founding-pilot intake is open. General self-service is not. Account creation begins evaluation; production access follows broker verification and signed terms.

Log in

Access your DROP operations workspace.