CCPA / CPRA

California privacy law gives a resident rights that a business must honor on request. An assistant that touches consumer records lands inside that duty immediately. This starter covers the traffic side of it, and the rights workflow itself stays a product you build.

The request path starts with injection screening and an identity check that needs verified user and organization claims. Redaction then masks national identifier patterns before the prompt leaves the gateway. A pattern block list stops prompts that name a consumer request, sensitive personal information, or a third party disclosure. Those phrases usually belong in a rights workflow, not in a model prompt.

Returned text must hold a combined score of 0.85, with relevance at 0.78 and accuracy at 0.80. Short answers fail too, because the gate wants at least 120 characters and two sentences. A response that misses a floor is blocked, so a reviewer sees a refusal rather than a thin answer.

Rights work is the part California regulators examine most closely. The starter therefore ends every response at a person, and the caller receives no assistant text at all. A recorded escalation takes the place of an answer. Decide before launch whether your team can absorb that volume of review.

Verification of a requester, opt-out signal handling and disclosure notices live in your product and your service desk. This starter cannot honor a deletion request, and it cannot publish a notice. Treat it as the traffic control layer under those obligations.

Grounding is measured on the way back, and an unverified citation is flagged rather than stopped. The Brazilian privacy starter shares this shape, and it answers to a different authority with a different notification clock.