Terms of Service
1Parties and acceptance
1.1.The Provider is the individual who owns the Ruby Host service (Telegram bot @rubyhostapp, website https://rubyhost.org).
1.2.Contacting the Provider: the "Support" section of the bot, @rubysupport on Telegram, email support@rubyhost.org. Complaints about server use (abuse) — abuse@rubyhost.org. Support replies within 24 hours.
1.3.Payments in roubles via SBP are collected by a payment service engaged by the Provider; the Customer's banking app may show that service, not the Provider, as the payee. The services under these Terms are provided by the Provider, and all questions should be addressed to the Provider using the contacts in clause 1.2.
1.4.The Customer is a person aged 18 or over with full legal capacity who uses the bot.
1.5.The Customer accepts these Terms by pressing "I accept" in the bot. By accepting, the Customer also agrees to the Acceptable Use Policy (AUP), the Refund Policy and the Privacy Policy (command /terms).
2Subject
2.1.The Provider grants the Customer temporary use of a virtual server (VPS) with the specifications of the selected plan: CPU, memory, disk, port and traffic, location, operating system.
2.2.The rental term is a day, a week or a month, chosen by the Customer, and can be renewed.
2.3.The Provider is not a VPN, website hosting or any other service that the Customer deploys on the server. The Customer is responsible for the content and use of the server.
3Balance and payment
3.1.Prices and the internal balance are denominated in US dollars. The balance is topped up by the methods available in the bot.
3.1.1.When paying via SBP the Customer pays in roubles. The rouble-to-dollar rate is set when the invoice is issued, based on Rapira data. Before payment is confirmed, the bot shows the Customer: the amount to be credited in dollars, the rate applied, the fee and the final amount payable in roubles. An invoice is valid for a limited time; after it expires the rate is recalculated.
3.1.2.Payment method fees are paid by the Customer and shown before payment as a separate line. The fee depends on the method chosen and is stated in the bot before payment.
3.1.3.Current plan prices are published in the bot and on the website https://rubyhost.org and are available without registration.
3.2.Services are prepaid only: the price of the term is debited from the balance when ordering or renewing, and the server is created after the debit.
3.3.The balance is an advance payment for the Provider's services, not electronic money or a deposit. It is paid out in money only in the cases listed in the Refund Policy.
3.4.Prices may change. A term already paid is provided at the price in effect at the time of payment.
4Server delivery
4.1.A server is usually delivered within a few minutes. Login details are sent in the bot.
4.2.If a server cannot be delivered, the debited amount is automatically returned to the balance.
4.3.The IP address is checked for reachability from Russia before delivery. If the address is unreachable from Russia at the time of delivery, the Provider replaces it free of charge.
5Renewal, suspension, deletion
5.1.The bot sends reminders before the term ends. If auto-renewal is on and the balance is sufficient, the term is renewed automatically.
5.2.If the term is not renewed, the server is suspended (powered off). 3 days after suspension the server and all its data are permanently deleted.
5.3.The Provider may suspend a server immediately for an AUP violation, a threat to the infrastructure or other customers, or upon a substantiated complaint (procedure in the AUP).
6Provider's obligations
6.1.Keep the hardware and network running and fix faults within a reasonable time.
6.2.Announce planned maintenance in the bot in advance when it is known.
6.3.Respond to support requests.
6.4.Store server passwords only in encrypted form.
7Customer's obligations
7.1.Comply with the AUP and the laws of the country where the server is located.
7.2.Secure the server: strong passwords, updates, access configuration.
7.3.Back up their own data. The Provider does not back up server contents.
7.4.Respond to the Provider's requests about complaints within the set time.
8Liability
8.1.The Provider's liability is limited to the amount paid for the current term of the server concerned.
8.2.For confirmed downtime caused by the Provider lasting more than 24 consecutive hours, the Customer receives a credit to the balance proportional to the downtime.
8.3.The Provider is not liable for: lost profits and indirect damages; access restrictions imposed by third parties (network operators, government bodies); data loss if the Customer made no backup; consequences of actions of the Customer or of third parties who gained access to the server through the Customer's fault.
8.4.The Provider does not guarantee that an IP address will remain reachable from particular networks in the future: blocks are imposed by third parties. If an address is blocked, the Customer can change the IP in the bot under the plan's rules.
9Changes
9.1.The Provider may change these Terms by publishing a new version in the bot. Continued use of the services after publication means acceptance of the new version. Material changes are announced in the bot in advance.
10Miscellaneous
10.1.Disputes are settled by negotiation: a claim is sent to the Provider using the contacts in clause 1.2 and is reviewed within 10 business days.
10.2.If any provision is found invalid, the remaining provisions stay in force.