Legal

Terms of Service

Review the rental period and data responsibilities before you begin. These terms apply to orders, delivery, and use of dedicated physical Macs from OsxNode.

Version 1.0 Effective October 21, 2026

  1. 1. Service scope
  2. 2. Pricing & terms
  3. 3. Provisioning & delivery
  4. 4. Expiration, shutdown & data
  5. 5. Acceptable use
  6. 6. Uptime & credits
  7. 7. Refunds
  8. 8. Liability & changes
Go to Console

1. Service scope

OsxNode provides cloud Mac rentals for set terms. The only model currently available is the OsxNode M4-16: Mac mini M4, 16 GB unified memory, and 256 GB SSD. Each device is assigned to one customer for the rental term. It is a dedicated physical machine, not a virtual machine, and its unified memory and GPU cores are not shared with other customers.

Available physical nodes are in Singapore, Tokyo, Seoul, and Hong Kong. Model and node availability is shown in real time in the Console. You can use the macOS graphical interface and command line, open a browser-based remote desktop from the Console after signing in, or configure VNC or SSH using the connection details provided.

The service provides the right to use the device; it does not include device ownership, model-weight licenses, software purchases, or managed operations. You are responsible for preparing and installing the tools, models, and data you need. Larger unified-memory configurations are not currently available. An additional SSD expands storage, not unified memory, and will not resolve insufficient memory for running a model.

2. Pricing & terms

Rentals are prepaid by the day, week, month, or quarter, and all orders are billed in US dollars (USD). The table below lists base rental prices for the OsxNode M4-16, excluding optional add-ons. The amount due and the term dates and configuration are confirmed at checkout and recorded in your order.

OsxNode M4-16 base rental prices
Model Daily Weekly Monthly Quarterly
OsxNode M4-16 $21.6/day $58.2/week $107.8/month $293.2/quarter

Payment is accepted only via USDT-TRC20 and Visa / Mastercard / Amex (through Stripe). Available payment gateways are determined by the response from the backend. For USDT-TRC20, verify the network, receiving address, and amount due. For card payments, rely on the gateway confirmation; closing the browser page or having a payment screenshot does not confirm that an order is complete.

Your node shuts down when the rental term expires unless you renew, and no further rental charges accrue. To keep tasks running, renew before expiration and check the new expiration time. Initiating a payment, contacting support, or expressing an intent to renew does not mean the renewal is complete.

Choose a rental plan

3. Provisioning & delivery

Your node is provisioned on the same day after payment is confirmed. Delivery is complete when the corresponding node and connection credentials appear in the Console. Before paying, check the model, node, billing term, and add-ons. After payment, sign in to the account used to place the order and check its status; the time you initiated payment alone does not mean the device is ready.

If payment requires manual verification, or the order cannot be matched to the payment record, submit a support ticket through the Console with your order number and proof of payment. For USDT-TRC20 orders, you can provide the transaction hash; for card orders, provide the order identifier from your payment record. Never share your full card number, security code, account password, or private key. Updates during verification will be provided through the order or support ticket; no fixed processing time in minutes is promised.

Once you receive your credentials, check the remote connection, specifications, and rental dates, then change the initial password. If you cannot connect or the delivered configuration differs from your order, save the error details and submit a support ticket promptly. See the connection guide for requirements for the browser-based remote desktop, VNC, and SSH. The service does not include audio streaming or direct USB device access.

4. Expiration, shutdown & data

If your rental term expires without renewal, the node shuts down automatically. You will no longer be able to use it through remote desktop or SSH, and running inference, builds, downloads, and other processes may be interrupted. Plan tasks around the expiration time shown in the Console and back up your models, datasets, experiment results, and custom configurations to your own storage before expiration.

Shutdown is not a backup and does not mean your data will be retained indefinitely. No standard post-shutdown data retention period is currently specified, so do not assume there is a recovery grace period after shutdown. If a specific order includes an explicit data retention arrangement, that written agreement applies. Otherwise, plan your backups on the assumption that data cannot be retrieved after expiration.

