Last updated: [DATE] · Effective: [DATE]
1. Agreement to terms
[State that using the product means accepting these terms, and who the agreement is between.]
2. Definitions
[Define key terms: "Service", "Account", "Team", "Subscription", "Credits", "Content", match your product's actual vocabulary.]
3. Accounts and eligibility
[Account requirements, minimum age, accuracy of info, and responsibility for credentials and team-member activity.]
4. Acceptable use
[What users may not do: abuse, reverse-engineering, scraping, reselling access, illegal content. List concrete prohibitions for your product.]
5. Subscriptions, billing, and credits
[Describe plans, billing cycles (monthly/annual), the credit/usage model, auto-renewal, and that payments are processed by Stripe. State price-change notice terms.]
6. Refunds and cancellation
[Your refund policy and how cancellation works, including what happens to data and access after cancellation.]
7. Intellectual property
[Who owns the Service vs. user Content. Clarify the license users grant you to host their Content, and that you retain rights to your software.]
8. User content
[Responsibility for content users upload, your right to remove violating content, and any storage/upload limits.]
9. Third-party services
[Disclaim responsibility for third-party integrations the user connects, and that their terms also apply.]
10. Disclaimers and warranties
["As is" disclaimer to the extent the law allows. Have a lawyer phrase this for your jurisdiction.]
11. Limitation of liability
[Cap on liability and exclusion of indirect damages, within legal limits. Lawyer-required.]
12. Indemnification
[User agrees to cover claims arising from their misuse or content.]
13. Termination
[When and how either party can terminate, and the effect on data and outstanding payments.]
14. Governing law and disputes
[Which jurisdiction's law governs and how disputes are resolved (courts/arbitration). Fill in your actual jurisdiction.]
15. Changes to terms
[How you'll notify users of changes and when changes take effect.]
16. Contact
[Your contact address for legal/terms questions, e.g. support@keel.dev.]