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)
• Jurisdictions / regulations in scope (GDPR, UK GDPR, CCPA/CPRA, others)
• Contact for privacy requests and whether there's a DPO

Output Format