California privacy request check

Verifiable Request 45 Day Response — Request Type: Correct · The acknowledgement period is 10 business days.

The calculated result is “Verifiable Request 45 Day Response”. Send the consumer an acknowledgement of the request.

Decision path4A927E8A04Schema 1.0.0
Entered facts7
The organization and request are within CCPA scopeYes
Consumer requestCorrect
One 45-day extension was usedNo
Receipt confirmed to the consumerNo
The 10-business-day acknowledgement deadline has been reachedYes
Receipt confirmed within 10 business daysNo
Request denied or not fulfilledYes
Action required
Calculated result

Verifiable Request 45 Day Response

Apply the published CCPA request lifecycle to the request type, verification, acknowledgement, extension, response, downstream action, and denial facts entered here. This scenario is distinct because it produces this exact combination of calculated result, active obligations, deadlines, and required evidence.

Published by ProseIDVersion 1.0.0
Rules activated3
Required

Send the consumer an acknowledgement of the request

Send the consumer an acknowledgement of the request.

11 CCR § 7021
Review

The acknowledgement may be late. Send it and preserve the timing record

The acknowledgement may be late. Send it and preserve the timing record.

11 CCR § 7021
Required

State the basis communicated to the consumer

State the basis communicated to the consumer.

11 CCR § 7021

Change the facts

A nearby path produces a different result.

Consumer requestCorrect → Opt Out Sale Or Sharing

Request denied or not fulfilledYes → No

Result becomesOpt Out Or Limit 15 Business Day Response

Inspect the changed path →

Published legal basis

Sources carried by this schema release.

The calculated path is bound to the cited version and sources. It is general information, not a substitute for advice on facts or law outside the schema.

Use your facts

Run the actual workflow.

This page shows one calculated path. Open the maintained workflow to answer with your own facts and, when needed, create a version-bound audit record.