Do You Actually Need Terms of Service?
Terms of Service aren't mandated by federal law like a Privacy Policy is — but without them, you have almost zero legal protection. If a customer sues you, disputes a charge, or abuses your service, Terms of Service are your first line of defense. They set the rules, limit your liability, and establish which state's laws apply to disputes.
You should have Terms of Service if you sell products or services online, run a subscription or SaaS product, allow user-generated content, accept payments, or offer any service where disputes might arise. Even a simple e-commerce site benefits from clear ToS.
What Every US Terms of Service Must Cover
Governing Law and Jurisdiction: Specify which state's laws govern the agreement and where disputes must be resolved. Delaware is popular for business-friendly courts; California is required if you have California users and is more consumer-protective. Choose based on where your business is incorporated or where most users are.
Limitation of Liability: Explicitly limit what you're liable for — service downtime, data loss, bugs, or damages. Most ToS include language like "Our total liability shall not exceed the amount you paid us in the past 12 months." This protects you from catastrophic lawsuit exposure.
Refund and Cancellation Policy: Be crystal clear: do you offer refunds? Within how long? For what reasons? "All sales final" is one option; 30-day money-back is another. Never be ambiguous. Unclear refund terms invite chargebacks and disputes.
Account Termination: Reserve the right to suspend or terminate accounts for violation of your ToS (e.g., harassment, illegal use, payment disputes). Explain what happens to the user's data when their account is terminated.
Intellectual Property Ownership: Clarify who owns what. Your company owns the service, the code, the design, the documentation. Users own the content they create — but grant you a license to use it (e.g., to store it, display it, back it up). If you use user content in marketing, say so explicitly.
User-Generated Content Rules: If users can post, upload, comment, or review on your platform, set expectations: no illegal content, no harassment, no spam, no IP infringement. You reserve the right to remove violating content and ban users.
Choosing Your Governing State
Picking the right governing state for your ToS matters. Delaware's courts are business-friendly and have deep jurisprudence on corporate disputes — most venture-backed companies choose Delaware. California is consumer-protective and required if your users or business are California-based. Texas, Nevada, and New York are also common choices. Avoid picking a state where you have no business presence unless you have a strategic reason.
The most important rule: be consistent. If your LLC is incorporated in Delaware, your ToS should be governed by Delaware law. If you're a California sole proprietor, use California law. Mismatches confuse courts and weaken enforceability.
Limitation of Liability: Protecting Yourself from Lawsuits
A Limitation of Liability clause is critical. Without it, you're exposed to claims for damages far exceeding the value you provided to a customer. A well-drafted clause typically says something like: "In no event shall [Company] be liable for indirect, incidental, special, or consequential damages, or loss of profit, revenue, or data." Combined with a cap ("Our total liability shall not exceed the amount you paid us"), this protects you from ruinous liability.
Note: limitations don't apply to gross negligence or willful misconduct. Courts won't enforce a ToS clause that tries to exempt you from liability if you're intentionally harmful.
Terms of Service vs Privacy Policy — Do You Need Both?
Yes. They serve completely different purposes. A Privacy Policy explains how you collect, use, and protect data. Terms of Service set the rules for using your service, limit your liability, and define ownership. A user should read both before using your service. You must provide links to both in a footer or easily accessible location.
Common Mistakes in DIY Terms of Service
- Vague language: "We may change terms at any time" is too broad. Specify a notice period (e.g., "we will notify you 30 days before material changes").
- Liability overreach: Don't try to exclude liability for personal injury, death, or fraud. Courts won't enforce it, and you'll look untrustworthy.
- Unreasonable refund policy: "No refunds ever, even if the service doesn't work" will invite chargebacks and bad reviews. A 30-day or 7-day refund is industry standard.
- Confusing user content ownership: Don't claim users' content as yours — just claim a license to use it for your service.
- No dispute resolution clause: A ToS without jurisdiction/governing law is nearly useless in court. Always specify.
- Not matching your actual practices: If your ToS say you don't share data but you do, that's deceptive under FTC law.