Terms of Service
The agreement between litecommerce and a tenant using the platform.
Draft scaffold — not a legal document
This page is a placeholder. It has not been reviewed by counsel, it is not in effect, and it creates no rights or obligations for anyone. It lists what the Terms of Service will need to cover — the operative language is deliberately absent.
Nothing here may be relied on, quoted, or presented to a customer as litecommerce's terms.
litecommerce's role
litecommerce is the service provider. The tenant is the merchant of record for its own sales.
Sections this document must cover
Scope only. These describe what each section has to establish, not what it will say.
1. Service scope and availability
What the platform provides, what is explicitly out of scope, and what availability (if any) is committed. No SLA number should appear here until one is actually measurable and operationally backed.
2. Tenant obligations
Accurate account information, lawful use, responsibility for content and goods sold, responsibility for end-customer relationships, and credential security.
3. Merchant of record, PCI, and tax responsibility
The allocation that currently lives only in help-center copy must become binding here: the tenant is merchant of record for its sales, sells through its own connected Stripe account, and owns its own tax registration, collection, and 1099-K reporting. litecommerce is merchant of record only for the tenant's own SaaS subscription to litecommerce.
4. Fees, billing, renewal, and refunds
Subscription pricing, billing cadence, automatic renewal, proration on plan change (DR-2569-01: upgrades prorate, downgrades prorate a refund), failed-payment handling, and the refund position. Must not contradict what the billing implementation actually does.
5. Acceptable use
Incorporates the Acceptable Use Policy by reference.
6. Intellectual property
Platform IP stays with litecommerce; tenant content and data stay with the tenant. Any licence litecommerce needs to operate the service must be stated and limited to that purpose.
7. Warranty disclaimer and limitation of liability
COUNSEL-DRAFTED. Jurisdiction-sensitive and unenforceable if drafted carelessly. No placeholder language.
8. Suspension, termination, and offboarding
Grounds for suspension, notice, the tenant's data-export window, and what happens to tenant data after termination. Must map to the implemented suspend/archive organization lifecycle rather than describing a process that does not exist.
9. Governing law and dispute resolution
COUNSEL-DRAFTED. Depends on the operating entity's jurisdiction.
10. Changes to these terms
How changes are notified and when they take effect. Must be consistent with the versioned consent captured at signup.
Open questions for counsel
- Confirm the contracting entity and its jurisdiction before any governing-law or liability language is drafted.
- The merchant-of-record and tax allocation is load-bearing and currently only stated in non-binding help copy. It must survive review intact.
- Renewal and refund language must be checked against the shipped billing behaviour, not against intent.
Tracked by issue #1828. Tenant storefront policies are a separate thing entirely — each tenant publishes its own shopper-facing policies, which are not covered by any document here.