Recurring Payments Terms

1. General provisions

1.1. These Terms govern the automatic recurring debiting of funds from the User's bank card in favour of the Company for the renewal of the paid services of the Millida platform: the rental of game servers at Millida Hosting, the rental of virtual machines at Millida VDS and other services for which the interface offers a subscription.

1.2. A recurring payment is an automatic repeat debit of funds from a previously linked bank card without the User entering its details again. A subscription is the mode of paying for a service by recurring payments, enabled by the User.

1.3. These Terms supplement the Public Offer (/legal/terms) and the agreement of the service for which the subscription is enabled. In case of a conflict concerning automatic debits, these Terms prevail.

1.4. A subscription is a method of payment, not a separate service. The composition, scope and quality of the service being paid for are determined by the agreement of the relevant service.

2. Enabling recurring payments

2.1. Recurring payments are enabled when paying for a service on the millida.net website and its subdomains, as well as in the Millida Launcher application, by ticking the consent box for these Terms before the payment is confirmed. Without that tick no subscription is enabled and the payment is processed as a one-off.

2.2. By making the first payment with a subscription enabled, the User instructs the Company and the payment provider to store the payment token of the bank card and to use it for subsequent automatic debits under these Terms.

2.3. Bank card details are not stored by the Company. Accepting the payment, tokenising the card and storing payment data are performed by a licensed payment provider (Antilopay) in accordance with its rules and the requirements of the payment systems. From the provider the Company receives only the anonymised token, the expiry date of the card, its payment system and the last four digits of its number — for display in the personal account.

2.4. A subscription is attached to a specific service. If the User pays for several services, the subscription for each of them is enabled and cancelled separately.

2.5. Only the holder of the bank card, or a person acting with their consent, may enable a subscription. Linking a card that the User has no right to dispose of is a breach of these Terms.

3. Terms of debiting

3.1. The amount of each debit equals the price of the renewal period chosen by the User, at the price in force on the date of the debit, in the currency stated when the subscription was set up.

3.2. The frequency of the debits equals the chosen payment period for the service: 1 (one), 3 (three), 6 (six) or 12 (twelve) months, unless another period is offered in the interface for a particular service. The period and the amount in force are shown in the control panel of the service.

3.3. The first debit is made at the moment the subscription is enabled and the service is paid for. Subsequent debits are made automatically on the date the paid period ends.

3.4. No trial period is provided unless expressly stated in the description of a particular service or promotion. Where a trial period is provided, the first paid debit is made on the first day after it ends.

3.5. A subscription runs indefinitely — until it is cancelled by the User or by the Company in the manner established by these Terms and by the agreement of the relevant service.

3.6. A successful debit extends the paid period of the service. If, at the moment of a debit, the service has been deleted, terminated or suspended for a breach, no debit is made and the subscription is cancelled automatically.

4. Informing the User

4.1. The price of the service, the frequency of the debits, the date of the nearest debit and the procedure for cancelling the subscription are communicated to the User before recurring payments are enabled — in the payment interface — and remain available in the control panel of the service for the whole term of the subscription.

4.2. The Company notifies the User of an upcoming debit at least 3 (three) calendar days in advance, and, where the payment period is three months or longer, at least 7 (seven) calendar days in advance.

4.3. Notifications are sent to the email address stated in the account and (or) placed in the personal account. The User must keep their contact details up to date.

4.4. For every debit made, the User is sent a confirmation stating the amount, the service and the billing period; details of the payment are kept in the transaction history of the personal account.

5. Failed debit

5.1. If a debit fails — because of insufficient funds, a block on the card or the expiry of its validity, withdrawal of consent at the issuing bank, restrictions of the payment system or any other reason — the paid period is not extended.

5.2. The Company and the payment provider may retry the debit: no more than 3 (three) attempts within 3 (three) calendar days from the date of the first failed attempt.

5.3. If no attempt succeeds, the subscription is switched off and the service moves to the unpaid state: the consequences — suspension and then termination of the service and deletion of data — are established by the agreement of the relevant service.

5.4. The User may at any time pay for the service manually or link another card; upon a successful payment the subscription resumes with a new billing period date.

6. Cancelling recurring payments

6.1. The User may cancel a subscription at any time and without giving reasons, by any of the following means: — in the control panel of the service, using the automatic renewal switch; — in the personal account, in the section for payment methods and subscriptions; — by contacting support: t.me/MillidaTeamBot.

6.2. Cancelling a subscription stops future automatic debits. The period already paid for continues until it ends.

6.3. Cancelling a subscription is not an application for a refund and in itself does not entail the return of amounts already debited. The refund procedure is established by the Refunds and Chargebacks Policy (/legal/refunds).

6.4. The Company may cancel the User's subscription if the service ceases to be provided, if the User breaches the platform's documents, and if the payment provider or the bank informs the Company that the consent to the debits is invalid.

6.5. A withdrawal of consent to recurring payments addressed to the issuing bank is treated as a cancellation of the subscription from the moment the Company receives the relevant information from the payment provider.