After the rental term ends, the device is reclaimed through disk erasure and system reinstallation before it is prepared for another customer. We do not guarantee recovery of erased files. Back up user files on both the base and any additional storage. Do not rely on placing a new order, paying afterward, or sending an email to stop data deletion once it has begun.

For details on data handling, see the Security & Availability. If you need more time, renew through the Console during your current rental term rather than waiting until shutdown to request the recovery of tasks or files.

5. Acceptable use

You must ensure that you have the necessary rights to any software, models, and data you upload, download, run, or distribute, and that your use complies with applicable laws. You may not use the service for mining, bulk unsolicited email, attacks on others' systems, distributing malware, stealing credentials, unauthorized scanning or network interference, or other activities that infringe third-party rights.

You are responsible for managing your Console account, remote desktop password, SSH keys, and any software you install. Do not disclose connection credentials or share access with untrusted third parties. If credentials are exposed or you notice unusual access, change them promptly and report the issue through a support ticket. Apply appropriate access restrictions to any ports you open and services you run.

If we detect prohibited use or an active security risk, OsxNode may immediately restrict connections or shut down the node to prevent further harm, then determine next steps based on the facts. Shutdown does not release you from responsibility for your actions. You must cooperate by providing relevant information about the issue, but do not send sensitive data through public channels.

6. Uptime & credits

We commit to 99.9% service availability, equivalent to about 43 minutes of downtime over a 30-day period. This is a service commitment, not a report of historical monitoring results. All nodes operate year-round, 365 days a year. For availability calculations and service credit terms, see the Security & Availability.

Downtime beyond the allowance is converted into account credit in proportion to the service fee for the current term. Submit a request through a Console support ticket during that term, including the node name, order number, downtime start and end times with time zone, and any connection errors or logs that may help with verification. Account credits are not cash refunds.

Downtime caused by your actions, account or credential misconfiguration, your network connection, or circumstances beyond reasonable control is assessed based on the actual cause and is not automatically treated as platform-caused downtime. A model exiting due to insufficient memory or an issue with software you installed does not, by itself, show that the physical node was unavailable. If you have questions, submit relevant records for review through a support ticket.

7. Refunds

Once provisioned, service is provided for the prepaid term you selected. Finishing an experiment early, stopping tasks, or not logging in during the rental term does not automatically change the order to hourly billing or entitle you to a refund for unused time. Choose a term that fits your experiment before paying.

For duplicate payments, provisioning not completed after payment, a configuration that differs from what was ordered, or other billing issues requiring review, request a refund through a Console support ticket. Include the order number, payment record, details of the issue, and the resolution you are requesting. Provisioned orders are reviewed against delivery and usage records; submitting a request does not mean a refund has been approved.

Refund eligibility, amount, and process depend on the order details, applicable law, and the outcome provided in writing through the support ticket. These terms do not promise a standard refund processing time or unconditional refunds. Requests for downtime covered by the availability commitment are handled under the account credit policy in Section 6 and should not be treated as refund requests.

8. Liability & changes

OsxNode provides the physical device, connectivity, and rental term specified in your order. We do not guarantee that a particular model will load, achieve a specific inference speed, or produce a particular experimental result. Assess suitability based on the 16 GB of unified memory and your actual workload; quantization, context length, and concurrent tasks all affect memory use.

You are responsible for maintaining restorable backups and for the software you deploy, data licensing, and access configuration. Platform liability is assessed based on actual performance, the cause of any issue, and applicable law. These terms do not exclude or limit liability where doing so is prohibited by law, or retroactively reduce rights attached to confirmed orders through later updates.

When these terms change, we will update the version and effective date on this page. New orders are subject to the terms confirmed at checkout. Any material change affecting existing orders will be explained in an order notice or written confirmation between the parties. If you have questions about pricing, data deletion, or usage restrictions, confirm the details through a support ticket before ordering or renewing.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Disputes should first be discussed through support. If no resolution is reached, they will be handled by a court with jurisdiction in that same jurisdiction. For questions about these terms, email support@osxnode.com. For questions about a specific order, refund, or service credit, sign in to the Console and submit a support ticket so we can verify your account and order records.