> ## Content Index
> Fetch the complete content index at: https://akribos.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# Deleting your data should not be a second job
- URL: https://akribos.tech/drop-deletion-should-not-be-a-second-job/
- Published: 2026-10-30T06:08:37.000Z
- Updated: 2026-10-30T12:38:24.000Z
- Description: California’s DROP system puts the burden of coordinating deletion closer to where it belongs.
- Author: Noah Nelson
- Tags: Privacy, Commentary

A privacy right that requires a person to discover every company holding their information comes with a built-in obstacle. The person least able to see the market is expected to navigate it.

California’s [Delete Request and Opt-out Platform, or DROP](https://privacy.ca.gov/drop/how-drop-works/?ref=akribos.tech), gives eligible California residents a central way to submit deletion requests to registered data brokers. The state says brokers began processing requests in August 2026 and must do so at least every 45 days. It is not an instantaneous eraser for every copy of personal information everywhere.

The interesting policy change is the allocation of work. A shared process recognizes that ordinary people cannot reasonably manage a separate relationship with each broker they have never chosen to use.

## Completion needs a receipt

Submitting a request is the beginning of the transaction. The experience should make clear whether a broker found a match, processed the request, or reported some other outcome. A person should not have to infer success from a button becoming unavailable.

There is also a difficult design tension in matching records. More identifying information may improve the chance of finding a record, but asking people to provide more data in order to reduce data collection deserves careful explanation. The interface should describe why each field helps and what happens to it.

Those are questions for testing, not reasons to dismiss the idea. A centralized mechanism can make a previously exhausting process manageable while still requiring oversight.

## Finding a record is different from proving its absence

A deletion service must connect the person making a request with records held under identifiers that may differ from the information that person normally uses. An email address, a device identifier, and a vehicle identifier are not the same kind of clue. A broker may have one without another.

The [state’s DROP help page](https://privacy.ca.gov/drop/help-with-drop/?ref=akribos.tech) explains that additional identifiers can improve matching but are not all required. It also says a “record not found” response means the broker could not match the information supplied. That is an important limitation: a failed match is not proof that the broker never held information about the person.

This is a communications problem as much as a database problem. Status language should describe the operation performed and its result. “We could not match this request” is narrower and more useful than a vague reassurance that everything is handled. People should be able to distinguish a completed deletion from an unresolved identity match.

## Collect enough to act, then explain the handling

A platform that coordinates deletion has to handle identifying information itself. That requirement deserves examination without pretending the task can be accomplished with no information at all. The relevant questions concern necessity, access, retention, and how the matching process is separated from unrelated uses.

The state says the information used to verify California residency is not shared with DROP. That is a specific architectural claim a reviewer can examine. It should not become a general declaration that every privacy concern around the service is settled.

For the person completing the form, optional fields should remain visibly optional. The interface should explain the likely benefit of providing another identifier and let the person proceed without feeling that an incomplete profile makes the entire request worthless. A system can communicate uncertainty without making the user do the system designer’s work.

## Deletion is not the same as erasing the internet

A broker-focused mechanism has a defined scope. It does not automatically remove information from every organization with which a person has a direct relationship, every public record, or every copy held outside the covered process. Presenting it as a universal eraser would create expectations no narrowly scoped service could satisfy.

That limitation does not make the mechanism trivial. Reducing the need to approach many registered brokers separately can materially improve the ability to exercise a right. The appropriate comparison is the work required before and after the shared process, not an impossible promise of total disappearance.

A careful review would follow actual request outcomes over time, using consenting participants and protecting their identifiers. It would record how statuses change, where matching fails, and whether people understand the result. It would not submit someone else’s information merely to make a compelling demonstration.

## Measure the burden after submission

The work can return in less visible forms: recovering an account, interpreting an exception, or correcting information that prevents a match. A good public service should expose those routes clearly and provide help that does not assume technical confidence.

Accessibility belongs in that evaluation. A deletion right should remain usable for someone who relies on assistive technology, shares a computer, or cannot spend a weekday navigating support. These are ordinary conditions of public use. If a privacy mechanism depends on spare time and specialized knowledge, the people who most need it can end up with the weakest practical access.

## Privacy that fits an ordinary life

The person using a deletion service may be dealing with a move, harassment, or a parent’s affairs. They may simply want fewer businesses trading information about them. None should need a specialist’s understanding of the advertising industry to begin.

The measure of a privacy tool is whether a person can exercise the right and understand the result. The existence of a form is only the first part.

## Sources

- [California privacy agency: how DROP works](https://privacy.ca.gov/drop/how-drop-works/?ref=akribos.tech)
- [state’s DROP help page](https://privacy.ca.gov/drop/help-with-drop/?ref=akribos.tech)