Version 2026-09-11

Hosting provider terms

Operator and contact

Sugar is an independently operated project, not a limited company. Its operator is [TO COMPLETE BEFORE PUBLISHING: operator’s full legal name], using the name Sugar.

Contact: [TO COMPLETE BEFORE PUBLISHING: public contact email]
Correspondence address: [TO COMPLETE BEFORE PUBLISHING: address for legal correspondence]
Country: [TO COMPLETE BEFORE PUBLISHING: operator’s country]

Scope and acceptance

These terms are a template for a written agreement between the Sugar operator and a hosting provider. Connecting a development installation does not itself create a revenue-sharing agreement. Before live billing, both parties must agree the provider’s identity, the addon, percentage, effective date, currency, payment terms and any variations in writing. The admin agreement reference records that agreement; it does not sign on the host’s behalf.

Provider responsibilities

The host supplies the hosting service and sells the Sugar addon to its customers. It is responsible for its checkout disclosures, customer contract, renewals, tax treatment, payments, cancellations, refunds and hosting support. The host must explain that Sugar is a separate integration and must not promise features or service levels the operator has not agreed to provide.

Revenue calculation

The default calculation uses the paid Sugar addon invoice-line amount excluding tax. Each paid addon line, including renewals, receives the percentage agreed for its payment date. Refunds reverse the associated share at the original percentage. Hosting charges are excluded. Amounts remain in their original currency; rounding uses that currency’s minor unit. Any invoice-wide discount or adjustment that changes this basis must be reconciled and agreed before invoicing.

Statements, invoices and disputes

Sugar records confirmed events and prepares statements and invoices for the host’s share payable to Sugar. Test transactions never create live invoices. The agreed payment term applies from the invoice issue date. Report disputed or missing entries before settlement where possible; retain the underlying invoice and refund references so both parties can reconcile them. An invoice is not evidence that payment was received.

Integrations and data

The host must send accurate payment, renewal, refund and service status updates, protect integration credentials, and investigate failed syncs. Both parties must give appropriate privacy information and document their actual controller or processor roles, security obligations, breach cooperation, retention and any required data-processing agreement before processing live customer data.

Ending the arrangement

Either party may request termination in writing, subject to any separately agreed notice period. Agree how existing customers will be informed, recurring addon charges stopped, access ended and outstanding balances or credits settled. Ending the integration does not erase accrued obligations or customer rights. Nothing here excludes liability or statutory rights that cannot legally be excluded.

Platform requirements

Both parties must comply with applicable Discord and hosting platform requirements. This agreement does not grant an exemption from platform monetisation rules. Any required approval must be resolved before the affected paid offering launches.