You found your email in a data broker record, but worry that a deletion request could expose it again.
Fast answer: California DROP lets eligible residents ask participating data brokers to delete matched, non-exempt personal information. It does not automatically delete an email address you gave directly to a merchant, erase every copy online, or make the request anonymous.
This guide is for California residents deciding whether DROP covers a particular email record, people checking a request that did not match, and anyone weighing the privacy implications of submitting identifiers.
Last updated October 23, 2026. We checked the official DROP overview, the state’s explanation of how DROP works, and the current DROP regulations. Check those official pages again before acting; the live instructions and processing rules control if they change.
Start by identifying who holds the email
California DROP is a state platform for California residents to submit deletion requests to data brokers. It is not a universal account-deletion form for every organization that has an email address. The request is directed at participating data brokers covered by the program, rather than every website, retailer, app, or email provider.
That distinction matters because the same address can sit in separate systems for different reasons. A broker may have collected it from another source or from activity that did not involve a direct relationship with you. A shop may have it because you entered it at checkout. Your email provider has it because it operates your mailbox. One DROP request does not automatically reach all three.
The official DROP overview describes the platform as a way for California residents to request deletion from data brokers. The state’s separate explanation of personal information and data brokers helps clarify whether the holder and type of information fit the program. Do not treat a company as covered just because it has your email or uses data in a way that feels like brokering.
Does DROP delete an email address you gave directly to a merchant? Not automatically. The official guidance distinguishes information a business gets directly from a consumer in its own interaction from information a data broker collects or holds under the program. A retailer’s signup list, purchase account, or newsletter database can therefore fall outside the deletion request’s reach when the retailer collected that address directly from you.
If the concern is a merchant account, use that company’s own privacy request or account settings. DROP may still be relevant to separate broker records about you, but it does not replace a direct request to the merchant.
Compare the records before choosing a route
Use the source of the record—not simply the fact that it contains an email address—to decide where to start.
| Record you want removed | Likely first route | What DROP means |
|---|---|---|
| Information held by a covered data broker and matched to you | Submit a request through DROP and review its status | It can request deletion of matched, non-exempt personal information held by the broker |
| Email you entered directly on a shop, app, or newsletter form | Contact that business or use its privacy controls | A DROP request does not automatically delete the merchant’s first-party customer record |
| Mailbox account or messages stored by your email provider | Use the provider’s account, retention, or deletion controls | DROP is not a mailbox-closure tool |
| A copy held by another organization or obtained from another source | Identify that holder and its relationship to the data | A deletion at one broker does not establish that every other copy is gone |
This is a routing guide, not a legal ruling about a specific company. The state’s description of personal information and data brokers is the better reference when the holder’s role is unclear.
A practical way to reason about a record is to separate who collected it, why it is held, and which organization controls it. An email shown in a broker’s profile does not prove that the broker was the original collector. Nor does the existence of a broker record prove that a merchant will remove its own customer record when the broker acts.
Treat matching as a separate checkpoint
Submitting a request does not establish that a broker has found a record. A broker must compare the information provided through DROP against its own records. Whether it can make a match depends on the identifiers available to the platform and the records the broker maintains. The official explanation of DROP’s matching process describes matching as part of the process; it does not promise that every record will match.
What does a result with no matched record mean? It means the request did not produce a confirmed match under the process shown in the platform. It does not prove that the broker has no information about you. The broker’s record could use different details, contain incomplete or outdated information, or fail to line up with the identifiers available for comparison. Treat “not matched” as an unresolved result, not as evidence that the data is absent.
The official process allows users to update their information in order to support matching, subject to the fields and instructions available in the current platform. Before adding details, check that you are using the official DROP service and review what the form asks for. Add only information you are comfortable submitting for the stated purpose; more identifiers can help distinguish records, but they also increase the amount of personal information you provide to the platform.
A helpful milestone view is:
- Request submitted: the platform has received a request; this alone does not confirm that a broker has located a record.
- Matching underway or reported: the broker’s records are being compared with the request information, according to the current status shown in DROP.
- Deletion reported: the relevant process indicates that matched, eligible information was handled. This should not be read as confirmation that all other copies or sources have been erased.
Use the platform’s current status descriptions rather than assuming that a label means more than it says. The official processing guidance for data brokers explains the broker’s role and the current process. If a status is unclear, compare its exact wording with the platform’s live explanation instead of guessing from the label.
Check what deletion covers—and what it does not
A successful match is not the same as deletion of every record connected to an email. The request concerns personal information held by a covered data broker that is within the program’s scope and not subject to an applicable exception. The official DROP regulations and current program guidance define that boundary.
Do not interpret a deletion result as any of the following:
- Closure of the email account itself.
- Deletion of messages in your inbox.
- Removal of a merchant’s directly collected customer record.
- Erasure of copies held by organizations outside the request’s reach.
- A guarantee that information will never be collected again.
The boundary is important even when a request succeeds. If one broker deletes matched data, another organization may hold similar information for a different reason or under a different relationship. The record may also have originated with a direct interaction that DROP does not automatically undo.
Does DROP remove every email record held by websites and data brokers? No. It is a broker-directed deletion mechanism, not a single command to every website that has ever received an address. Each holder and each source must be considered separately. A business that received your address directly may require a separate request, and other copies may have their own applicable rules.
The processing period also should not be treated as immediate. The DROP regulations set a 45-day access cadence for data brokers using the platform. That cadence is a process parameter, not a promise that every individual record will be matched or erased within a particular number of days from the moment you submit a request. Follow the status shown in the official platform and avoid inferring a final outcome from elapsed time alone.
The important measurable distinction is between the platform’s schedule for broker participation and the result for an individual request. One is a general process rule; the other depends on a match, the data held, and whether the information is eligible for deletion. Keep those questions separate when you assess whether your email privacy concern has been resolved.
Review the information you submit to DROP
Do you need to provide an email address, and how is it handled? Follow the fields displayed in the official DROP form and the platform’s current privacy and process explanations. The information requested supports identity matching; it is not the same dataset as the information a data broker already holds about you. Those are two separate flows: information submitted to the state platform to make a request, and information a broker compares against its own records.
That distinction helps you evaluate risk without assuming either perfect privacy or automatic exposure. The platform’s descriptions of data conversion, storage, and transfer explain its stated technical and operational safeguards. They do not make the process zero-risk, and they do not mean you are using an anonymous lookup tool. Read the official explanation of how DROP works together with the fields and notices shown when you submit.
Before you proceed, check the request against this list:
- [ ] Confirm that you are a California resident and are using the official DROP platform.
- [ ] Identify the organization holding the record; separate a data broker from a merchant or email provider.
- [ ] Work out whether the address came from a direct signup, purchase, or subscription, or from another collection route.
- [ ] Read the current form and privacy notice so you know which identifiers you are being asked to submit.
- [ ] Submit only information needed for the request and matching process described by the platform.
- [ ] Save the request reference or status details the platform provides, then use its current status explanations when checking progress.
- [ ] If the result is not matched, review whether the platform allows an update and whether you are comfortable supplying additional identifiers.
- [ ] Contact a merchant separately if the record you want removed is in its direct customer database.
This checklist is deliberately about decisions, not a promise of outcome. A platform can process the information needed to compare a request, but the result still depends on whether the relevant broker has a matching record and whether the information is covered.
Privacy boundary: A deletion request and an anonymous search are different things. DROP needs enough information to associate a request with a person; check its current disclosures before submitting, and do not assume that using it hides your identity from the platform.
Keep deletion rights separate from future email isolation
DROP addresses a past or existing data-broker record. Email isolation addresses a different point in time: whether a low-trust site receives your primary address when you register in the future. Neither approach substitutes for the other. A new address does not retract data already collected, and a deletion request does not prevent a new site from collecting an address you provide later.
If you are deciding between a temporary address and a reusable alias, compare how long you need access, whether you may need password recovery, and whether you expect to reply to messages. Our guide to choosing between a disposable address and a longer-term option explains that decision by use case. For broader privacy controls, our data practices overview is a separate reference; neither guide changes DROP’s legal scope.
For bank, payment, government, healthcare, or other important accounts, keep an email address you can control over the long term. Those accounts may need future security alerts, account recovery, or ongoing correspondence. A short-lived inbox is a poor fit if losing access could lock you out or prevent you from receiving an important notice.
For a one-time registration or a low-trust site that only needs a message or verification code, an isolated temporary inbox can help avoid exposing your primary address to that new service. It will not remove an address from a broker’s existing records or make your identity anonymous. If that is the narrow problem you are solving, Inboxtmp can be considered as a separate email-isolation option—not as part of California DROP and not as a substitute for a deletion request.