Set the rules for using your service
Terms of Service form the contract between you and the people who use your website or app. They establish who may use it, what they may not do, who owns the intellectual property, and how disputes are handled. A clear ToS reduces risk and sets expectations before anyone signs up. This builder assembles one from a few inputs and only includes the sections you need.
How it works
You describe your service and toggle optional clauses. The generator always includes the core sections — acceptance, eligibility, acceptable use, intellectual property, warranty disclaimer, limitation of liability, termination, changes, governing law, and contact — and renumbers them automatically. Three optional blocks switch in only when relevant:
- Accounts for services with logins and credentials.
- Fees and payment for paid plans and subscriptions.
- User content for platforms where users upload material, including the licence you need to host it.
What each core section does
Acceptance establishes that using the service means agreeing to the terms — the clickwrap mechanism that creates the contract. Eligibility sets the minimum age and any geographic restrictions. Acceptable use lists prohibited conduct: spam, scraping, illegal activity, impersonation. Spell these out specifically; vague language is harder to enforce.
Intellectual property makes clear who owns what. Your content, code, and branding remain yours; user content (if any) stays theirs, subject to a licence for you to display it. The warranty disclaimer says the service is provided “as is” — you are not guaranteeing uptime or accuracy. The limitation of liability caps your exposure to indirect or consequential losses, which can otherwise be enormous in a software context.
Termination covers both your right to suspend or delete accounts and what happens to user data on termination. Governing law picks the jurisdiction for disputes; this matters most for enforcement but can be overridden by mandatory consumer-protection laws in the user’s country.
Practical checklist before publishing
- Update the “last updated” date every time you revise the document.
- Notify existing users of material changes — a banner or email is standard practice.
- Pair the ToS with a separate privacy policy (legally distinct and required by GDPR, CCPA, etc.) and a cookie notice if you use tracking.
- If you accept payments, add a refund policy — credit-card chargebacks are expensive and a clear refund clause reduces them.
- Keep your governing-law clause consistent with your company’s place of registration.
This is a template to get you started quickly, not legal advice. A qualified lawyer familiar with your jurisdiction and business model should review the final document before it goes live.