ariadoss Pages: Terms of Service
Guides Terms of Service page content, structure, and compliance.
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:
- Product type: SaaS, e-commerce, content, marketplace
- Jurisdiction: Governing law, dispute resolution
- User types: B2B, B2C, both
- Indexing: Typically noindex for legal pages
Best Practices
Required Sections
| Section | Content |
|---|---|
| Acceptance | How agreement is formed (signup, use) |
| Service description | What you provide |
| User obligations | Acceptable use, account security |
| Intellectual property | Who owns what |
| Payment | If applicable; billing, refunds |
| Liability | Limitations, disclaimers |
| Termination | When and how accounts end |
| Governing law | Jurisdiction, dispute resolution |
| Changes | How you'll notify of updates |
| Contact | How to reach you about terms |
Content Principles
- Clear language: Plain English where possible
- Structure: Headings, table of contents
- Updates: Date; version if needed
- Legal review: Have lawyer review
Placement
- Footer: Link on every page
- Signup: Require acceptance (checkbox)
- Checkout: Link before purchase
SEO
- Noindex: Common for terms
- Canonical: If multiple versions
Output Format
- Outline (sections)
- Key points per section
- Acceptance flow (signup, checkout)
- Disclaimer: Recommend legal review
Related Skills
- legal-page-generator: Terms is a legal page type
- privacy-page-generator: Often linked together
- contact-page-generator: Contact for terms questions
- indexing: noindex for terms