This is an editable starting point. Operator identity, dates, retention periods, and product-specific rules still need to be supplied.
The service and its operator
This is editable starter content, not a completed service agreement. Add the operator’s identity, what the service provides, eligibility requirements, an effective date, and the rules appropriate to your deployment.
Accounts and access
Use a sign-in method you control and keep authentication details private. The operator must describe account restrictions, cancellation procedures, and the handling of misuse. Add rules for user content or uploaded files if the product accepts them.
Subscriptions and payments
The template itself is shared for free. The pricing page demonstrates plans for a product built with it. Prices, billing intervals, renewal terms, cancellation, and refunds must match the operator’s published offer and actual payment configuration.
When the deployment uses a payment provider’s test environment, test transactions do not represent a real purchase. A display label alone does not determine whether the backend uses test or live credentials.
Credits and invitations
Credits are used inside the product. The operator must publish their uses, any expiry rules, and the conditions for invitation rewards. Product credits are distinct from third-party affiliate commissions and should not be presented as a cash balance.
Support and changes
Use the contact page to find published support channels. Add your actual support scope, change-notice process, dispute handling, and other relevant terms before publishing this as a finished agreement.