Terms of Service

Who the contract is between, and how it is accepted — in practice, at signup. Whoever creates a workspace is binding their employer, so the terms should say they warrant they are authorised to do so.

What SimpleSynk provides, and what it does not commit to.

Responsibility for credentials and for the conduct of invited users, and the behaviour that will get an account suspended.

Per-active-person pricing, the monthly billing cycle, proration when headcount changes, and the fact that VAT is added at checkout based on the customer's country and VAT status. Should state that published price changes do not apply to an existing subscription until the customer moves to a new plan.

How to cancel, when access ends, and the refund position. Note that EU consumer withdrawal rights generally do not apply to B2B sales — but if you ever sell to individuals, they do.

Confirmation that the customer owns their content, the licence granted to us to operate the service, and how data can be exported or is deleted after termination. Should cross-reference the Data Processing Agreement.

Any uptime commitment. If there is no SLA, say so plainly rather than leaving it ambiguous.

Limitation and exclusion of liability, and any cap. This is the section most worth paying a lawyer for.

How either side ends the agreement, and what happens to data afterwards.

Which country's law applies and where disputes are heard.

How customers are notified of changes and when they take effect.