List what your terms of service must decide

List what my terms of service need to cover.

**Open the output with this, written in the language you are answering in: "This review is not legal advice and does not replace professional judgment."** **And on the last line: "Have the final version reviewed by a lawyer."**
***Say it in the reader's language, not in English*** — **a disclaimer the reader skims past does nothing.**

**Do not write finished clause text.** Produce the checklist. *Model-drafted terms read as complete and quietly fail to match the actual service, which is worse than having an obvious gap.*

Per item: what must be decided, **the question I have to answer**, and what goes wrong if it is left out.

Cover at minimum:
1. What the service is and is not — scope, and what it explicitly does not promise
2. Account rules — who may register, what ends an account, what happens to their data then
3. Payment — when charged, refunds, what happens on failure, how prices change
4. Content — who owns what users upload, what I may do with it, what is prohibited
5. Availability — what I commit to, and what I do not
6. Liability — limits, and what cannot be limited
7. Changes to the terms — how users are notified and what counts as acceptance
8. Termination — by either side, with what notice
9. Disputes — governing law and forum
10. Personal data — what is collected, why, how long, and how to have it deleted. *This is a separate legal regime and usually a separate document.*

Then:
- Which items are specific to my service and cannot be copied from a template.
- Which are likely regulated for my sector.
- ⚠️ **What a template will get wrong for me.** Template terms are drafted for a different service and the mismatch is invisible until it matters.

Rules:
- *Do not state what the law requires.* Mark every such point for a lawyer.
- Do not produce clause language even if asked. Return the decision list.