ccpa-compliance
Tools and guidance for California consumer privacy act compliance.
Install
mkdir -p .claude/skills/ccpa-compliance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16164" && unzip -o skill.zip -d .claude/skills/ccpa-compliance && rm skill.zipInstalls to .claude/skills/ccpa-compliance
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
California Consumer Privacy Act (CCPA) / CPRA compliance for businesses handling California resident data. Use when serving California users, building privacy features, implementing consumer data rights, or responding to data subject requests.Key capabilities
- →Implement GPC signal detection to auto-honor opt-out
- →Build a Data Subject Request (DSR) API for CCPA compliance
- →Add a 'Do Not Sell My Personal Information' opt-out flow
- →Map data to document personal data collected
- →Update privacy policy with required disclosures
- →Track and honor opt-out preferences
How it works
The skill provides code examples and guidance for implementing consumer rights, managing sensitive personal information, and handling privacy notices and GPC signals.
Inputs & outputs
When to use ccpa-compliance
- →Build a data subject request API
- →Add a 'Do Not Sell' opt-out flow
- →Implement GPC signal detection
- →Review compliance for data collection
About this skill
CCPA / CPRA Compliance
Overview
The California Consumer Privacy Act (CCPA), amended by CPRA (California Privacy Rights Act effective January 1, 2023), gives California residents rights over their personal information. Applies to for-profit businesses that do business in California and:
- Have annual gross revenue above the inflation-adjusted threshold ($26,625,000 since 2025-01-01; the statute says $25M and is re-indexed in odd-numbered years), OR
- Buy, sell or share personal info of 100,000+ California consumers/households, OR
- Derive 50%+ of annual revenue from selling or sharing personal info
Administrative fines (California Privacy Protection Agency or Attorney General): up to $2,663 per violation, $7,988 for intentional violations or those involving minors under 16 (2025 adjustment of $2,500 / $7,500). Consumers cannot sue for ordinary violations; the private right of action covers data breaches only ($107 to $799 per consumer per incident since 2025). Source: cppa.ca.gov/regulations/cpi_adjustment.html. The regulations in force from 2026-01-01 also add risk assessments, cybersecurity audits and automated decision-making technology (ADMT) rules with their own start dates; this skill covers the consumer-request and opt-out core only. This is engineering guidance, not legal advice.
Instructions
Consumer Rights Under CCPA/CPRA
| Right | Description | Response Deadline |
|---|---|---|
| Right to Know / Access (incl. portable copy) | What personal info is collected, used, shared, sold | Confirm receipt in 10 business days; answer in 45 days (+45-day extension with notice) |
| Right to Delete | Request deletion of personal info | Same: 10 business days / 45 days |
| Right to Correct | Correct inaccurate personal info (CPRA) | Same: 10 business days / 45 days |
| Right to Opt-Out | Opt out of sale or sharing of personal info | As soon as feasible, at most 15 business days; no verification may be required |
| Right to Limit | Limit use of sensitive personal info (CPRA) | At most 15 business days |
| Right to Non-Discrimination | Cannot be denied service for exercising rights | Always |
Source: CPPA regulations, sections 7021 and 7026 (cppa.ca.gov/regulations).
Sensitive Personal Information (CPRA)
CPRA adds extra protections for sensitive PI:
- SSN, driver's license, passport number
- Financial account credentials
- Precise geolocation (within a radius of 1,850 feet)
- Racial or ethnic origin
- Religious or philosophical beliefs
- Union membership
- Contents of mail, email, text messages
- Genetic data
- Neural data (added by SB 1223, in force since 2025)
- Biometric data used for identification
- Health information
- Sexual orientation or sex life
Data Inventory and Mapping
Before building request workflows, map your data:
# data_inventory.py — what personal data you collect, where, and who receives it
DATA_INVENTORY = {
"users.email": {"category": "contact", "sensitive": False, "shared_with": ["SendGrid"]},
"users.location": {"category": "location", "sensitive": True, "shared_with": []},
"events.device_id": {"category": "identifier", "sensitive": False, "shared_with": ["Mixpanel"]},
}
Privacy Notice Requirements
Your privacy policy must disclose:
- Categories of personal information collected
- Purposes for collection
- Whether you sell or share personal information
- Categories of third parties data is disclosed to
- Consumer rights and how to exercise them
- Contact info for privacy requests
Also state whether you sold or shared personal information in the preceding 12 months, link to the opt-out page, and give a contact for privacy requests (for example [email protected]).
GPC (Global Privacy Control) Signal Detection
GPC is a browser signal (HTTP header Sec-GPC: 1, and navigator.globalPrivacyControl in JavaScript) that the regulations treat as a valid opt-out of sale/sharing request (section 7025); businesses must honor it. Apply it to the browser or device that sent it, and to the account too if the user is logged in. It does not cover the right to limit sensitive data use.
// Express.js middleware — detect GPC signal and honor opt-out
const gpcMiddleware = (req, res, next) => {
const gpcEnabled = req.headers['sec-gpc'] === '1';
if (gpcEnabled) {
// Auto-apply opt-out for this request
req.privacyConsent = {
optedOutOfSale: true,
optedOutOfSharing: true,
source: 'gpc_signal',
detectedAt: new Date().toISOString()
};
// Record opt-out preference
if (req.user) {
recordOptOut(req.user.id, 'gpc_signal');
} else {
// Use cookie to persist for anonymous users
res.cookie('ccpa_optout', '1', {
maxAge: 365 * 24 * 60 * 60 * 1000, // 1 year
httpOnly: true,
secure: true,
sameSite: 'Lax'
});
}
}
next();
};
Data Subject Request (DSR) API
# FastAPI DSR endpoints
from fastapi import FastAPI, BackgroundTasks, HTTPException
from pydantic import BaseModel, EmailStr
from enum import Enum
import uuid
from datetime import datetime, timezone
app = FastAPI()
class DSRType(str, Enum):
KNOW = "know"
DELETE = "delete"
CORRECT = "correct"
OPT_OUT = "opt_out"
LIMIT_SPI = "limit_sensitive"
PORTABILITY = "portability"
class DSRRequest(BaseModel):
request_type: DSRType
email: EmailStr
name: str
correction_details: str | None = None # For CORRECT requests
class DSRResponse(BaseModel):
request_id: str
status: str
deadline: str
message: str
@app.post("/api/privacy/dsr", response_model=DSRResponse)
async def submit_dsr(request: DSRRequest, background_tasks: BackgroundTasks):
"""Submit a Data Subject Request."""
request_id = str(uuid.uuid4())
deadline_days = 15 if request.request_type in (DSRType.OPT_OUT, DSRType.LIMIT_SPI) else 45 # 15 business days vs 45 calendar days
# Store request
dsr_record = {
"id": request_id,
"type": request.request_type,
"email": request.email,
"name": request.name,
"status": "pending",
"submitted_at": datetime.now(timezone.utc).isoformat(),
"deadline_days": deadline_days,
"verified": False
}
await db.dsr_requests.insert(dsr_record)
# Opt-out and limit requests must NOT require verification: process them now.
if request.request_type in (DSRType.OPT_OUT, DSRType.LIMIT_SPI):
background_tasks.add_task(process_dsr, request_id, request.request_type, request.email)
return DSRResponse(request_id=request_id, status="processing",
deadline="15 business days at most",
message="Your request is being applied.")
# Others: confirm receipt within 10 business days and verify identity.
# send_verification_email must create and store a one-time token on the record.
background_tasks.add_task(send_verification_email, request.email, request_id)
return DSRResponse(
request_id=request_id,
status="pending_verification",
deadline="45 days from receipt (verification time counts)",
message="We've sent a verification email. Please verify your identity to proceed."
)
@app.post("/api/privacy/dsr/{request_id}/verify")
async def verify_dsr(request_id: str, token: str, background_tasks: BackgroundTasks):
"""Verify identity and begin DSR processing."""
dsr = await db.dsr_requests.find_one({"id": request_id, "token": token})
if not dsr:
raise HTTPException(status_code=404, detail="Request not found")
await db.dsr_requests.update({"id": request_id}, {"verified": True, "verified_at": datetime.now(timezone.utc).isoformat()})
background_tasks.add_task(process_dsr, request_id, dsr["type"], dsr["email"])
return {"status": "processing", "message": "Identity verified. Processing your request."}
async def process_dsr(request_id: str, dsr_type: DSRType, email: str):
"""Process DSR by type."""
user = await db.users.find_one({"email": email})
if not user:
await complete_dsr(request_id, "no_data_found")
return
if dsr_type == DSRType.DELETE:
await delete_user_data(user["id"])
elif dsr_type == DSRType.KNOW:
data_export = await export_user_data(user["id"])
await send_data_export(email, data_export)
elif dsr_type in (DSRType.OPT_OUT, DSRType.LIMIT_SPI):
await opt_out_user(user["id"]) # LIMIT_SPI also needs its own flag for sensitive data
elif dsr_type == DSRType.CORRECT:
await queue_correction_review(request_id, user["id"]) # applies correction_details after review
return # not complete until the correction is applied
elif dsr_type == DSRType.PORTABILITY:
portable_data = await export_portable_data(user["id"])
await send_data_export(email, portable_data, format="json")
await complete_dsr(request_id, "completed")
Data Export Pipeline (Right to Know / Portability)
Return the categories and specific pieces of personal information (covering at least the preceding 12 months), plus the sources, purposes and third parties, in a portable machine-readable format such as JSON. Build it from the data inventory so every table that holds the user's data is covered:
async def export_user_data(user_id: str) -> dict:
user = await db.users.find_one({"id": user_id})
orders = await db.orders.find({"user_id": user_id})
return {
"export_date": datetime.now(timezone.utc).isoformat(),
"profile": {"name": user["name"], "email": user["email"], "created_at": user["created_at"]},
"purchase_history": [{"order_id": o["id"], "date": o["date"], "amount": o["amount"]} for o in orders],
"third_party_sharing": [{"vendor": "Stripe", "purpose": "Payment processing"}],
}
Opt-Out of Sale/Sharing
Content truncated.
Limitations
- →Applies to for-profit businesses with specific revenue or data handling thresholds
- →Fines up to $2,500 per unintentional violation, $7,500 per intentional violation
- →DSR response within 45 days
How it compares
This skill provides concrete code examples and a compliance checklist for CCPA/CPRA, directly addressing specific legal requirements unlike general privacy guidelines.
Compared to similar skills
ccpa-compliance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ccpa-compliance (this skill) | 0 | 6mo | No flags | Intermediate |
| gdpr-dsgvo-expert | 8 | 11mo | Review | Advanced |
| data-privacy-compliance | 4 | 11mo | No flags | Intermediate |
| juicebox-data-handling | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by TerminalSkills
View all by TerminalSkills →You might also like
gdpr-dsgvo-expert
davila7
Senior GDPR/DSGVO expert and internal/external auditor for data protection compliance. Provides EU GDPR and German DSGVO expertise, privacy impact assessments, data protection auditing, and compliance verification. Use for GDPR compliance assessments, privacy audits, data protection planning, and regulatory compliance verification.
data-privacy-compliance
davila7
Data privacy and regulatory compliance specialist for GDPR, CCPA, HIPAA, and international data protection laws. Use when implementing privacy controls, conducting data protection impact assessments, ensuring regulatory compliance, or managing data subject rights. Expert in consent management, data minimization, and privacy-by-design principles.
juicebox-data-handling
jeremylongshore
Implement Juicebox data privacy and handling. Use when managing personal data, implementing GDPR compliance, or handling sensitive candidate information. Trigger with phrases like "juicebox data privacy", "juicebox GDPR", "juicebox PII handling", "juicebox data compliance".
ra-qm-skills
alirezarezvani
12 production-ready regulatory affairs and quality management skills for HealthTech/MedTech: ISO 13485 QMS, MDR 2017/745, FDA 510(k)/PMA, ISO 27001 ISMS, GDPR/DSGVO compliance, risk management (ISO 14971), CAPA, document control, and internal auditing. Python tools included (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw.
compliance-auditor
qa-aman
|
fda-medtech-compliance-auditor
TJSNDHU
Expert AI auditor for Medical Device (SaMD) compliance, IEC 62304, and 21 CFR Part 820. Reviews DHFs, technical files, and software validation.