Individual skill

privacy-policy-drafter

Draft a clear, plain-language privacy policy tailored to what a product actually collects and does with data. Use when asked to write a privacy policy, draft a data-protection notice, or create a GDPR/CCPA-aware privacy statement. Produces a structured policy covering data collected, purposes, legal bases, sharing, retention, user rights, and contact — written to be readable, not boilerplate. Not legal advice; have counsel review before publishing.

plugins/pm-legal/skills/privacy-policy-drafter/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Privacy Policy Drafter Skill

A privacy policy should tell users plainly what you collect, why, and what control they have — not hide it in legalese. This skill drafts a structured, regulation-aware policy from how the product actually handles data. **Not legal advice — a qualified lawyer should review before you publish, and obligations vary by jurisdiction.**

## Working from a brief

Given a product description, **draft the full policy anyway**, inferring typical data flows and marking each inference *(confirm — reflects assumed practice)*. Never leave "[company name]"-style gaps un-flagged, and never state a practice the founder didn't confirm as fact without labelling it an assumption.

## Required Inputs

Ask for (if not already provided):
- **Product / company** and what it does
- **Data collected** (account info, usage/analytics, payment, location, cookies, etc.)
- **Why** it's collected and **who it's shared with** (processors, analytics, payment, ads)
Back to top