@proseid v1.0.0 US

California CCPA consumer-request lifecycle

Tracks intake, verification, acknowledgement, extension, disposition, downstream action, confirmation, and response timing for California delete, correct, know, sale-or-sharing opt-out, and sensitive-information limit requests. ADMT rights with a 1 January 2027 compliance date are outside this version.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v1.0.0
Applies in: United States
Fields: 25
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

ccpa_regulations_20262026-01-01 → continues indefinitely

Current

Controlling sources

Legal references

California Consumer Privacy Act, as amended California Civil Code §§ 1798.100 et seq.

Source ↗

California Consumer Privacy Act Regulations 11 CCR §§ 7000 et seq.

Source ↗

Schema fields

25 fields

Field

Type

Description

Req

Business handling the request

String

—

Req

Request denied or not fulfilled

Boolean

—

Opt

The 15-business-day opt-out or limit deadline has been reached

Boolean

—

Opt

Identity verified to the degree required for this request

Boolean

—

Opt

Receipt confirmed to the consumer

Boolean

—

Opt

Receipt confirmed within 10 business days

Boolean

—

Opt

Request track

String

—

Opt

The consumer can confirm that the opt-out or limit request was processed

Boolean

—

Opt

Date received

Date

—

Req

Response and actions taken

String

—

Req

Denial or statutory-exception reason

String

—

Opt

Required downstream action

Select

Choices: Completed, Not Required After Documented Review, Outstanding

Opt

The organization and request are within CCPA scope

Boolean

—

Req

One 45-day extension was used

Boolean

—

Opt

Completed within the extended 90-day maximum

Boolean

—

Opt

The 10-business-day acknowledgement deadline has been reached

Boolean

—

Opt

Consumer request

Select

Choices: Know, Delete, Correct, Opt Out Sale Or Sharing, Limit Sensitive Information

Req

Opt-out or limit request honored within 15 business days

Boolean

—

Opt

The extended 90-calendar-day maximum has been reached

Boolean

—

Opt

Internal request reference

String

—

Req

Extension notice sent during the initial 45-day period

Boolean

—

Opt

Request completed

Boolean

—

Opt

Completed within the initial 45 calendar days

Boolean

—

Opt

The initial 45-calendar-day response deadline has been reached

Boolean

—

Opt

Reason the extension was reasonably necessary

String

—

Opt

Example payload

JSON

{
  "responses": {
    "business_name": "",
    "request_denied": false,
    "opt_out_or_limit_deadline_reached": false,
    "identity_verified": false,
    "receipt_confirmed": false,
    "receipt_confirmed_within_10_business_days": false,
    "consumer_can_confirm_request_processed": false,
    "received_at": "",
    "response_summary": "",
    "denial_or_exception_reason": "",
    "downstream_action_status": "",
    "ccpa_scope_confirmed": false,
    "extension_used": false,
    "completed_within_extended_90_days": false,
    "acknowledgement_deadline_reached": false,
    "request_type": "",
    "completed_within_15_business_days": false,
    "extended_response_deadline_reached": false,
    "request_reference": "",
    "extension_notice_sent_in_initial_period": false,
    "request_completed": false,
    "completed_within_45_calendar_days": false,
    "initial_response_deadline_reached": false,
    "extension_reason": ""
  },
  "effective_at": "2026-07-23"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "business_name",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v1.0.0

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

EU right-of-withdrawal record

OSHA fatality or severe-injury reporting determination

SEC material cybersecurity incident disclosure record

HIPAA breach-notification determination