Legal

Terms of Service

Understand the rental terms before moving your project to a remote Mac. Learn what your purchase includes, how billing works, and what each party is responsible for.

Applies to orders and renewalsCheck the billing period in your order confirmation

  1. 1. Service scope
  2. 2. Accounts and eligibility
  3. 3. Billing and payment
  4. 4. Renewals, expiry & data
  5. 5. Acceptable use
  6. 6. Software, certificates & your responsibilities
  7. 7. Availability & notifications
  8. 8. Liability & issue resolution
  9. 9. Changes & disputes
Console

1. Service scope

VPSOmni provides remote access to physical Mac mini computers powered by Apple Silicon M4 or M4 Pro. For the rental term, the entire physical machine is dedicated to one customer. It is not a virtual machine, and its system, memory, and local storage resources are not shared with other customers. You receive the right to use the machine remotely for the agreed term, not ownership of the hardware.

The service provides access to the macOS graphical interface and command line for development, compilation, simulator testing, build tasks, and compliant model experiments. Connection details for the browser, remote desktop, and SSH are available in your instance details after you sign in to the console. Keep your credentials secure; do not publish instance details or connection keys.

The service catalog offers three machine tiers. Your confirmed order determines the delivered configuration. Remote access does not provide direct connections to local peripherals. If your workflow depends on physically connecting an iPhone, low-latency audio/video monitoring, or other local peripherals, first check that it can be completed remotely. Renting a machine does not include third-party developer eligibility, software licences, or a guarantee of app review approval.

2. Accounts and eligibility

You must be legally able to enter into and fulfil a service agreement. If you order on behalf of a team or organisation, you must have the necessary authorisation. Information used to register and place an order must be accurate and kept up to date. Keep your contact email accessible so you can receive verification, order, and service notifications.

You are responsible for securing your console account, email, password, and instance connection details, and for managing access for authorised users. Do not share your account with unauthorised people or publish credentials. If you notice a suspicious login, exposed credentials, or unauthorised activity, report it promptly through a console support ticket and replace the affected credentials.

Orders, payments, and usage records associated with your account help verify service status. For account ownership questions, payment disputes, or changes to sensitive settings, we may ask for information relevant to the request. Never send passwords, complete private keys, or full payment card details by email.

3. Billing and payment

Billing periods are available by the day, week, month, or quarter, and all charges are in US dollars (USD). Your order combines the machine, node, billing period, storage upgrades, and any other add-ons. Review each item and the total before paying. The catalog helps you choose a configuration; availability is determined by the live status returned by the console, and the final charge is the amount shown in the checkout details you confirm.

Daily billing suits project testing or short-term tasks. If you already know you need ongoing development, a weekly, monthly, or quarterly term may be a better fit. A longer term means purchasing more time upfront; it does not mean you can split the charge into hourly usage. The console records determine the service period, start and end times, and order status. Not connecting to the machine or running tasks does not pause billing.

We accept only USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe. Available payment gateways are determined by the response from our backend. For USDT-TRC20, check the network, recipient details, and amount due. For card payments, complete the verification on the payment page. A transfer screenshot alone does not confirm payment. If a payment issue occurs, submit a support ticket with your order number and transaction reference.

If you have questions about an invoice item, cancellation terms, or refund eligibility, contact support before paying. We do not guarantee an unpublished refund timeframe or a uniform refund outcome. We will review each case based on the order status, what was delivered, and the applicable terms.

Choose a configuration and rent a Mac

4. Renewals, expiry & data

Service stops when the term expires unless you renew. To continue, check the expiry time in the console and complete the renewal, then verify the payment and new service term. Submitting a renewal request, opening the payment page, or receiving a payment verification prompt does not mean the renewal is complete. Check the updated order and instance status in the console.

Before expiry, export your projects, build artifacts, signing materials, configuration files, and any other data you need to keep. Verify that your backups work in your own storage. The remote machine should not be the only copy of important files. Once service stops at expiry, do not assume you will still be able to connect, make a backup, or restore the previous environment.

Service reclamation includes erasing data on the machine and preparing it for reassignment. This page does not promise an unpublished fixed retention period, a specific time by which erasure will be complete, or a data recovery window. If you need a handover, confirmation of deletion, or have compliance requirements, raise them in a console support ticket before expiry and confirm the arrangements. Data erased during reclamation cannot be used as a recoverable backup.

