Public Offer

1.1. The averisca.cloud service provides virtual game servers accessible via the control panel and SFTP. Available features depend on the selected plan.

1.2. Game servers run on Linux and are isolated in Docker environments.

1.3. Specifications, resources, and limitations of the service are specified in the plan description at the time of ordering.

1.4. Creating an account after confirming agreement with this offer, terms of service, and privacy policy constitutes acceptance of these documents.

1.5. For game hosting, backups created by the user through the control panel are stored for 31 calendar days from creation and then automatically deleted. VPS backups are governed by the separate rule in the “VPS Services” section.

2.1. Services are managed via https://my.averisca.cloud/. Accounts cannot be sold or transferred without prior approval from the service.

2.2. The user independently chooses the server configuration and verifies whether it suits their project needs.

2.3. Support is provided regarding the operation of ordered services and the Averisca infrastructure.

2.4. Modifications, plugins, and other software may be installed provided they do not violate the law, service rules, and infrastructure stability.

2.5. Malware, attacks, flood, spam, phishing, hacking, botnets, and other dangerous activities are strictly prohibited. In case of immediate threat, the service may immediately suspend or terminate the service. Refunds are considered separately according to Section 7.

2.6. Services cannot be used for unauthorized traffic tunneling, resale of DDoS protection, or bypassing third-party system filtering.

2.7. The user may modify startup parameters within the control panel limits. Bypassing established limits, isolation, or technical restrictions is prohibited.

2.8. Test access can be provided no more than once every 24 hours.

2.9. A single user may maintain one account unless otherwise agreed in advance with support.

3.1. The agreement is considered concluded from the moment of acceptance under paragraph 1.4. Provision of paid service begins after payment and activation.

3.2. Disputes are initially resolved by contacting support and negotiations.

4.1. Support requests are accepted in Ukrainian or English via the ticket system or by email at support@averisca.cloud.

4.2. Depending on the severity of the violation, the service may issue a warning, temporary restriction, suspension, or termination of service.

4.3. Warnings may be omitted in cases of attacks, malware, fraud, vulnerability exploitation, restriction bypass, or other immediate threats.

4.4. If access to the user dashboard is lost or blocked, requests may be submitted by email to support@averisca.cloud.

4.5. The content of support tickets is not published without legal grounds or party consent.

5.1. Game servers operate in isolated containers on shared physical infrastructure. CPU, RAM, disk subsystem, and network connectivity of the node are shared among multiple users.

5.2. The CPU or vCore value defines the maximum available limit of processor time, but does not mean granting a separate physical core for exclusive use.

5.3. Short-term use up to the maximum CPU limit is permitted during server startup, world generation, backups, and normal traffic spikes. The plan is not designed for continuous 24/7 utilization of 100% available CPU.

5.4. The service may restrict prolonged or systematic CPU loads close to the maximum limit if they exceed the normal game server profile, reduce shared resource availability, or affect node stability or other services.

5.5. RAM in the plan is the container memory limit, not a dedicated physical memory module assigned to the user. Exceeding the limit may cause process stoppage or restart.

5.6. Disk space is a storage quota. The physical drive and its I/O are shared. The service may limit prolonged intensive read/write operations, mass creation of small files, continuous archiving, or other loads degrading shared storage.

5.7. Network bandwidth is shared and is not a dedicated channel unless explicitly stated otherwise in the plan. Continuous maximum speed utilization, tunneling, proxying, or resale of network resources may be restricted.

5.8. Bypassing limits, isolation, or technical restrictions is prohibited.

5.9. In the absence of an immediate threat, the service notifies the user of the restriction reason and provides an opportunity to optimize the server, change settings, or upgrade to an appropriate plan.

6.1. Attempts to exploit vulnerabilities, bypass isolation, or access unauthorized data are grounds for immediate service suspension.

6.2. The service may refuse a new order or renewal to a user who has violated rules, posed a threat to the infrastructure, or provided false data.

6.3. Already paid services will not be degraded or terminated prematurely without user violation, technical necessity, or other legal grounds.

7.1. Refund requests can be submitted within 14 calendar days after the initial payment. If the service is already activated, the unused period value is refunded. Full refunds are available if the service was not activated or confirmed service faults were not resolved within a reasonable time.

