Three names, one document, endless confusion. Terms of service, terms of use and terms and conditions all designate the contract that governs the use of a site or an application. The short answer: legally, the name does not matter; what the document says does. The longer answer explains why three names exist and when each one fits best.
Where the three names come from
| Name | Typical habitat | Connotation |
|---|---|---|
| Terms of service (ToS) | SaaS and online services | You are providing an ongoing service with accounts and billing |
| Terms of use (ToU) | Content sites, apps without accounts | Rules for merely accessing and browsing |
| Terms and conditions (T&C) | Commerce, contracts generally | The generic contract wording, common outside tech |
Courts read the content, not the title. A document called "terms of use" that sets payment obligations works like any contract; a "terms of service" page that nobody could find or accept may not bind anyone. Pick the name your audience expects and spend your energy on substance and presentation.
The difference that actually matters
The meaningful distinction is not between the three names; it is between the terms (whatever you call them) and the privacy policy. The terms are a contract you choose to publish, mainly to protect yourself. The privacy policy is a disclosure the law obliges you to publish, to protect your users. One can be accepted by a checkbox; the other must be true whether anyone reads it or not. Merging them into a single wall of text weakens both: consent to a contract and transparency about data are different legal acts.
Practical takeaways
- Keep two separate pages: terms on one, privacy policy on the other, both linked in the footer.
- Name the terms whatever fits your context; "terms and conditions" is the safest generic label.
- Make acceptance explicit at signup for the terms; make the privacy policy freely readable with no acceptance wall.
- Date both documents and keep prior versions.
For working examples of each, see our terms and conditions guide and our privacy policy guide, or read the production versions on this site: terms and privacy policy.