Terms of Service Generator
Overview
Scans a website or application to understand the business model, user interactions,
data collection practices, and third-party integrations, then generates a comprehensive
terms of service document with 16 sections. Includes GDPR and CCPA compliance provisions,
plain English summaries after each section, and [VERIFY] tags for assumptions that
require human confirmation.
The generated ToS adapts its language and provisions based on the detected business type
(e-commerce, SaaS, marketplace, content platform, mobile app, etc.).
Legal Disclaimer: This skill generates template documents for informational and
educational purposes only. Generated terms of service are not a substitute for legal
advice. All documents should be reviewed by a licensed attorney before publication.
Regulatory requirements vary by jurisdiction and business type. No attorney-client
relationship is created by using this tool.
Prerequisites
- A live website URL or local codebase to analyze
- Knowledge of the business entity name and jurisdiction
- Understanding of whether the service involves payments, user accounts, or user-generated content
Instructions
Analyze the website or application. Use WebFetch to scan the target URL. Identify:
- Business type (SaaS, e-commerce, marketplace, content, API, mobile app)
- User interaction patterns (accounts, purchases, subscriptions, content uploads)
- Data collection mechanisms (forms, cookies, analytics scripts, payment processors)
- Third-party integrations (Stripe, Google Analytics, social login, CDNs)
- Geographic indicators (language, currency, server location)
If a codebase is available instead, use Glob and Read to scan for:
- Cookie/tracking implementations
- Authentication flows
- Payment integrations
- User data models
- API endpoints that accept user input
Gather business details from the user:
- Legal entity name and type (LLC, Corp, sole proprietor)
- Business address and jurisdiction
- Contact email for legal notices
- Minimum user age requirement
- Whether the service is free, paid, or freemium
Determine applicable compliance frameworks:
- GDPR — if serving EU/EEA users (detected via language, .eu domain, Euro pricing)
- CCPA/CPRA — if serving California users or meeting revenue/data thresholds
- COPPA — if the service could attract users under 13
- ADA/WCAG — if a US-based public-facing service
- PCI-DSS — if processing payment card data
- CAN-SPAM — if sending marketing emails
Generate the 16-section Terms of Service:
| # |
Section |
Covers |
| 1 |
Agreement to Terms |
Acceptance mechanism, effective date |
| 2 |
Description of Service |
What the service provides |
| 3 |
User Accounts |
Registration, security, age requirements |
| 4 |
Acceptable Use Policy |
Prohibited conduct, content standards |
| 5 |
User-Generated Content |
Ownership, licenses, moderation rights |
| 6 |
Intellectual Property |
Company IP rights, trademarks, DMCA |
| 7 |
Payment Terms |
Pricing, billing cycles, refunds (if applicable) |
| 8 |
Free Trials & Subscriptions |
Trial terms, auto-renewal, cancellation |
| 9 |
Privacy & Data Collection |
Reference to privacy policy, GDPR/CCPA summary |
| 10 |
Third-Party Services |
Links, integrations, disclaimers |
| 11 |
Disclaimers & Warranties |
"As-is" provision, warranty limitations |
| 12 |
Limitation of Liability |
Liability caps, excluded damages |
| 13 |
Indemnification |
User indemnification obligations |
| 14 |
Termination |
Grounds, notice, effect of termination |
| 15 |
Governing Law & Disputes |
Jurisdiction, arbitration, class action waiver |
| 16 |
General Provisions |
Modifications, severability, entire agreement, contact |
Add plain English summaries. After each section, include a blockquote:
> **In Plain English:** {simple summary of what this means for users}
Insert compliance-specific provisions:
- GDPR: Data processing legal basis, right to erasure, DPO contact, data portability
- CCPA: "Do Not Sell My Personal Information" rights, opt-out mechanism
- COPPA: Age verification, parental consent mechanism
Tag all assumptions. Place [VERIFY] before any clause based on inferred information:
[VERIFY: assumed SaaS model based on subscription pricing detected]
[VERIFY: jurisdiction set to Delaware — confirm with business owner]
[VERIFY: assumed no users under 13 — confirm age policy]
Write the output file using the naming convention below.
Output
Generate a single Markdown file named TERMS-OF-SERVICE-{company}-{YYYY-MM-DD}.md with:
# Terms of Service
**{Company Name}**
**Last Updated:** {date}
**Effective Date:** {date}
---
## Table of Contents
1. [Agreement to Terms](#1-agreement-to-terms)
{... all 16 sections ...}
---
## 1. Agreement to Terms
{formal legal text}
> **In Plain English:** {simple explanation}
## 2. Description of Service
{formal legal text}
> **In Plain English:** {simple explanation}
{... sections 3-16 ...}
---
## Contact Information
{business contact details}
---
**[VERIFY] Tags Summary:**
{numbered list of all assumptions needing confirmation}
**Compliance Frameworks Applied:** {GDPR, CCPA, etc.}
**Generated by:** Legal Assistant Plugin — Not a substitute for legal counsel.
Error Handling
| Error |
Cause |
Solution |
| Website unreachable |
URL is down or behind auth |
Ask user for a description of the service or local codebase path |
| Cannot determine business type |
Minimal website content |
Ask user directly about their business model |
| Payment detection ambiguous |
Cannot tell if free or paid |
Ask user to confirm pricing model |
| International complexity |
Multiple jurisdictions detected |
Generate provisions for all detected jurisdictions, add [VERIFY] |
| Dynamic content not scannable |
SPA with client-side rendering |
Ask user to describe features or provide sitemap |
| Missing company details |
User did not provide entity info |
Use [VERIFY] placeholders, list in summary |
Examples
Example 1: SaaS Application
Request: "Create terms of service for https://example-saas.com — we're a project management tool"
Result: TERMS-OF-SERVICE-ExampleSaaS-2026-04-02.md with:
- 16 sections with SaaS-specific provisions
- Payment terms for subscription model (detected via Stripe integration)
- GDPR provisions (EU users detected via multi-language support)
- CCPA provisions (US-based company)
- User-generated content section for project data
- 8 [VERIFY] tags for assumptions
Example 2: E-Commerce Store
Request: "Generate ToS for my Shopify store selling handmade jewelry"
Result: TERMS-OF-SERVICE-HandmadeJewels-2026-04-02.md with:
- E-commerce focused provisions (returns, shipping, product descriptions)
- Payment terms referencing Shopify Payments / PayPal
- No user-generated content section (simplified)
- Consumer protection provisions per FTC guidelines
- CCPA opt-out mechanism
Resources
Source: jeremylongshore/claude-code-plugins-plus-skills → skills/.curated/terms-generator/SKILL.md
Also appears in: jeremylongshore/claude-code-plugins-plus-skills/plugins/business-tools/general-legal-assistant/skills/terms-generator/SKILL.md
1---2name: terms-generator3description: "'Generates comprehensive terms of service by analyzing a website or application to detect business type, data collection, and user interactions. Use when launching a website, app, or SaaS product that needs terms of service with GDPR/CCPA compliance. Trigger with \"/terms-generator\" or \"create terms of service for my website\". '"4allowed-tools: "Read, Write, Glob, Grep, WebFetch"5category: security-and-compliance6source_repo: jeremylongshore/claude-code-plugins-plus-skills7source_path: "skills/.curated/terms-generator/SKILL.md"8source_url: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/HEAD/skills/.curated/terms-generator/SKILL.md9---1011# Terms of Service Generator1213## Overview1415Scans a website or application to understand the business model, user interactions,16data collection practices, and third-party integrations, then generates a comprehensive17terms of service document with 16 sections. Includes GDPR and CCPA compliance provisions,18plain English summaries after each section, and `[VERIFY]` tags for assumptions that19require human confirmation.2021The generated ToS adapts its language and provisions based on the detected business type22(e-commerce, SaaS, marketplace, content platform, mobile app, etc.).2324> **Legal Disclaimer:** This skill generates template documents for informational and25> educational purposes only. Generated terms of service are not a substitute for legal26> advice. All documents should be reviewed by a licensed attorney before publication.27> Regulatory requirements vary by jurisdiction and business type. No attorney-client28> relationship is created by using this tool.2930## Prerequisites3132- A live website URL or local codebase to analyze33- Knowledge of the business entity name and jurisdiction34- Understanding of whether the service involves payments, user accounts, or user-generated content3536## Instructions37381. **Analyze the website or application.** Use WebFetch to scan the target URL. Identify:39 - Business type (SaaS, e-commerce, marketplace, content, API, mobile app)40 - User interaction patterns (accounts, purchases, subscriptions, content uploads)41 - Data collection mechanisms (forms, cookies, analytics scripts, payment processors)42 - Third-party integrations (Stripe, Google Analytics, social login, CDNs)43 - Geographic indicators (language, currency, server location)44452. **If a codebase is available instead**, use Glob and Read to scan for:46 - Cookie/tracking implementations47 - Authentication flows48 - Payment integrations49 - User data models50 - API endpoints that accept user input51523. **Gather business details from the user:**53 - Legal entity name and type (LLC, Corp, sole proprietor)54 - Business address and jurisdiction55 - Contact email for legal notices56 - Minimum user age requirement57 - Whether the service is free, paid, or freemium58594. **Determine applicable compliance frameworks:**60 - **GDPR** — if serving EU/EEA users (detected via language, .eu domain, Euro pricing)61 - **CCPA/CPRA** — if serving California users or meeting revenue/data thresholds62 - **COPPA** — if the service could attract users under 1363 - **ADA/WCAG** — if a US-based public-facing service64 - **PCI-DSS** — if processing payment card data65 - **CAN-SPAM** — if sending marketing emails66675. **Generate the 16-section Terms of Service:**6869 | # | Section | Covers |70 |---|---------|--------|71 | 1 | Agreement to Terms | Acceptance mechanism, effective date |72 | 2 | Description of Service | What the service provides |73 | 3 | User Accounts | Registration, security, age requirements |74 | 4 | Acceptable Use Policy | Prohibited conduct, content standards |75 | 5 | User-Generated Content | Ownership, licenses, moderation rights |76 | 6 | Intellectual Property | Company IP rights, trademarks, DMCA |77 | 7 | Payment Terms | Pricing, billing cycles, refunds (if applicable) |78 | 8 | Free Trials & Subscriptions | Trial terms, auto-renewal, cancellation |79 | 9 | Privacy & Data Collection | Reference to privacy policy, GDPR/CCPA summary |80 | 10 | Third-Party Services | Links, integrations, disclaimers |81 | 11 | Disclaimers & Warranties | "As-is" provision, warranty limitations |82 | 12 | Limitation of Liability | Liability caps, excluded damages |83 | 13 | Indemnification | User indemnification obligations |84 | 14 | Termination | Grounds, notice, effect of termination |85 | 15 | Governing Law & Disputes | Jurisdiction, arbitration, class action waiver |86 | 16 | General Provisions | Modifications, severability, entire agreement, contact |87886. **Add plain English summaries.** After each section, include a blockquote:89 `> **In Plain English:** {simple summary of what this means for users}`90917. **Insert compliance-specific provisions:**92 - GDPR: Data processing legal basis, right to erasure, DPO contact, data portability93 - CCPA: "Do Not Sell My Personal Information" rights, opt-out mechanism94 - COPPA: Age verification, parental consent mechanism95968. **Tag all assumptions.** Place `[VERIFY]` before any clause based on inferred information:97 - `[VERIFY: assumed SaaS model based on subscription pricing detected]`98 - `[VERIFY: jurisdiction set to Delaware — confirm with business owner]`99 - `[VERIFY: assumed no users under 13 — confirm age policy]`1001019. **Write the output file** using the naming convention below.102103## Output104105Generate a single Markdown file named `TERMS-OF-SERVICE-{company}-{YYYY-MM-DD}.md` with:106107```108# Terms of Service109**{Company Name}**110111**Last Updated:** {date}112**Effective Date:** {date}113114---115116## Table of Contents1171. [Agreement to Terms](#1-agreement-to-terms)118{... all 16 sections ...}119120---121122## 1. Agreement to Terms123{formal legal text}124125> **In Plain English:** {simple explanation}126127## 2. Description of Service128{formal legal text}129130> **In Plain English:** {simple explanation}131132{... sections 3-16 ...}133134---135136## Contact Information137{business contact details}138139---140**[VERIFY] Tags Summary:**141{numbered list of all assumptions needing confirmation}142143**Compliance Frameworks Applied:** {GDPR, CCPA, etc.}144**Generated by:** Legal Assistant Plugin — Not a substitute for legal counsel.145```146147## Error Handling148149| Error | Cause | Solution |150|-------|-------|----------|151| Website unreachable | URL is down or behind auth | Ask user for a description of the service or local codebase path |152| Cannot determine business type | Minimal website content | Ask user directly about their business model |153| Payment detection ambiguous | Cannot tell if free or paid | Ask user to confirm pricing model |154| International complexity | Multiple jurisdictions detected | Generate provisions for all detected jurisdictions, add [VERIFY] |155| Dynamic content not scannable | SPA with client-side rendering | Ask user to describe features or provide sitemap |156| Missing company details | User did not provide entity info | Use [VERIFY] placeholders, list in summary |157158## Examples159160**Example 1: SaaS Application**161162Request: "Create terms of service for https://example-saas.com — we're a project management tool"163164Result: `TERMS-OF-SERVICE-ExampleSaaS-2026-04-02.md` with:165166- 16 sections with SaaS-specific provisions167- Payment terms for subscription model (detected via Stripe integration)168- GDPR provisions (EU users detected via multi-language support)169- CCPA provisions (US-based company)170- User-generated content section for project data171- 8 [VERIFY] tags for assumptions172173**Example 2: E-Commerce Store**174175Request: "Generate ToS for my Shopify store selling handmade jewelry"176177Result: `TERMS-OF-SERVICE-HandmadeJewels-2026-04-02.md` with:178179- E-commerce focused provisions (returns, shipping, product descriptions)180- Payment terms referencing Shopify Payments / PayPal181- No user-generated content section (simplified)182- Consumer protection provisions per FTC guidelines183- CCPA opt-out mechanism184185## Resources186187- [FTC Business Guidance on Terms](https://www.ftc.gov/business-guidance) — Federal Trade Commission compliance188- [California Attorney General CCPA](https://oag.ca.gov/privacy/ccpa) — CCPA regulations and guidance189- [ICO Guide to Data Protection](https://ico.org.uk/for-organisations/) — UK/GDPR compliance guidance190- [CommonPaper Standard Terms](https://commonpaper.com/standards/) — CC BY 4.0 open-source terms191- [Termly ToS Generator](https://termly.io/) — Reference for section structures192- [SBA Small Business Legal Resources](https://www.sba.gov/) — US government business guidance193194---195196**Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `skills/.curated/terms-generator/SKILL.md`197198**Also appears in:** `jeremylongshore/claude-code-plugins-plus-skills/plugins/business-tools/general-legal-assistant/skills/terms-generator/SKILL.md`