privacy-page-generator
# privacy-page-generator This Claude Code skill structures Privacy Policy pages for digital products, guiding users through identifying what data their product collects, which privacy regulations apply, and how to disclose AI involvement, analytics, and data retention practices. Use it when users need to create, update, or ensure compliance for privacy documentation, especially when GDPR, CCPA, cookie policies, or AI model training are relevant.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/privacy-page-generator && cp -r /tmp/privacy-page-generator/skills/pages/legal/privacy ~/.claude/skills/privacy-page-generatorSKILL.md
# Pages: Privacy Policy Guides Privacy Policy page content, structure, compliance, and AI-specific disclosures. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment Identify: 1. **Product category**: Free anonymous, free with account, freemium, subscription SaaS, enterprise/B2B, API/developer, marketplace, e-commerce, content/media, mobile app, AI agent/MCP — see legal-page-generator §Product Categories 2. **Data actually collected**: URLs, prompts, uploads, analytics, cookies, account data, payment data — be exhaustive 3. **AI involvement**: Whether AI models process user data and whether data is used for training (see §AI Disclosures) 4. **Jurisdiction needs**: Which privacy regulations apply — see legal-page-generator §Jurisdiction Decision Framework 5. **Indexing**: Typically index (see legal-page-generator §Indexing Strategy) --- ## Required Sections (14-Section Framework) ### 1. Who We Are - Operator name (or "the operator of [Product]" for anonymous operations) - Tool purpose in one plain-language sentence - Contact email ### 2. What [Product] Does - One paragraph explaining the core function - Mention that no account or payment is required (if applicable) - Set expectations: this is a [free/paid] [tool type] that does [X] ### 3. Information We Collect Structure with clear sub-sections: **What We Do NOT Collect** (trust signal — include for all products): - No accounts, no passwords, no user profiles - No payment information (if free) - No contact lists or address books - No precise location data - Adapt this list to what's actually true for the product **Data You Submit** (URLs, prompts, uploads, form inputs): - What happens to it: processed for [purpose], sent to [AI providers if applicable] - Whether it's stored: "processed in-memory and discarded after the request" or retention period - Whether it's used for training: "not used to train AI models" (if true — state explicitly) **Generated Content** (AI output, images, text): - Returned to user's browser/account - Whether retained on servers - Whether used for training **Analytics Data**: - Which analytics tool (GA4, Plausible, etc.) - What's collected (page views, device/browser, referrer, country-level location, session duration) - Whether it identifies individuals **Account Data** (if applicable): - Email, username, profile information - How it's used and stored **Payment Data** (if applicable): - Note that payment is processed by [processor], not stored directly ### 4. How We Use Information - Purposes: service provision, improvement, security, analytics, legal compliance - **AI Model Training Disclosure**: State explicitly whether user data is used to train, improve, or fine-tune AI models. If using API-based AI (OpenAI API, Google Cloud), note that these providers do not train on API data. If using consumer AI tools, disclose that training may occur. - Marketing communications (with consent where required) ### 5. Cookies Table format with opt-out instructions: | Cookie | Purpose | Duration | How to Opt Out | |--------|---------|----------|----------------| | `_ga`, `_ga_*` | Google Analytics — aggregate usage measurement | Up to 2 years | [GA opt-out browser add-on](https://tools.google.com/dlpage/gaoptout) or block third-party cookies | | `[session_cookie]` | Session management / fair-use enforcement | 24 hours / session | Clear browser data | Also state: - Whether advertising cookies are used - Whether cross-site tracking occurs - Whether the site responds to Do Not Track signals ### 6. Third-Party Processors Table format with privacy policy URLs: | Provider | Purpose | Privacy Policy | |----------|---------|----------------| | [Cloud provider] | Hosting / backend | [URL] | | [CDN provider] | Content delivery / routing | [URL] | | [AI model provider 1] | AI generation / processing | [URL] | | [AI model provider 2] | AI generation / processing | [URL] | | [Analytics provider] | Usage analytics | [URL] | ### 7. Data Retention Specify per category — avoid vague "as long as needed" language: - **Submitted data** (URLs, prompts, uploads): processed in-memory, discarded after response — not stored - **Generated content**: delivered to browser, not retained on servers - **Analytics aggregates**: retained for [X] months (GA4 default: 14 months) - **Server access logs**: retained for 30 days for security/debugging - **Account data** (if applicable): retained until account deletion; then deleted within [X] days ### 8. Your Rights Structure by jurisdiction: **GDPR (EEA/UK)**: - Rights: access, rectification, erasure, restriction, portability, objection - Legal basis for processing (Art. 6) - Right to lodge complaint with supervisory authority - Response timeframe: 30 days **CCPA (California)**: - Rights: know, delete, correct, opt-out of sale/sharing - Statement: "[Product] does not sell personal information" - How to exercise rights **How to Exercise**: - Email contact - Identity verification if needed (note: for anonymous tools, minimal data exists) ### 9. International Transfers - Where data is processed (country/region) - Safeguards: Standard Contractual Clauses, adequacy decisions, or other mechanisms - Note that data may transit through other regions as part of standard internet routing ### 10. Children - Age threshold: under 13 (US/COPPA) or under 16 (EEA/GDPR) - Statement: "not directed to children" / "do not knowingly collect" - What to do if a child has submitted data: contact for deletion ### 11. Security - TLS/HTTPS in transit - Encryption at rest (provider-managed or self-managed) - **No-credentials advantage** (if no accounts): "no passwords or credentials to leak" - No payment data stored (if applicable) - Breach notification commitment ### 12. Changes - Material changes pos
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.