7. Refunds and disputed debits

7.1. Funds debited under a subscription are refunded in accordance with the Refunds and Chargebacks Policy (/legal/refunds), the terms of the agreement of the relevant service and the applicable law.

7.2. If the User considers a debit to be erroneous or unauthorised, they contact support (t.me/MillidaTeamBot) within 14 (fourteen) calendar days from the date of the debit. The period for considering the request is up to 14 (fourteen) calendar days.

7.3. Before applying to the bank for a chargeback, the User must contact the Company's support: in most cases a disputed debit is resolved faster and without the bank's involvement. The consequences of an unjustified chargeback are established by the Refunds and Chargebacks Policy.

8. Changes to the price and the terms of the subscription

8.1. The Company may change the price of the service, the frequency of the debits and other terms of the subscription, having notified the User at least 14 (fourteen) calendar days before the date from which the changes apply to their subscription.

8.2. If the User does not agree with the changes, they may cancel the subscription before the date of the next debit. Continuation of the subscription after that date means agreement with the new terms.

8.3. A reduction of the price, and changes that improve the User's position, apply without prior notice.

How this document is accepted

This document is an offer within the meaning of applicable law and is addressed to an indefinite range of persons.

The document is deemed accepted the moment the User performs any of the following: — ticking the consent box in the platform interface; — completing account registration; — placing an order, a deal, a withdrawal request or a service request; — actually using the relevant service — for documents that do not provide for a separate consent box.

Where acceptance is a distinct action in the interface — a consent box, registration or placing an order — the Company records it in an electronic journal together with the date and time, the document version, the checksum of its text, the IP address and information about the User's software. Such a record is evidence that the contract was concluded and is recognised by the parties as the equivalent of a handwritten signature. An extract from the journal can be requested from support.

For documents accepted by actually using the service, the service usage records themselves serve as evidence of acceptance.

Amendments to this document

The Company may amend this document unilaterally. Amendments do not raise the price or shorten the term of a service the User has already paid for: the paid period is rendered at the price and for the term in force at the time of payment.

A new version is published on the website and takes effect 14 (fourteen) calendar days after publication, unless the version itself specifies a later date. Changes driven by legal requirements, decisions of authorised bodies or payment systems, or by the need to remove a security threat take effect immediately upon publication.

Registered Users are notified of material changes in their personal account and (or) at the email address stated in the account. Posting a notice in the platform interface also counts as notification.

A User who disagrees with the new version may, before it takes effect, stop using the relevant service. Any amounts already paid are refunded only in the cases and in the manner set out in the Refund and Chargeback Policy. Continuing to use the service after the new version takes effect means agreeing to it.

All previous versions are retained and available on request from support; rights and obligations that arose earlier are governed by the version in force when they arose.

Final provisions

Governing law. This document and the relations of the parties are governed by the substantive law of the Kyrgyz Republic, without regard to its conflict-of-law rules.

Pre-court claim procedure. Before going to court, a party must send a written claim through support. A claim is reviewed within 10 (ten) business days of receipt. The pre-court claim procedure is mandatory, except for disputes with a consumer User: for them a claim is recommended but is not a precondition for going to court.

Jurisdiction. Failing agreement, the dispute is to be heard by the court at the Company's location. A consumer User may also bring a claim before the court whose jurisdiction is established by consumer protection law, including the court at the User's place of residence.

Evidence. The parties may rely on records of the Company's information systems — operation logs, the ledger of funds movement, message and order history, the document acceptance journal — as evidence. The Company ensures the integrity of these records by recording their time, version and checksum. The User may submit any evidence, including screenshots. Evidence is assessed under the rules of the applicable procedural law.

Language of the contract. The contract is concluded in Russian. Where translations into other languages exist, the Russian text prevails.

Severability. If a particular provision is held invalid or unenforceable, the remaining provisions stay valid; the invalid provision is to be replaced by a valid one closest to it in meaning.

No waiver. The Company's failure to exercise a right does not mean waiving it and does not prevent exercising it later.

Assignment. The Company may transfer its rights and obligations under the contract to an affiliate or a successor upon reorganisation, having notified the User. The User may not transfer its rights under the contract to third parties without the Company's written consent.

Legally significant messages. The parties recognise the legal force of messages sent to the email address stated in the account, through the personal account and through official support channels. The User must keep contact details up to date; the risk of not receiving a message sent to outdated details lies with the User.

Entire agreement. This document, together with the other platform documents, constitutes the entire agreement of the parties on the subject matter and supersedes all prior arrangements.

Survival. The provisions on liability, indemnity, confidentiality, intellectual property, dispute resolution and financial obligations survive termination of the contract.

Company details: Market Link LLC, registration number 303671-3301-OOO, taxpayer number 01605202410603, Russian taxpayer number 9909692242, registered address: Kyrgyz Republic, Bishkek, Sverdlovsky district, 62 Kievskaya street. Support: t.me/MillidaTeamBot.