Terms of service

1. General

1.1. This agreement is between the provider (the owner of the MultiOBX service, the "Provider") and the user of the MultiOBX service (the "User").

1.2. The agreement is accepted at the moment a key is created, time is paid for or the app is first used.

1.3. Data processing is described in the Privacy policy, which forms part of this agreement.

2. Subject

2.1. The Provider gives access to a secure connection service: an app and servers through which the traffic of the User's device is carried in encrypted form.

2.2. Access is tied to a key. The key is created on the website or in the app and does not require a name, e-mail or any other information about the User.

3. Key and devices

3.1. The key is shown once, at the moment of creation. The User is responsible for keeping it. A lost key cannot be recovered, and paid time cannot be moved from it.

3.2. No more than 5 devices can be attached to one key.

3.3. The key can be replaced in the account page no more than once every 30 days. Devices and paid time are kept.

3.4. The User must not pass the key to third parties. All actions performed with the key are deemed to be the User's actions.

4. Prices and payment

4.1. Current prices and terms are listed on the Pricing page and in the account page when choosing a term.

4.2. Payment adds the stated number of days to the key. Days are added to the current term; if the term has already ended, the count starts from the moment of payment.

4.3. There is no subscription with automatic renewal. When the paid days end, access to the connection stops; the key and the account page remain available for adding time.

4.4. Payment is made with a voucher or an order. An order is considered paid once the payment is confirmed by the payment provider or the Provider.

4.5. The Provider may change prices. A change does not affect days already paid for.

5. Refunds

5.1. If within 7 days of payment the service did not work through the Provider's fault and support has confirmed this, the User may receive a refund for the paid period.

5.2. In all other cases paid and unused days are not refunded: the limitations of particular networks and platforms are described on the How it works and How the protection works pages and are not considered a defect of the service.

5.3. Before disputing a payment with a bank (chargeback), contact support. A dispute filed without contacting support leads to the key being disabled.

6. Acceptable use

6.1. The User undertakes to use the service in accordance with the law applicable to them and bears sole responsibility for doing so.

6.2. It is forbidden to use the service for sending spam, attacking networks and systems, distributing malicious software or violating the rights of third parties.

6.3. In case of violation the Provider may restrict or terminate access under the key without a refund.

7. Limitations and liability

7.1. The service is provided "as is". The Provider does not guarantee that the connection works on every network, a particular speed or the absence of interruptions.

7.2. Known limitations (virtual machines on Windows, system requests on Android and iOS, the first seconds after system boot) are described on the website and are not a defect of the service.

7.3. The Provider is not liable for lost profit or indirect losses. The Provider's total liability is limited to the amount paid by the User for the last paid period.

8. Suspension and termination

8.1. The Provider may suspend the service for maintenance, announcing it on the website in advance where possible.

8.2. The Provider may discontinue the service with at least 30 days' notice on the website. In that case paid and unused days are refunded pro rata.

8.3. The User may stop using the service at any time; unused days are not refunded except as set out in section 5.

9. Changes to the agreement

9.1. A new revision is published on this page with its date. Continued use of the service after publication means acceptance of the new revision.

10. Contact

10.1. Support: see the contact on the Help page. Quote an order number or the date the key was created. Do not send the key itself.