Cloud Bots Terms of Service
Last updated: September 29, 2026
Applies to: partners connecting Cloud Bots on the AdaptGroup platform.
1. General
Cloud Bots is provided by AdaptGroup LLC, registered in Wyoming, USA (the "Company"), as part of the AdaptGroup platform (the "Platform").
The module enables a partner to sell server infrastructure services through a Telegram bot under its own branding. Available resource types, plans, and actions are determined by the catalog and Platform settings. Mention of a service in these terms does not mean it is available in every location or plan.
The partner manages the bot's presentation, available sales settings, and interactions with its customers. The Company provides server infrastructure and Platform functionality. Administration of the customer's operating system and applications is not included unless separately agreed.
2. Related Documents
Connection to and use of the module are subject to the Platform terms and this document. Ordered resources are also subject to:
- Infrastructure Terms — resource provision, payment, renewal, and termination of rental.
- AUP — acceptable use, complaints, and restrictions.
- SLA — server availability and compensation.
- DPA — processing personal data on the customer's behalf, where applicable.
- Copyright Complaints / DMCA Policy.
General account and organization rules are set out in the Platform Public Offer and Organization Terms. Processing for the Platform's own purposes is described in the Privacy Policy.
These terms govern Cloud Bots orders and payments; the Infrastructure Terms govern rental. The partner must not promise terms on the Company's behalf that have not been agreed with it. Mandatory rights under applicable law remain unaffected.
3. Bot Connection and Management
The partner connects its Telegram bot using a token obtained through BotFather and manages available settings in the Platform dashboard.
The partner is responsible for safeguarding the token, access to its Telegram account, and the permissions of organization members. If compromise is suspected, the token must be replaced and support notified. Changes to the token or settings outside the Platform may interrupt the bot's operation; such a change is not, by itself, a violation of these terms.
The partner's text, images, links, and broadcasts must comply with the law and Telegram's rules. Customers must not be misled about the seller, resource specifications, price, or service terms.
4. Catalog, Prices, and Customer Information
The partner selects available offerings and sets prices within Platform settings. Resource costs to the partner, applicable fees, and payment terms are displayed in the dashboard.
Before ordering, the customer must have access to the resource specifications, location, rental term and price, renewal terms, included IP addresses and traffic, additional service charges, and material restrictions. The partner provides access to the applicable service terms and its support contacts.
Displayed availability reflects resource stock at the time of calculation and is not a reservation. Fulfilment is checked when the order is processed.
Virtual CPUs and CPU share do not mean dedicated physical cores unless that service is expressly offered and actually provided. The partner must not promise automatic backups, unlimited bandwidth, or features not included in the chosen service.
Infrastructure price changes and renewal prices are governed by the Infrastructure Terms. The Company announces price increases at least seven days in advance in the Telegram channel @adapt_cloud_alert. A new price does not alter the cost of an already paid period. The partner must take account of these notices and communicate applicable changes to customers.
5. Balances and Partner Income
Customer balance funds and partner income are accounted for separately. A customer balance top-up is not, by itself, partner income and does not constitute a server purchase or renewal.
When a paid order is placed, the corresponding amount is deducted from the customer's balance on the terms shown to them. Partner income is generated from completed transactions, taking account of infrastructure costs and applicable fees. Amounts associated with incomplete or disputed transactions are not treated as finally earned income.
Available bot income may be transferred to the organization's balance within Platform functionality. Subsequent withdrawal follows the Platform's general terms; current limits and fees are displayed in the dashboard.
6. Order Fulfilment and Renewal
Order acceptance and deduction of funds do not mean that the server is ready. Preparation is a separate step; the result and access to the delivered resource are provided after completion. Dedicated servers may require manual preparation.
The start of the paid period, consequences of non-payment, and resource release deadlines are governed by the Infrastructure Terms. Waiting for preparation must not be presented as successful delivery.
The customer must check the order specifications and information required to configure access. Resource changes, reinstallations, deletions, and other actions are performed only within available functionality and may cause a restart or data loss. The consequences must be clear to the user before an irreversible action.
Automatic renewal applies only where the feature exists and is enabled. Renewal requires successful payment; having funds without a completed renewal does not extend the rental term. Separately billed IP addresses may have their own expiry dates, different from the server's.
Reminders help manage payments, but their receipt is not a condition for rental expiry. The partner must enable the customer to see the current payment deadline and resource status.
7. Errors and Refunds
If a resource has not been provided and non-fulfilment is confirmed, the amount charged must be returned to the balance used to pay for the order. Confirmed erroneous or duplicate charges must also be corrected. A refund to an internal balance and withdrawal from the Platform are distinct operations; mandatory legal requirements concerning the refund method remain applicable.
A timeout, missing notification, or interface error does not, by itself, prove that an operation failed. Where the outcome is uncertain, order status and resources actually provided are checked first. Until the outcome is established, the partner must not make unverified claims that the order has completed or been cancelled.
Voluntary cancellation of a properly provided service after use does not entitle the customer to a refund for the remaining period, except where required by law. Unavailability compensation is governed by the separate SLA, and the consequences of violations by the AUP.
8. Support and Violations
The partner provides its contacts to customers and handles enquiries about ordering, payment, and use of the bot. Infrastructure issues and Platform technical errors are referred to Company support with an order or resource identifier and a description of the problem. Customers may also use the Company's general support contacts.
The partner must forward resource-related violation notices and remediation requests to the customer, must not conceal restrictions, and must assist with complaints. Restrictions are governed by the AUP and Copyright Complaints Policy; there is no guaranteed number of warnings.
The server SLA is not a separate availability guarantee for Telegram, the bot, or a payment service. However, interface unavailability does not, by itself, cancel the Company's obligations for infrastructure already provided.
9. Data and Resource Access
To handle orders, the Platform processes necessary user, balance, order, and resource information. The partner must use data available to it lawfully, inform customers about processing and transfers, and restrict staff access.
Sending data to the Platform does not replace the necessary legal basis for processing. The parties' roles regarding data in hosted applications depend on the actual circumstances and the DPA, not merely on the order having been placed through a bot.
Passwords, SSH keys, and console links must be used only for authorized access. Selling a resource through a bot does not give the partner or the Company an unrestricted right to inspect the customer's files or operating system contents. Access is governed by the Infrastructure Terms and DPA.
10. Disconnection and Changes to Terms
Disconnecting the bot or losing access to it does not cancel accepted orders, existing obligations, or resource payment deadlines. Before disconnection, the partner must inform customers about continued service and resolve incomplete operations through support. Resources are not assumed to transfer automatically to another bot or integration.
Changes to these terms are published in Platform documentation. Price changes follow the notification requirements and protection of paid periods specified in the Infrastructure Terms.
11. Contacts
- Support: [email protected], @adapt_support.
- Abuse complaints: [email protected].
- Partnership and business proposals: [email protected].
AdaptGroup LLC
30 N Gould St Ste R, Sheridan, WY 82801, USA.