ccpa-cpra-privacy-expert by borghei/claude-skills
npx skills add https://github.com/borghei/claude-skills --skill ccpa-cpra-privacy-expert适用于《加州消费者隐私法案》(CCPA) 和《加州隐私权法案》(CPRA) 合规性的工具和指南。
根据所有 CCPA/CPRA 要求评估组织的准备情况。验证隐私政策、消费者权利处理、技术保障措施和退出机制。
# 从 JSON 配置文件检查合规性
python scripts/ccpa_compliance_checker.py --input company_profile.json
# 生成空白输入模板
python scripts/ccpa_compliance_checker.py --template > company_profile.json
# 用于自动化的 JSON 输出
python scripts/ccpa_compliance_checker.py --input company_profile.json --json
# 将报告导出到文件
python scripts/ccpa_compliance_checker.py --input company_profile.json --output report.json
评估类别:
| 类别 | 关键检查项 |
|---|---|
| 适用性 | 收入阈值、消费者数量、数据销售收入 |
| 隐私政策 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 要求的披露内容、更新频率、可访问性 |
| 消费者权利 | 请求处理、验证、时间线 |
| 退出机制 | "请勿出售"链接、GPC信号、Cookie同意 |
| 敏感个人信息 | SPI类别、使用限制链接、处理控制 |
| 技术保障措施 | 加密、访问控制、安全措施 |
| 服务提供商 | 协议要求、数据处理条款 |
| 风险评估 | 年度审计、处理风险评估 |
输出:
映射个人信息类别,识别敏感个人信息,跟踪数据在收集、使用、共享和出售过程中的流向。生成数据清单报告。
# 从 JSON 数据清单映射数据
python scripts/ccpa_data_mapper.py --input data_inventory.json
# 生成空白清单模板
python scripts/ccpa_data_mapper.py --template > data_inventory.json
# 导出映射报告
python scripts/ccpa_data_mapper.py --input data_inventory.json --output mapping_report.json
# 生成数据流图(基于文本)
python scripts/ccpa_data_mapper.py --input data_inventory.json --flow-diagram
功能:
跟踪的个人信息类别:
| 类别 | CCPA 章节 | 示例 |
|---|---|---|
| 标识符 | 1798.140(v)(1)(A) | 姓名、SSN、IP地址、电子邮件 |
| 客户记录 | 1798.140(v)(1)(B) | 财务信息、医疗信息 |
| 受保护分类 | 1798.140(v)(1)(C) | 种族、性别、年龄、残疾 |
| 商业信息 | 1798.140(v)(1)(D) | 购买历史、趋势 |
| 生物识别信息 | 1798.140(v)(1)(E) | 指纹、面部几何特征 |
| 互联网活动 | 1798.140(v)(1)(F) | 浏览、搜索、互动 |
| 地理位置数据 | 1798.140(v)(1)(G) | 精确位置 |
| 感官数据 | 1798.140(v)(1)(H) | 音频、视觉、热感 |
| 专业信息 | 1798.140(v)(1)(I) | 就业、教育 |
| 教育信息 | 1798.140(v)(1)(J) | 非公开教育记录 |
| 推断信息 | 1798.140(v)(1)(K) | 画像、偏好 |
references/ccpa-cpra-requirements-guide.md
完整的法规要求涵盖:
references/ccpa-implementation-playbook.md
分步实施指南:
Step 1: 确定适用性
→ 检查 2500万美元收入、10万+消费者、50%+ PI 收入阈值
→ 审查豁免情况(HIPAA、GLBA、就业数据)
Step 2: 生成合规性配置文件模板
→ python scripts/ccpa_compliance_checker.py --template > profile.json
→ 填写组织详细信息
Step 3: 运行合规性评估
→ python scripts/ccpa_compliance_checker.py --input profile.json
Step 4: 审查得分和发现项
→ 首先解决关键缺口(退出链接、隐私政策)
→ 按类别规划修复
Step 5: 创建数据清单
→ python scripts/ccpa_data_mapper.py --template > inventory.json
→ 记录所有收集的 PI 类别
→ python scripts/ccpa_data_mapper.py --input inventory.json
Step 6: 制定实施计划
→ 参见 references/ccpa-implementation-playbook.md
Step 1: 接收消费者请求
→ 识别请求类型(知情、删除、退出、更正、可携、限制 SPI)
Step 2: 在 10 个工作日内确认(确认收到)
→ 在跟踪系统中记录请求
Step 3: 验证消费者身份
→ 标准请求匹配 2+ 个数据点
→ 敏感数据请求匹配 3+ 个数据点
→ 退出请求无需验证
Step 4: 在 45 个日历日内完成请求
→ 延期:最多可额外延长 45 天并通知
→ 使用数据清单搜索所有系统
→ python scripts/ccpa_data_mapper.py --input inventory.json
Step 5: 交付响应
→ 如果请求,以可移植格式提供信息
→ 记录完成情况和响应
Step 6: 监控合规性
→ 跟踪响应时间和完成率
→ 生成季度合规性报告
Step 1: 根据要求审查当前隐私政策
→ python scripts/ccpa_compliance_checker.py --input profile.json
→ 检查 privacy_policy 类别得分
Step 2: 更新数据清单
→ python scripts/ccpa_data_mapper.py --input inventory.json
→ 验证所有 PI 类别均已披露
Step 3: 验证要求的披露内容
→ 收集的 PI 类别(过去 12 个月)
→ PI 来源
→ 商业/商业目的
→ 第三方类别
→ 消费者权利描述
→ "请勿出售或共享"链接
→ "限制使用我的敏感 PI"链接
Step 4: 更新并发布
→ 至少每年更新一次
→ 重大变更后 30 天内更新
→ 维护先前版本存档
| 日期 | 里程碑 |
|---|---|
| 2020年1月1日 | CCPA 生效 |
| 2020年7月1日 | 司法部长开始执法 |
| 2020年11月3日 | CPRA 通过(第24号提案) |
| 2023年1月1日 | CPRA 修正案生效 |
| 2023年7月1日 | CPPA 开始执行 CPRA |
| 2026年 | 就业和 B2B 数据豁免状态审查 |
如果满足以下条件,企业 将受 CCPA/CPRA 约束:
实体类型:
| 实体 | 定义 | 义务 |
|---|---|---|
| 企业 | 确定处理的目的和方式 | 完全遵守 CCPA/CPRA |
| 服务提供商 | 代表企业处理 PI(合同约定) | 有限使用、删除义务 |
| 承包商 | 通过书面合同处理 PI(CPRA 新增) | 认证、有限使用、审计权 |
| 第三方 | 非作为服务提供商/承包商接收 PI | 受退出权约束 |
豁免:
| 权利 | CCPA 章节 | 描述 | 时间线 |
|---|---|---|---|
| 知情权 | §1798.100, §1798.110 | 收集的 PI 类别和具体内容 | 45天 |
| 删除权 | §1798.105 | 删除从消费者处收集的 PI | 45天 |
| 退出权 | §1798.120 | 选择退出 PI 的出售或共享 | 立即 |
| 不受歧视权 | §1798.125 | 不因行使权利而受到报复 | 持续 |
| 更正权 | §1798.106 | 更正不准确的 PI (CPRA) | 45天 |
| 限制 SPI 使用权 | §1798.121 | 限制敏感 PI 的使用 (CPRA) | 立即 |
| 数据可携权 | §1798.130 | 以可移植格式接收 PI (CPRA) | 45天 |
根据 CPRA §1798.140(ae) 需要加强保护的 SPI 类别:
| 违规类型 | 处罚 | 执法者 |
|---|---|---|
| 非故意违规 | 每次违规 2,500 美元 | CPPA / 司法部长 |
| 故意违规 | 每次违规 7,500 美元 | CPPA / 司法部长 |
| 涉及未成年人(16岁以下)的违规 | 每次违规 7,500 美元 | CPPA / 司法部长 |
| 数据泄露(私人诉讼) | 每位消费者每次事件 100-750 美元 | 消费者(法院) |
执法机构:
| 方面 | CCPA/CPRA | GDPR |
|---|---|---|
| 范围 | 加州消费者 | 欧盟/欧洲经济区数据主体 |
| 法律基础 | 选择退出模式 | 选择加入(同意或法律基础) |
| 涵盖数据 | 个人信息 | 个人数据 |
| 敏感数据 | 具有限制使用权的 SPI | 需要明确同意的特殊类别 |
| 泄露通知 | 司法部长通知、私人诉讼 | 72 小时内通知 DPA |
| DPO 要求 | 无 | 某些处理需要 |
| 处罚 | 每次违规 2,500-7,500 美元 | 最高全球收入的 4% 或 2000 万欧元 |
| 私人诉讼权 | 仅限数据泄露 | 各成员国不同 |
| 跨境传输 | 无限制 | 充分性决定、SCCs、BCRs |
| 儿童数据 | 16岁以下需选择加入,13岁以下需父母同意 | 16岁以下需父母同意(可变) |
Cookie 同意管理:
全球隐私控制 (GPC):
Sec-GPC: 1 头信息或 navigator.globalPrivacyControl隐私设计:
数据清单和映射:
自动化决策:
第 1-2 个月:发现和评估
第 3-4 个月:实施
第 5-6 个月:运营化
每周安装次数
1
代码仓库
GitHub 星标数
29
首次出现
今天
安全审计
安装于
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
Tools and guidance for California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA) compliance.
Evaluates organizational readiness against all CCPA/CPRA requirements. Validates privacy policies, consumer rights handling, technical safeguards, and opt-out mechanisms.
# Check compliance from a JSON profile
python scripts/ccpa_compliance_checker.py --input company_profile.json
# Generate a blank input template
python scripts/ccpa_compliance_checker.py --template > company_profile.json
# JSON output for automation
python scripts/ccpa_compliance_checker.py --input company_profile.json --json
# Export report to file
python scripts/ccpa_compliance_checker.py --input company_profile.json --output report.json
Assessment Categories:
| Category | Key Checks |
|---|---|
| Applicability | Revenue threshold, consumer count, data selling revenue |
| Privacy Policy | Required disclosures, update cadence, accessibility |
| Consumer Rights | Request handling, verification, timelines |
| Opt-Out Mechanisms | "Do Not Sell" link, GPC signal, cookie consent |
| Sensitive PI | SPI categories, use limitation link, handling controls |
| Technical Safeguards | Encryption, access controls, security measures |
| Service Providers | Agreement requirements, data processing terms |
| Risk Assessments | Annual audits, processing risk evaluations |
Output:
Maps personal information categories, identifies sensitive personal information, tracks data flows across collection, use, sharing, and selling. Generates data inventory reports.
# Map data from a JSON data inventory
python scripts/ccpa_data_mapper.py --input data_inventory.json
# Generate a blank inventory template
python scripts/ccpa_data_mapper.py --template > data_inventory.json
# Export mapping report
python scripts/ccpa_data_mapper.py --input data_inventory.json --output mapping_report.json
# Generate data flow diagram (text-based)
python scripts/ccpa_data_mapper.py --input data_inventory.json --flow-diagram
Features:
Personal Information Categories Tracked:
| Category | CCPA Section | Examples |
|---|---|---|
| Identifiers | 1798.140(v)(1)(A) | Name, SSN, IP address, email |
| Customer Records | 1798.140(v)(1)(B) | Financial info, medical info |
| Protected Classifications | 1798.140(v)(1)(C) | Race, sex, age, disability |
| Commercial Information | 1798.140(v)(1)(D) | Purchase history, tendencies |
| Biometric Information | 1798.140(v)(1)(E) | Fingerprints, face geometry |
| Internet Activity | 1798.140(v)(1)(F) | Browsing, search, interaction |
| Geolocation Data | 1798.140(v)(1)(G) | Precise location |
| Sensory Data | 1798.140(v)(1)(H) | Audio, visual, thermal |
| Professional Info | 1798.140(v)(1)(I) |
references/ccpa-cpra-requirements-guide.md
Complete regulatory requirements covering:
references/ccpa-implementation-playbook.md
Step-by-step implementation guidance:
Step 1: Determine applicability
→ Check $25M revenue, 100K+ consumers, 50%+ PI revenue thresholds
→ Review exemptions (HIPAA, GLBA, employment data)
Step 2: Generate compliance profile template
→ python scripts/ccpa_compliance_checker.py --template > profile.json
→ Fill in organizational details
Step 3: Run compliance assessment
→ python scripts/ccpa_compliance_checker.py --input profile.json
Step 4: Review scores and findings
→ Address critical gaps first (opt-out link, privacy policy)
→ Plan remediation by category
Step 5: Create data inventory
→ python scripts/ccpa_data_mapper.py --template > inventory.json
→ Document all PI categories collected
→ python scripts/ccpa_data_mapper.py --input inventory.json
Step 6: Develop implementation plan
→ See references/ccpa-implementation-playbook.md
Step 1: Receive consumer request
→ Identify request type (Know, Delete, Opt-Out, Correct, Portability, Limit SPI)
Step 2: Acknowledge within 10 business days (confirm receipt)
→ Document request in tracking system
Step 3: Verify consumer identity
→ Match 2+ data points for standard requests
→ Match 3+ data points for sensitive data requests
→ No verification needed for opt-out requests
Step 4: Fulfill request within 45 calendar days
→ Extension: up to 45 additional days with notice
→ Search all systems using data inventory
→ python scripts/ccpa_data_mapper.py --input inventory.json
Step 5: Deliver response
→ Provide information in portable format if requested
→ Document completion and response
Step 6: Monitor compliance
→ Track response times and completion rates
→ Generate quarterly compliance reports
Step 1: Review current privacy policy against requirements
→ python scripts/ccpa_compliance_checker.py --input profile.json
→ Check privacy_policy category score
Step 2: Update data inventory
→ python scripts/ccpa_data_mapper.py --input inventory.json
→ Verify all PI categories are disclosed
Step 3: Verify required disclosures
→ Categories of PI collected (past 12 months)
→ Sources of PI
→ Business/commercial purposes
→ Categories of third parties
→ Consumer rights description
→ "Do Not Sell or Share" link
→ "Limit the Use of My Sensitive PI" link
Step 4: Update and publish
→ Annual update at minimum
→ Update within 30 days of material changes
→ Maintain prior version archive
| Date | Milestone |
|---|---|
| Jan 1, 2020 | CCPA effective |
| Jul 1, 2020 | AG enforcement begins |
| Nov 3, 2020 | CPRA passed (Proposition 24) |
| Jan 1, 2023 | CPRA amendments effective |
| Jul 1, 2023 | CPPA enforcement of CPRA begins |
| 2026 | Employment and B2B data exemptions status review |
A business is subject to CCPA/CPRA if it:
Entity Types:
| Entity | Definition | Obligations |
|---|---|---|
| Business | Determines purposes and means of processing | Full CCPA/CPRA compliance |
| Service Provider | Processes PI on behalf of a business (contractual) | Limited use, deletion obligations |
| Contractor | Processes PI via written contract (CPRA addition) | Certification, limited use, audit rights |
| Third Party | Receives PI not as service provider/contractor | Subject to opt-out rights |
Exemptions:
| Right | CCPA Section | Description | Timeline |
|---|---|---|---|
| Right to Know | §1798.100, §1798.110 | Categories and specific pieces of PI collected | 45 days |
| Right to Delete | §1798.105 | Delete PI collected from the consumer | 45 days |
| Right to Opt-Out | §1798.120 | Opt out of sale or sharing of PI | Immediate |
| Right to Non-Discrimination | §1798.125 | No retaliation for exercising rights | Ongoing |
| Right to Correct | §1798.106 | Correct inaccurate PI (CPRA) | 45 days |
| Right to Limit SPI Use | §1798.121 | Limit use of sensitive PI (CPRA) | Immediate |
| Right to Data Portability | §1798.130 |
SPI categories requiring enhanced protections under CPRA §1798.140(ae):
| Violation Type | Penalty | Enforcer |
|---|---|---|
| Unintentional violation | $2,500 per violation | CPPA / AG |
| Intentional violation | $7,500 per violation | CPPA / AG |
| Violations involving minors (under 16) | $7,500 per violation | CPPA / AG |
| Data breach (private action) | $100-$750 per consumer per incident | Consumer (court) |
Enforcement Bodies:
| Aspect | CCPA/CPRA | GDPR |
|---|---|---|
| Scope | California consumers | EU/EEA data subjects |
| Legal basis | Opt-out model | Opt-in (consent or legal basis) |
| Data covered | Personal information | Personal data |
| Sensitive data | SPI with limit-use right | Special category with explicit consent |
| Breach notification | AG notification, private action | 72-hour DPA notification |
| DPO requirement | None | Required for certain processing |
| Penalties | $2,500-$7,500 per violation | Up to 4% global revenue or €20M |
| Private right of action | Data breaches only | Varies by member state |
| Cross-border transfers | No restrictions | Adequacy decisions, SCCs, BCRs |
Cookie Consent Management:
Global Privacy Control (GPC):
Sec-GPC: 1 header or navigator.globalPrivacyControlPrivacy by Design:
Data Inventory and Mapping:
Automated Decision-Making:
Month 1-2: Discovery and Assessment
Month 3-4: Implementation
Month 5-6: Operationalization
Weekly Installs
1
Repository
GitHub Stars
29
First Seen
Today
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
31,600 周安装
前端动画设计指南:提升用户体验的微交互与动效策略
38,600 周安装
跨平台设计适配指南:移动端、桌面端、平板、打印及邮件适配策略与实施方法
38,800 周安装
前端打磨(Polish)终极指南:提升产品细节与用户体验的系统化检查清单
39,900 周安装
Web应用测试指南:使用Python Playwright自动化测试本地Web应用
39,500 周安装
Azure Cloud Migrate:AWS Lambda到Azure Functions迁移工具 - 微软官方评估与代码迁移
38,700 周安装
Excel财务建模规范与xlsx文件处理指南:专业格式、零错误公式与数据分析
42,900 周安装
| Employment, education |
| Education Info | 1798.140(v)(1)(J) | Non-public education records |
| Inferences | 1798.140(v)(1)(K) | Profiles, preferences |
| Receive PI in portable format (CPRA) |
| 45 days |
| Children's data | Opt-in for under 16, parental for under 13 | Parental consent for under 16 (variable) |