Identity Verification on California's DROP Platform: What It Checks

On California’s DROP platform, identity verification is primarily a California-residency eligibility check completed before submission. It is separate from later broker record matching: the Agency verifies eligibility, while brokers compare hashed identifiers and may not contact consumers to reverify requests.

The governing final DROP regulations use the more precise phrase “California residency verified.” CalPrivacy’s consumer instructions describe the technology as identity verification because the California Identity Gateway uses personal information or Login.gov to establish eligibility. Both descriptions refer to the entry check, not a promise that every identifier in the later deletion request belongs to one uniquely identified person.

What identity verification means in DROP

The DELETE Act is the California law enacted through SB 362. DROP is the Data broker Requests and Opt-out Platform built to carry out the law’s centralized deletion mechanism. The law calls for a single verifiable consumer request; the regulations specify how residency verification, request submission, identifier matching, and status reporting operate within that system. The California DELETE Act overview provides the broader legislative context.

“Verification” can describe several different operations. Treating them as one check creates false expectations about what DROP has established.

The first row controls access to the platform. The third controls what a particular broker can do with the request. A company is a covered data broker only when the statutory definition and exclusions apply; DROP is not a request channel for every business that has information about a California resident.

How the California residency check works

The check comes before submission

Section 7620 of the effective regulations requires the Agency to verify California residency before a consumer submits a DROP deletion request. If the Agency cannot verify residency, the request cannot be submitted at that point. This is an eligibility gate, not an optional broker-by-broker preference.

For this purpose, section 7622 points to the definition of resident in California Code of Regulations, title 18, section 17014, as that provision read on September 1, 2017. That official regulation includes a person present in California for other than a temporary or transitory purpose and a person domiciled in California but outside the state for a temporary or transitory purpose. Residency can therefore involve more than a current mailing address.

Two verification routes are presented

CalPrivacy’s current DROP workflow presents two routes: enter basic personal information through the California Identity Gateway, or sign in through Login.gov. A California Identity Gateway account is not required. The Agency recommends the Login.gov route when the consumer already has an account, rather than saying that every DROP user must create one.

The California Department of Technology describes the Identity Gateway as an intermediary connecting state services with identity and eligibility providers. In DROP, its relevant output is an eligibility result that allows the consumer to return to the request flow. The public instructions do not provide a universal list of documents that every consumer must upload through the basic-information route, so a guide should not invent one.

Creating a new Login.gov account is a separate process. CalPrivacy’s DROP help page cautions that account creation may require photos of identification or other documents for identity proofing. That possibility comes from the Login.gov route; it is not a statement that DROP itself always demands a driver’s license, selfie, Social Security number, or document upload.

Residency data and deletion-request data are different

CalPrivacy states that information entered for the residency check is not shared with DROP. After verification, the consumer returns to DROP and creates the deletion request. The official workflow lists name, date of birth, and ZIP code as the minimum request-profile fields, with categories such as email addresses, phone numbers, mobile advertising identifiers, connected-TV identifiers, and vehicle identification numbers available as additional matching inputs.

This distinction matters for data minimization. Verification information supplied to the gateway serves the eligibility decision. Information entered into the DROP profile serves broker matching. The Agency’s DROP notice at collection says DROP collects the profile information a consumer enters as well as specified usage and device information, and identifies the purposes for that collection. A consumer should read the current notice shown by the official service before submitting because operational notices can be updated.

The regulations also state that the Agency may verify personal information added to a deletion request at any time. They do not say that every optional profile field is verified before submission. Accordingly, an accepted request should not be interpreted as state certification that every email address, phone number, device identifier, or vehicle identifier is accurate.

What to do if residency cannot be verified

Start by checking the information for transcription or formatting errors and retrying through the official service. CalPrivacy gives that advice for both the personal-information and Login.gov routes on its help page.

If DROP reports that it is unable to verify California residency, the regulations provide a review procedure. Under section 7622, the consumer may request review through DROP within 10 calendar days of the classification. The submission must explain how the consumer meets the referenced California residency definition and provide an email address or phone number for the Agency’s response. The Agency may request substantiating documentation case by case and must give written notice when the submitted information demonstrates residency.

The rule does not supply a fixed list of acceptable review documents or promise that every review will succeed. Do not send unrequested sensitive documents through a general contact channel. Follow the fields and secure upload instructions displayed in the official DROP review flow, and use CalPrivacy’s official contact route if the review control is unavailable.

Why broker matching is not a second identity check

Once a request enters DROP, brokers receive consumer deletion lists containing identifiers in hashed form. The regulations’ processing rules direct brokers to standardize comparable data in their own records, hash it with the specified method, and compare the results. This is record matching. It does not authorize a broker to ask the consumer for identity documents or conduct a separate residency review.

The distinction is explicit: section 7616 prohibits a data broker from contacting a consumer to verify a deletion request submitted through DROP. If one identifier maps to multiple consumers in the broker’s records, the prescribed result is an opt-out of sale or sharing for the associated consumers rather than deletion based on an ambiguous match. A broker may also report that a record was deleted, exempted, or not found under the defined status rules.

A “record not found” result therefore does not reverse the Agency’s residency decision. It means the broker did not find a match after applying the required comparison process. Similarly, an opt-out caused by an ambiguous identifier does not mean the person failed the initial identity or residency check. It reflects uncertainty inside the broker’s dataset.

DROP submissions are a specialized form of consumer request. They should not be confused with a direct CCPA request to a specific business, where verification rules can differ with the right, account relationship, and sensitivity of the requested disclosure. The broader California privacy-law guide explains those direct rights separately.

Practical verification checklist

Before and during the eligibility stage:

1. Start only from the official privacy.ca.gov DROP pages and confirm the destination remains a California government service.
2. Decide whether the basic-information route or an existing Login.gov account is the more appropriate verification path.
3. Enter current, accurate information and correct formatting errors before assuming the residency classification is final.
4. Keep eligibility inputs separate from optional identifiers added later to improve broker matching.
5. Read the live notice at collection before entering profile identifiers, particularly device or vehicle identifiers.
6. If verification fails, use the on-screen review control promptly and follow the current section 7622 requirements.
7. Provide substantiating documents only when the Agency requests them and only through the official secure route presented for the review.
8. Preserve the DROP ID after submission; do not treat it as public evidence of identity or deletion.
9. Interpret each broker status as a matching outcome, not as a new decision about California residency.

Limits of verification

Passing the DROP eligibility check means the consumer may submit through this California mechanism. It does not prove that every registered broker holds a record, that matching will be unique, that exempt information must be erased, or that first-party data held by another business falls within the request. Those questions depend on the statute, regulations, broker records, and applicable exceptions.

This article provides general information, not legal advice. For a disputed residency classification, suspected misuse of identifiers, or disagreement about a broker’s legal obligations, consult the current official materials and consider advice from a qualified legal professional.