5. Acceptable use

You may use the service only with proper authorisation and in accordance with applicable rules. Do not use a node for unauthorised access, attacks, distributing malware, stealing credentials, fraud, distributing infringing content, or other unlawful activity. Do not disrupt networks, damage service infrastructure, or attempt to access non-public data belonging to other customers or the platform.

Scanning, testing, automated access, and bulk tasks must be authorised and comply with the target system's access restrictions. Having an entire machine to yourself does not permit you to place unlimited load on external networks. You are responsible for confirming that you have the rights to use the code, datasets, models, media, and programs you run.

If there is a clear security risk, evidence of a policy violation, or a valid request from an authorised authority, we may restrict connections, suspend, or terminate service in proportion to the risk. Where we can notify you without increasing the risk, we will explain the action and how to request a review. You may use a console support ticket to provide proof of authorisation, explain your use, or dispute the action taken.

6. Software, certificates & your responsibilities

You are responsible for obtaining any developer eligibility needed to develop, sign, distribute, and submit apps for review, as well as valid licences for your software, plugins, models, and media. The physical Mac rental fee does not include these qualifications or licences, nor does it change the requirements third-party platforms apply to projects, content, and distribution.

Protect signing certificates, private keys, provisioning profiles, repository credentials, and access tokens according to the principle of least privilege. Never expose secrets in public repositories, build logs, or support tickets. When a task is complete, revoke tokens you no longer need, remove temporary access, and export any signing materials you need to keep before expiry.

You are responsible for changes to your environment, including installing software, adjusting system settings, deleting files, and running scripts. Before deleting, resetting, or taking another irreversible action, verify the target and make a backup. Build success, signature validity, and app review approval also depend on your project code, tool versions, authorisations, and third-party review rules; troubleshoot each separately.

7. Availability & notifications

All nodes operate year-round, 365 days a year. Service availability depends on the physical node, the remote access connection, and your project itself. Your local network, routing between networks, client settings, or project errors may each affect the connection or task results.

If you experience a connection outage or other issue, note your order number, node, when it occurred, connection method, and error message, then submit a console support ticket. If another connection method still works, include that information too. These details help identify whether the issue is at the network, system, or application level. Do not expose connection credentials while troubleshooting.

Notifications about instance status, service changes, or security actions are sent to the email address linked to your account or discussed through console support tickets. The impact, progress, and next steps depend on the findings of our review. These terms do not specify a fixed recovery time or automatic compensation multiplier. Submit your order records for review of a specific service issue.

8. Liability & issue resolution

We are responsible for providing the dedicated physical Mac remote access service specified in your confirmed order and addressing issues within the scope of service delivery. You are responsible for your project content, usage authorisations, account security, and independent backups. Issues caused by events beyond reasonable control, your actions, or third-party systems should be assessed based on their actual cause, not just where an error appears.

If you believe the service does not match your order or an issue has caused a verifiable impact, keep your order records, error messages, and relevant timestamps, and submit a support ticket promptly. We will review the delivery, cause of the issue, and records provided by both parties, then discuss the appropriate resolution. Do not destroy important records or repeatedly perform irreversible actions before the issue has been reviewed.

The extent of any loss, available remedies, and allocation of responsibility are determined by applicable law, valid order terms, and the evidence. Nothing in this section excludes or limits liability that cannot be excluded or limited under applicable law. App review outcomes, commercial returns, and third-party platform status are not service delivery criteria.

9. Changes & disputes

We may update these terms to reflect changes to the service, payment processes, or compliance requirements. We will provide information before changes to prices, service scope, or the parties' key rights and responsibilities take effect. Read the terms shown when placing a new order or renewing, and keep your order confirmation. The terms agreed when an order was placed and applicable law will govern how that order is handled.

These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises, the parties should first try to resolve it using order records and support channels. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction.

For questions about these terms, order reviews, or disputes, email support@vpsomni.com; for an existing order, we recommendsigning in to the console and submitting a support ticketso we can link it to your instance and payment records. Include a brief summary of the issue and your order number. Do not attach passwords, complete private keys, or full payment card details.