US State Privacy Law Assessment
Assess US state privacy law compliance for "$ARGUMENTS". Map applicable state laws, compare requirements, and create a cross-state compliance matrix.
Prerequisites
Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run /compliance:regulatory-landscape $ARGUMENTS first, or use --skip-checks to bypass.
If --skip-checks is present in $ARGUMENTS, skip this check.
Process
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference
- Read
plugins/compliance/shared/assessment-template.md for output structure
- Read
.metapowers/compliance/$ARGUMENTS/00-scope.md for scope and control framework context
Applicable state law mapping:
- Determine which state laws apply based on organizational operations and customer base
- Assess applicability for established laws: Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA
- Assess applicability for newer laws: Texas TDPSA, Oregon OCPA, Montana MCDPA, Iowa ICDPA, Delaware DPDPA, New Jersey NJDPA, New Hampshire, Kentucky, Nebraska, Maryland, Minnesota, and others
- Document applicability thresholds per state (consumer count, revenue, data processing volume)
Cross-state requirement comparison:
- Compare consumer rights across states (access, delete, correct, portability, opt-out)
- Identify opt-out vs opt-in consent models per state
- Compare right to cure periods (30 days, 60 days, or none)
- Map enforcement mechanisms (AG only vs private right of action)
- Assess universal opt-out signal requirements per state
Common baseline identification:
- Identify the most restrictive state as the compliance floor
- Map common requirements shared across all applicable states
- Highlight unique or unusual state-specific requirements
- Assess whether a single compliance program can satisfy all states
Unique state requirements:
- Assess Data Protection Impact Assessment (DPIA) requirements by state
- Evaluate profiling and automated decision-making rights per state
- Review sensitive data definitions and consent requirements (varies by state)
- Assess children's data protections by state
- Evaluate data broker registration requirements where applicable
State-by-state compliance matrix:
- Create matrix: state vs requirement category (rights, notice, consent, DPIAs, enforcement)
- Score compliance per state per category
- Identify states with highest compliance gap
- Prioritize remediation by enforcement risk and gap severity
Write the artifact to .metapowers/compliance/$ARGUMENTS/01-assess/us-state-privacy.md following the assessment template structure with:
- Applicable States — list of states with applicability rationale
- Cross-State Matrix — requirements comparison across all applicable states
- Common Baseline — most restrictive floor requirements
- Unique Requirements — state-specific obligations not covered by baseline
- Per-State Compliance Score — readiness per state
- Gap Analysis — areas where current practices fall short per state
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The US state privacy law assessment written to .metapowers/compliance/$ARGUMENTS/01-assess/us-state-privacy.md. Present a summary to the user highlighting:
- Number of applicable state laws and highest-risk states
- Common baseline compliance score
- States with the largest compliance gaps
- Top 3 gaps requiring remediation
1---2name: us-state-privacy3description: Assess US state privacy law compliance — VCDPA, CPA, CTDPA, UCPA, and emerging laws4---56# US State Privacy Law Assessment78Assess US state privacy law compliance for "$ARGUMENTS". Map applicable state laws, compare requirements, and create a cross-state compliance matrix.910## Prerequisites1112Read `.metapowers/compliance/$ARGUMENTS/00-scope.md`. If this file does not exist, tell the user:1314> Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run `/compliance:regulatory-landscape $ARGUMENTS` first, or use `--skip-checks` to bypass.1516If `--skip-checks` is present in $ARGUMENTS, skip this check.1718## Process19201. **Read context files:**21 - Read `plugins/compliance/shared/grc-lifecycle-guide.md` for GRC methodology reference22 - Read `plugins/compliance/shared/assessment-template.md` for output structure23 - Read `.metapowers/compliance/$ARGUMENTS/00-scope.md` for scope and control framework context24252. **Applicable state law mapping:**26 - Determine which state laws apply based on organizational operations and customer base27 - Assess applicability for established laws: Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA28 - Assess applicability for newer laws: Texas TDPSA, Oregon OCPA, Montana MCDPA, Iowa ICDPA, Delaware DPDPA, New Jersey NJDPA, New Hampshire, Kentucky, Nebraska, Maryland, Minnesota, and others29 - Document applicability thresholds per state (consumer count, revenue, data processing volume)30313. **Cross-state requirement comparison:**32 - Compare consumer rights across states (access, delete, correct, portability, opt-out)33 - Identify opt-out vs opt-in consent models per state34 - Compare right to cure periods (30 days, 60 days, or none)35 - Map enforcement mechanisms (AG only vs private right of action)36 - Assess universal opt-out signal requirements per state37384. **Common baseline identification:**39 - Identify the most restrictive state as the compliance floor40 - Map common requirements shared across all applicable states41 - Highlight unique or unusual state-specific requirements42 - Assess whether a single compliance program can satisfy all states43445. **Unique state requirements:**45 - Assess Data Protection Impact Assessment (DPIA) requirements by state46 - Evaluate profiling and automated decision-making rights per state47 - Review sensitive data definitions and consent requirements (varies by state)48 - Assess children's data protections by state49 - Evaluate data broker registration requirements where applicable50516. **State-by-state compliance matrix:**52 - Create matrix: state vs requirement category (rights, notice, consent, DPIAs, enforcement)53 - Score compliance per state per category54 - Identify states with highest compliance gap55 - Prioritize remediation by enforcement risk and gap severity56577. **Write the artifact** to `.metapowers/compliance/$ARGUMENTS/01-assess/us-state-privacy.md` following the assessment template structure with:58 - **Applicable States** — list of states with applicability rationale59 - **Cross-State Matrix** — requirements comparison across all applicable states60 - **Common Baseline** — most restrictive floor requirements61 - **Unique Requirements** — state-specific obligations not covered by baseline62 - **Per-State Compliance Score** — readiness per state63 - **Gap Analysis** — areas where current practices fall short per state64 - **Evidence Inventory** — existing evidence and evidence gaps65 - **Remediation Priorities** — ranked list of gaps to address6667## Output6869The US state privacy law assessment written to `.metapowers/compliance/$ARGUMENTS/01-assess/us-state-privacy.md`. Present a summary to the user highlighting:70- Number of applicable state laws and highest-risk states71- Common baseline compliance score72- States with the largest compliance gaps73- Top 3 gaps requiring remediation