What terms of service cover
Terms of service are the contract between you and the people who use your product. Privacy is a separate document; terms set the rules of use and the deal. In plain words, they answer: who can use the product and how accounts work; how people pay, renew, cancel and get refunds; what users must not do; who owns what, including content users upload; when you can suspend or close an account; what you don’t promise (disclaimers) and how much you can be liable for; how you’ll change the terms; and which law applies.
How to use this generator
- Pick your model. A SaaS subscription gets billing, auto-renewal and cancellation clauses; a one-time purchase gets a purchase clause; a free product gets a short note that you’ll ask before charging anything.
- Write your real refund policy. If you leave it blank, the draft shows a placeholder rather than inventing one.
- Untick acceptable-use rules that don’t fit, and add your own, such as API rate limits or content rules for a community product.
- The user content section says users keep ownership and give you a license only to run the product. If you use content for anything else, such as training models or marketing, say so plainly and have it reviewed.
- Governing law, the liability cap and the notice period stay as [bracketed] placeholders until you fill them in.
A template is a starting point
These clauses are common in software terms, but whether they fit, and whether they’re enforceable, depends on your company, your customers and their countries. Consumer protection rules in particular can override what a contract says. Read every clause, delete what doesn’t apply and have a qualified lawyer review the result before you publish. For a short, plain-English example, read our own terms and privacy policy.
Pair your terms with a privacy policy and a cookie policy, then work through the launch checklist before you go live.