privacy-policy-stephane-boghossian
A zero-hallucination privacy-policy generator that takes anyone — non-lawyer founder to lawyer — from a guided intake to a publishable, jurisdiction-aware privacy policy. Jurisdiction-first: it detects which laws apply from where your users are, then drafts only the required clauses — GDPR/EU + UK, US (CCPA/CPRA, ~20 state laws, COPPA, sector overlays), and global/MENA (LGPD, Quebec Law 25, India DPDP, China PIPL, UAE/DIFC, Saudi PDPL), plus app-store, cookies, and AI/EU AI Act disclosures. Its rule: state only what you confirm; never invent a statute, citation, fine, or date — every claim is
npx skills add lawve-ai/awesome-legal-skills --skill privacy-policy-stephane-boghossian --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Privacy Policy Generator Generate a **bulletproof, jurisdiction-aware privacy policy** for any business or product, usable by a non-lawyer founder and trusted by a lawyer. The whole point of this skill is **correctness without hallucination**: a fabricated statutory citation or a clause that doesn't match the user's real practices is worse than no policy at all. ## ⚖️ The prime directive (read this first, never break it) 1. **State ONLY what the user confirms they actually do.** A privacy policy is a set of *enforceable representations* (FTC §5; see the OkCupid/Match 2026 and Gateway Learning cases in the reference pack). Saying more than is true is the #1 legal failure. Never default-in a flattering or risk-adding clause. 2. **Never invent law.** Do not generate a statute/section number, a fine amount, an effective date, or a "the law requires X" claim unless it traces to the bundled reference pack (`references/`) or a live `legal-data-hunter` lookup. If you're unsure of a specific, **name the law in plain terms** ("California's CCPA/CPRA," "the EU GDPR") and describe the *right* functionally — or omit it. Uncertain → omit or mark `[VERIFY]`, never guess. 3. **Confirm-don't-assu
- ⚖️ The prime directive (read this first, never break it)
- Workflow
- Step 1 — Pick the mode
- Step 2 — Compute the applicable-law set FIRST (jurisdiction-first)
- Step 3 — Gather practices (only the questions the selected laws require)
- Step 4 — Ground the legal content (zero-hallucination layer)
- Step 5 — Assemble the policy
- Step 6 — Self-QA gate (do NOT skip)
- Step 7 — Deliver the package
- Hard rules (guardrails)
- Companion documents
What does the privacy-policy-stephane-boghossian skill do?
A zero-hallucination privacy-policy generator that takes anyone — non-lawyer founder to lawyer — from a guided intake to a publishable, jurisdiction-aware privacy policy. Jurisdiction-first: it detects which laws apply from where your users are, then drafts only the required clauses — GDPR/EU + UK, US (CCPA/CPRA, ~20 state laws, COPPA, sector overlays), and global/MENA (LGPD, Quebec Law 25, India DPDP, China PIPL, UAE/DIFC, Saudi PDPL), plus app-store, cookies, and AI/EU AI Act disclosures. Its rule: state only what you confirm; never invent a statute, citation, fine, or date — every claim is
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill privacy-policy-stephane-boghossian --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.