/legal

name: legal-page-generator
description: When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal requirements." For Privacy Policy content, use privacy-page-generator. For Terms of Service, use terms-page-generator. For Cookie Policy, use cookie-policy-page-generator.
metadata:
  version: 1.2.0

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 operat