| name | privacy-generator |
| title | Privacy Policy Generator |
| description | Generates comprehensive privacy policies by scanning websites for data collection
signals including cookies, forms, payment processors, and third-party scripts.
Use when launching a website or app that collects user data and needs GDPR/CCPA compliance.
Trigger with "/privacy-generator" or "create a privacy policy for my website". |
| author | jeremylongshore |
| author_url | https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/business-tools/general-legal-assistant/skills/privacy-generator |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | cross-jurisdiction |
| practice | data-protection |
| language | en |
| tags | ["legal","privacy-policy","gdpr","ccpa","cookies"] |
Privacy Policy Generator
Overview
Scans a website or application codebase to detect data collection signals — cookies,
web forms, payment processors, analytics scripts, social media embeds, and third-party
trackers — then generates a tailored privacy policy with 12 sections. Includes specific
GDPR rights (7 individual rights), CCPA rights (6 consumer rights), and cookie consent
banner text in both minimal and full GDPR formats.
The detection phase maps every data touchpoint to its legal basis and disclosure
requirement, ensuring the generated policy accurately reflects actual data practices
rather than relying on generic boilerplate.
Legal Disclaimer: This skill generates template documents for informational and
educational purposes only. Generated privacy policies are not a substitute for legal
advice. Data protection requirements vary by jurisdiction, industry, and data type.
All documents should be reviewed by a licensed attorney and/or data protection officer
before publication. No attorney-client relationship is created by using this tool.
Prerequisites
- A live website URL or local codebase to scan
- Knowledge of the business entity name and jurisdiction
- Understanding of what data is collected and why (the scan detects signals but cannot
capture server-side-only processing)
Instructions
-
Scan for data collection signals. Use WebFetch on the target URL to detect:
| Signal Category | What to Look For |
|---|
| Cookies | Set-Cookie headers, cookie consent banners, tracking pixels |
| Analytics | Google Analytics, Mixpanel, Amplitude, Hotjar, Segment |
| Forms | Contact forms, registration, login, newsletter signup |
| Payments | Stripe, PayPal, Square, Braintree, payment form fields |
| Social | Facebook Pixel, Twitter tags, LinkedIn Insight, social login |
| Advertising | Google Ads, Facebook Ads, retargeting pixels |
| CDN/Third-Party | Cloudflare, AWS CloudFront, Google Fonts, embedded iframes |
| Chat/Support | Intercom, Zendesk, Drift, live chat widgets |
-
If scanning a codebase instead, use Glob and Grep to find:
- Cookie-setting code (
document.cookie, setCookie, middleware)
