legal-page-generator
This Claude Code skill guides the creation and structure of legal pages such as Privacy Policies, Terms of Service, and Cookie Policies for digital products. Use it when users request help drafting, optimizing, or organizing legal compliance content, or mention specific legal page types, compliance requirements, or regulatory needs for their product category and jurisdiction.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/legal-page-generator && cp -r /tmp/legal-page-generator/skills/pages/legal/legal ~/.claude/skills/legal-page-generatorSKILL.md
# Pages: Legal Guides legal page content, structure, compliance, and platform readiness for AI/SaaS products. **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/platform, e-commerce, content/media, mobile app, AI agent/MCP — see §Product Categories 2. **Page type**: Privacy Policy, Terms of Service, Cookie Policy, etc. 3. **Jurisdiction needs**: Which countries' laws apply — see §Jurisdiction Decision Framework 4. **Indexing strategy**: Index or noindex — see §Indexing Strategy 5. **Platform dependencies**: Which external platforms require these pages — see §Platform Dependencies --- ## Product Categories The legal page structure depends heavily on the product category. Identify which one applies before drafting: | Category | Key Legal Characteristics | Sections to INCLUDE | Sections to SKIP | |---|---|---|---| | **Free Anonymous** | No accounts, no payment, no persistent storage, GA4 analytics | What we DON'T collect, no-training statement, fair-use limits, free/no-SLA | Payment, account responsibilities, refund, data portability | | **Free with Account** | Login required, user data stored, may have social features | Account security, data access/portability, user responsibilities | Payment, billing, refund | | **Freemium** | Free + paid tiers, payment data, auto-renewal | Payment terms, billing, tier differences, data handling per tier | — | | **Subscription SaaS** | Recurring billing, auto-renewal, cancellation | Payment, billing cycles, auto-renewal disclosure, cancellation process | — | | **Enterprise / B2B** | DPA, SOC 2, zero-training guarantees, SCCs | DPA reference, sub-processor list, security certifications, data processing roles, custom retention | Fair-use limits (usually N/A) | | **API / Developer** | Data processor role, rate limits, API keys | Rate limits, API key security, data processor terms, uptime/SLA | End-user account sections | | **Marketplace / Platform** | Multi-party, UGC responsibility, submission licensing | Content moderation, takedown process, submitter licenses, third-party content disclaimer | — | | **E-commerce** | Physical/digital goods, refunds, shipping | Refund policy, shipping policy, consumer rights, payment security | — | | **Content / Media** | Copyright, DMCA, content licensing | DMCA contact, content ownership, republication terms | Payment (unless paid content) | | **Mobile App** | App store review, privacy nutrition labels, permissions | App store compliance notes, permission justifications, data collection summary | — | | **AI Agent / MCP** | Automated decisions, tool invocation, sub-processor chains | AI decision transparency, sub-processor chain disclosure, autonomous action limits | — | --- ## Platform Dependencies Many external platforms **require** posted Privacy Policy and/or Terms of Service before the product can be listed, advertised, or operate in compliance. These should be flagged to the user during generation. ### Submission & Directory Platforms Most AI tool directories, MCP/Skills marketplaces, and software directories require both Privacy Policy and Terms of Service to be publicly accessible before a listing can be approved. Common requirements across these platforms: - Publicly linked Privacy Policy and Terms of Service - No illegal, deceptive, or IP-infringing content - Accurate, non-misleading product descriptions - Submitter warrants ownership or authority to list - Platform reserves right to reject or remove listings at discretion - Often require a DMCA/copyright complaint contact ### Advertising & Distribution Platforms | Platform | Requires | Consequence if Missing | |----------|----------|----------------------| | Google Ads | Privacy Policy link during account setup | Cannot launch campaigns | | Meta Ads (Facebook/Instagram) | Privacy Policy for ad account verification | Ad account suspended | | TikTok Ads | Privacy Policy for account review | Cannot launch | | Apple App Store | Privacy Policy URL + privacy nutrition labels | App rejected | | Google Play Console | Privacy Policy URL for all apps | App rejected | | LinkedIn Ads | Privacy Policy for business page verification | Restricted access | ### Infrastructure & Compliance | Requirement | What's Needed | |-------------|---------------| | Google Analytics ToS §7 | Posted privacy policy that discloses GA usage | | Stripe / payment processors | Privacy Policy URL during onboarding | | OAuth providers (Google, GitHub) | Privacy Policy URL for app verification | | SOC 2 / ISO 27001 | Both pages are standard vendor-assessment prerequisites | | Enterprise procurement | Both pages are due-diligence checklist items | | Accelerators (YC, Techstars, etc.) | Legal pages are standard application requirements | --- ## Jurisdiction Decision Framework Use a three-layer approach to determine which laws apply: **Layer 1 — Operator location** → determines primary governing law and venue in Terms. **Layer 2 — User locations** → determines which privacy regulations apply and whether regional supplements are needed. If the product is accessible globally, assume GDPR (EU), CCPA (California), and the operator's home jurisdiction at minimum. **Layer 3 — Data storage location** → determines data localization obligations. China (PIPL) and India (DPDP) may require local storage. ### Major Privacy Regulations (2025–2026) | Jurisdiction | Law | Consent Model | Max Penalty | Notable | |---|---|---|---|---| | EU/EEA | GDPR | Opt-in | €20M / 4% global revenue | 72h breach notification; DPO required for certain entities | | UK | UK GDPR + DPA 2018 | Opt-in | £17.5M / 4% | Post-Brexit independent; UK Representative required | | Ca
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.