7.2. The service may deny voluntary refunds in cases of confirmed fraud, refund abuse, or gross violations related to service usage. This does not restrict rights that cannot be waived by agreement.

7.3. Bonuses, promo codes, and free credits are non-refundable and cannot be exchanged for cash.

7.4. Approved refunds are processed within 14 business days.

7.5. Requests may be submitted via a support ticket or by email to support@averisca.cloud. The service may request account or payment verification before processing a refund.

7.6. Issues with a specific provider, route, device, or region are not automatically considered a service fault if the server operates normally overall. Each case is investigated individually.

7.7. Refunds are issued to the original payment method when technically feasible. Alternative methods are used only by agreement with the user.

8.1. Paid services are activated after full prepayment.

8.2. Service duration is determined by the plan and account dashboard information.

8.3. For game hosting, the service is suspended after the paid period ends and server data may be deleted after 7 days without recovery. VPS data is subject to the separate 24-hour retention rule in the “VPS Services” section.

8.4. New prices apply to future orders and renewals unless otherwise agreed with the user.

9.1. A VPS is a virtual server running on Averisca physical infrastructure or infrastructure sites used by the service. It is logically isolated from other virtual servers, but this isolation does not mean that a separate physical server is provided.

9.2. The processor, physical RAM, storage subsystem, and network resources of a physical node may be shared by multiple VPSs. Exact parameters are defined by the selected plan and may include vCPU count, RAM, disk or storage, network speed, a traffic limit (if any), IPv4, IPv6, backups, add-on services, and other characteristics shown before ordering.

9.3. vCPU represents the computing resource available to the VPS and is not a separate physical core provided for exclusive use. Prolonged or anomalous load is governed by Fair Use and the VPS Usage Rules.

9.4. The plan RAM value is the maximum memory available to the virtual server. It does not represent the transfer of a separate physical memory module.

9.5. The stated storage amount is the VPS storage quota. The physical storage subsystem is shared, so performance may depend on current shared-infrastructure load. Guaranteed IOPS or MB/s are provided only when expressly stated in the plan.

9.6. Maximum network speed is determined by the plan. Unless the plan expressly says otherwise, network capacity is shared. “Up to 500 Mbit/s” or “up to 1 Gbit/s” means the plan ceiling, not a guaranteed constant 24/7 throughput. A traffic limit applies only if shown in the plan.

9.7. IPv4 and IPv6 are provided for use with the VPS and are not transferred into the user’s ownership. Additional IPs may be a separate paid service. An IP may be changed or withdrawn after service termination, for technical necessity, a security incident, address-resource availability, or other objective reasons; advance notice is provided where reasonably possible.

9.8. Outbound SMTP ports, including TCP/25, may be technically restricted. Unblocking may be requested but is not guaranteed; the service may ask for the intended SMTP use. Having a VPS does not itself guarantee access to TCP/25.

9.9. Backups are included only when stated in the plan or ordered as a separate service. The number, frequency, retention, capacity, and other parameters are defined by the relevant plan or add-on and must be shown before payment.

9.10. After the paid period ends, the VPS is suspended. VPS data is retained for 24 hours from the end of the paid period to allow renewal. After that, the VPS and its data may be deleted without recovery. The service is not required to delete data at the exact second the 24-hour period ends, and any data remaining after that time does not create a guaranteed additional retention period.

9.11. If an order includes a setup fee, its amount is shown before payment. The setup fee covers one-time setup or service preparation. Once the related work has been performed, the setup fee and other completed one-time add-on services may be excluded from a voluntary refund. This does not limit consumer rights that cannot be excluded by agreement.

9.12. Users must comply with the VPS Usage Rules and Abuse Policy. Depending on severity, a violation may result in a warning, temporary restriction, suspension, or termination. For serious or repeated violations, the service may refuse new orders and future renewals. Abuse matters are handled under the separate Abuse Policy.

10.1. The VPS is governed together by this offer, the Terms of Service, the Abuse Policy, and the Privacy Policy. If provisions differ, VPS-specific provisions apply to VPS services and game-hosting rules apply to the relevant game-hosting services.

10.2. Before ordering, the user must be able to view the plan specifications, billing period, setup fee, additional charges, backup terms, and links to the current legal documents.