consent-languagelisted

Generates legally compliant privacy notices, consent flows, cookie banners, and data subject rights disclosures for products and services. Use when user says "write a privacy policy", "privacy notice", "cookie consent", "GDPR consent flow", "data subject rights page", "at collection notice", "CCPA disclosure", "PIPEDA privacy statement", "opt-in consent copy", "cookie banner text", "legitimate interests notice", "generate consent UI copy", or when launching a product or feature that collects personal data and needs compliant disclosure language. Produces layered notices (short/full), jurisdiction-specific variations, UI copy for consent flows, cookie categorization text, and rights exercise mechanisms. Grounded in GDPR Arts. 13/14, PIPEDA Clause 4.8, CCPA § 1798.100, Quebec Law 25, COPPA, ePrivacy Directive, and PIPL Art. 17.
fevra-dev/Subrosa · ★ 0 · Web & Frontend · score 72

Install: claude install-skill fevra-dev/Subrosa

# Consent Language Generates privacy notices, consent flows, cookie banners, and rights disclosures that satisfy legal requirements across GDPR, PIPEDA, CCPA/CPRA, Quebec Law 25, COPPA, ePrivacy Directive, and PIPL. **Composable with:** - `data-minimization` — run first; the field inventory defines what must be disclosed - `privacy-impact-assessment` — PIA determines legal basis; consent language implements it - `privacy-architecture` — if ZK or anonymous credentials are used, consent language should reflect the reduced data collection --- ## Regulatory Source of Truth Statutory citations and jurisdiction facts (deadlines, thresholds, ages, category lists) in this skill and its reference files derive from the normalized taxonomy: `taxonomy/regulatory-taxonomy.md` + the per-jurisdiction records (`taxonomy/regulatory-taxonomy--*.md`, axes A0–A12). Records consumed here: `ca-pipeda-law25`, `eu-gdpr-uk`, `us-ca-ccpa`, `br-lgpd`, `cn-pipl`, `sg-pdpa`, `th-pdpa` (+ COPPA and ePrivacy as sectoral overlays — S-profile records `us-coppa`, `eu-eprivacy`). On any discrepancy between this skill's files and a record: **the record wins** — unless this file is more specific or more correct, in which case fix the record and log the reconciliation in `.fable/reconciliation-log.md`. Never resolve a conflict by inventing a citation; unresolved conflicts carry `[UNVERIFIED — confirm against primary source]`. For "design-to-strictest" defaults use `taxonomy/regulatory-taxonomy--floor.md`.