A verifiable consumer request is a request to exercise a privacy right that a business can reasonably confirm was made by the consumer to whom the personal information relates, or by a person legally authorized to act on that consumer’s behalf. The term comes from the California Consumer Privacy Act (CCPA) and its regulations, and it sits at the heart of user rights in Privacy practice because it decides whether a business must act on a request at all.
Verification protects consumers in two directions. It ensures that genuine requests are honored, and it prevents impostors from obtaining or deleting someone else’s data, a real risk because a right-to-know response can itself become a data breach if sent to the wrong person.
How a verifiable consumer request is processed
A business processes a verifiable consumer request by receiving it through a designated channel, confirming receipt, matching identifying details against records it already holds, and then responding on the merits. The verification step comes before disclosure or deletion, never after.
The following table shows the standard sequence and the timing expectations set by the CCPA regulations.
| Stage | What happens | Timing |
|---|---|---|
| Intake | Request arrives by web form, toll-free number or other method | Day 0 |
| Acknowledgment | Business confirms receipt and explains next steps | Within 10 business days |
| Verification | Identifiers are matched against existing records | As early as possible |
| Fulfillment | Data disclosed, corrected or deleted | Within 45 calendar days |
| Extension | Notice with reasons for additional time | Up to 45 more days |
| Recordkeeping | Request and response logged | Kept for 24 months |
The 45-day clock starts when the business receives the request, not when verification finishes. Slow verification therefore consumes the response window, which is why mature programs automate identity matching wherever possible.
Verification standards by request type
The CCPA regulations apply a risk-based verification standard: the more sensitive the data and the greater the harm from a wrongful response, the stronger the proof the business should require. A business must consider the type and sensitivity of the information, the risk of harm, the likelihood of fraud and the available verification methods.
| Request type | Required certainty | Typical method |
|---|---|---|
| Categories of data | Reasonable degree of certainty | Match at least two data points |
| Specific pieces of data | Reasonably high degree of certainty | Match three data points plus signed declaration |
| Deletion | Reasonable or reasonably high, by sensitivity | Two or three data points |
| Correction | Reasonable or reasonably high, by sensitivity | Identity match plus supporting documents |
| Opt-out of sale or sharing | Not a verifiable request | No identity proof required |
| Limit sensitive data use | Not a verifiable request | No identity proof required |
The distinction for opt-out requests is deliberate. Stopping the sale of data cannot harm the consumer, so the business may not demand verification, although it may decline a request it has a documented, good-faith reason to believe is fraudulent.
Account holders, non-account holders and households
When a consumer has a password-protected account, the business may verify the request through its existing authentication practices, such as a login with multi-factor authentication. It must, however, re-authenticate before disclosing or deleting data, and it must not force a consumer to create an account just to submit a request.
For non-account holders, the business matches details the consumer provides against information already in its systems, such as a recent order number, billing postal code and email address. Requests concerning a household require a joint request from all members, with each member individually verified and none of them a minor unless a parent acts.
Requests made through an authorized agent add a further layer. The business may require signed written permission from the consumer, and it may ask the consumer to verify identity directly or confirm that the agent has permission, unless the agent holds a power of attorney.
How it differs from a DSAR and related concepts
A verifiable consumer request is a California-specific legal construct, while a data subject access request (DSAR) is the broader term used across regimes, especially the GDPR. The underlying idea is similar, but the rules on scope and verification differ in ways that matter for global programs.
| Concept | Legal source | Verification approach |
|---|---|---|
| Verifiable consumer request | CCPA and its regulations | Tiered certainty by request type |
| DSAR under the GDPR | Article 15 and Article 12 | Additional information only if reasonable doubts exist |
| Authenticated request | Many newer state laws | Commercially reasonable authentication |
| Opt-out preference signal | CCPA regulations | No identity check; applies to browser or device |
Under the GDPR, a controller may request extra information only when it has reasonable doubts about identity, which sets a lower default burden than the CCPA tiers. Many other American state laws use the phrase authenticated consumer request with functionally similar meaning.
Failure modes and good practice in verification
Verification fails in two opposite ways: over-verification that blocks legitimate consumers and under-verification that hands data to fraudsters. Regulators treat both as compliance problems, and excessive friction can also count as a dark pattern that undermines the right itself.
| Mistake | Risk | Better practice |
|---|---|---|
| Demanding a passport scan | Collects new sensitive data unnecessarily | Match existing data points first |
| Emailing full reports unencrypted | Interception exposes personal data | Use a secure portal with authentication |
| Requiring account creation | Prohibited barrier to exercising rights | Accept requests from non-account holders |
| Charging a fee | Unlawful for standard requests | Process at no cost to the consumer |
| Keeping verification data indefinitely | Expands breach exposure | Delete it once the request closes |
- Use data already held for matching whenever possible, instead of collecting new identifiers.
- Delete information gathered solely for verification promptly after the request is processed, except for required records.
- When verification fails, explain the denial and tell the consumer what would allow the request to proceed.
- Never disclose Social Security numbers, account passwords or security answers in a response to a right-to-know request.
The short version
A verifiable consumer request is a privacy request that a company can check really came from you. Before it shows you your data or deletes it, the company makes sure you are who you say you are. It is like a bank asking a few questions before discussing your account.
The check gets stricter when more is at stake. Seeing a full copy of your data needs more proof than asking the company to stop selling it. That simple rule protects you from impostors without making ordinary requests hard.
Where it makes a difference
A subscription meal-kit company receives an emailed request from someone asking for every piece of personal information held about a named customer. The sender does not have an account login, so the privacy team asks for three existing data points: the delivery postal code, the last four digits of the payment card and the date of the most recent order, all of which already exist in its records.
Two details match, but the order date does not, and the email address differs from the one on file. Because the request seeks specific pieces of data, the team needs a reasonably high degree of certainty. It denies the disclosure, explains why, and offers to send a verification link to the address on file.
The real customer later confirms she never sent the request. The outcome: an attempted account takeover failed, and the company documented a compliant, timely response within the 45-day window.