Review these terms before using a dedicated physical Mac node

SureVM offers dedicated physical Mac mini rentals by the day, week, month or quarter. Each valid order corresponds to the model, node, rental term and add-ons selected by the user. A node is a physical device, not a virtual machine instance sharing compute resources with other accounts.

Services include physical node initialization, delivery of remote access credentials, VNC remote desktop access, administrator privileges, and node status and order management through the console. Within the authorized scope, users may install development tools, run build jobs, manage project files and adjust system settings.

Available configurations include only SureVM M4 Core (M4, 16GB, 256GB) and SureVM M4 Plus (M4, 24GB, 512GB). The specific node, additional storage and Thunderbolt 5 linking options are determined by the configurable catalog shown at checkout.

Users must provide account information that is genuine, accurate and capable of receiving service notifications, and promptly update information that is no longer valid or has changed. When using a team or organization-managed email address, users must ensure they are authorized to represent that organization in creating orders and managing nodes.

Users must protect account credentials, verification codes, remote desktop passwords, private keys and project access tokens. Console accounts must not be shared publicly, and node credentials must not be distributed through uncontrolled channels. SureVM will not ask users to provide remote desktop passwords, private keys or complete payment credentials in ordinary support requests.

Users may allow their employees, contractors or project collaborators to use a node, but must ensure that authorized users understand and follow these Terms. The account holder is responsible for managing authorized users’ actions on the node, resulting charges and any impact caused.

When creating an order, users must confirm the model, node, rental term and add-ons in sequence. Available nodes include Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the US West; the specific combination is based on the console’s real-time availability.

After configuration and payment are completed, SureVM initializes the physical node according to the order. The normal process generally includes order confirmation, payment confirmation, system initialization and credential delivery. The approximately 4-minute estimate shown on the page describes a typical operational process and is not a fixed completion guarantee for every order.

Delivery is complete when the console shows the node as manageable and provides the required access information. After receiving the delivery notice, users should promptly verify the model, memory, storage, node location and rental term. If the delivered service does not match the order, stop nonessential activity and submit a ticket.

1. 1
   Confirm configuration

   Verify the model, node, term, storage upgrade and linking options so project requirements are not confused with the order configuration.

2. 2
   Complete payment

   The USD amount, payment method and order summary shown at checkout are the final confirmation details.

3. 3
   Verify delivery

   After the first connection, check system information, network connectivity and available storage, then update security settings immediately.

All service prices are quoted and settled in US dollars (USD). SureVM supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The available gateway and payment status are determined by the console response.

The checkout page lists the base model, rental term, node, additional storage, Thunderbolt 5 linking and total amount due. Users should verify the order summary before submitting payment. After successful payment, the order is governed by the configuration, term and amount confirmed at checkout.

When using USDT-TRC20, users must verify the network, recipient details and amount due, and bear processing costs caused by selecting the wrong network, entering an incorrect address or making duplicate transfers. For card payments, the payment processor may perform necessary identity, risk and transaction checks.

Taxes, bank fees, on-chain transfer fees and other costs charged by a payment instrument, where payable by the user under applicable rules or the payment method’s requirements, are handled separately from SureVM service prices. SureVM retains transaction records necessary for fulfillment, reconciliation, refunds and dispute handling.

The service term begins when order delivery is completed and ends at the expiration time shown in the order. Daily, weekly, monthly and quarterly nodes are calculated independently according to their respective order terms. Users should review renewal options and the amount due in the console before expiration.

A renewal is confirmation of a new term. Before payment, users should recheck the model, node, add-ons, renewal duration and price. A node without a completed renewal may stop operating after the current paid term ends. Before expiration, users should export code, build artifacts, model files, media projects and other data they need to retain.

A cancellation request does not automatically reverse a completed delivery or a service term that has already begun. Refund eligibility is reviewed for each order based on payment status, whether the node has been initialized, whether the service has been used, the reason for cancellation and applicable rules.

Duplicate payments, system confirmation errors or verified delivery discrepancies may be reported through the console with the order number, payment record and issue details. Where refund conditions are met, the refund will generally be processed through the original payment route or another executable route agreed by both parties. The actual arrival time depends on the relevant payment process.

Users may use Cloud Mac for lawful software development, automated builds, testing, MLX experiments, audio and video processing, and other ordinary computing tasks, but must not use a node for unlawful activity, to undermine service stability or to infringe third-party rights.

The following activities are prohibited:

• Unauthorized access:Scanning, probing, bypassing authentication or attempting to access accounts, networks, devices or data without authorization.
• Malicious code:Creating, distributing or running programs intended to steal data, control devices, extort, damage systems or conceal unauthorized activity.
• Resource abuse:Generating sustained abnormal network traffic, interfering with infrastructure, circumventing reasonable limits or affecting the normal operation of other nodes.
• Rights infringement:Processing protected code, media, models, personal information or other third-party content without permission.
• Fraud and impersonation:Falsifying identity, payment information or service origin, or using the SureVM brand and infrastructure deceptively.
• Resale and uncontrolled sharing:Using a node as an unmanaged public access service without written confirmation, or exposing credentials to unidentified third parties.

SureVM may require users to stop the relevant activity, provide necessary information or take corrective measures based on the level of risk. Where there is an urgent security risk, ongoing attack or apparent unlawful activity, SureVM may first restrict affected connections or nodes and then explain the next steps through an account notice.

SureVM targets 99.9% service availability. All nodes are designed to operate normally 365 days a year. Availability measures whether node infrastructure managed by SureVM continuously provides the agreed remote access and computing capabilities.

The following are excluded from SureVM-responsible service outages: failures of the user’s local network, endpoint device or remote desktop client; inaccessibility caused by the user modifying the system, network, firewall, account permissions or critical services; failures of third-party networks or payment systems; force majeure; and restrictions resulting from misuse, nonpayment or security-risk response.

When determining the scope of an interruption, SureVM will consider node records, infrastructure logs, the user’s reported time and reproducible information. A single remote session disconnection, application error or failed project build does not automatically mean that the physical node was unavailable.

If users cannot connect continuously, they should first check their local network and credentials, then submit the node number, time of occurrence, error symptoms, troubleshooting steps completed and redacted logs through the console. Complete information helps establish the start and end times and the responsible scope.

Eligible service interruptions are calculated based on the affected node, verified interruption duration, corresponding order term and the scope of responsibility defined in these Terms. Users should submit a claim within a reasonable time and provide the order number, node number, time of occurrence, impact description and necessary redacted evidence.

Credits are calculated only against the affected service and do not extend to unaffected nodes, other orders or external systems managed by the user. The specific form and amount will be explained in a console ticket after verification is complete.

To the extent permitted by applicable rules, SureVM is not liable for lost profits, loss of goodwill, lost business opportunities, indirect or special losses, or data loss caused by the user’s failure to establish backup and recovery procedures. Users should maintain independent copies of repositories, build artifacts, model files, media assets and configuration records according to project importance.

SureVM’s liability is limited to losses directly related to the affected service, reasonably demonstrable and caused by an event within SureVM’s scope of responsibility. No limitation of liability excludes or restricts liability that applicable law expressly prohibits from being excluded or restricted.

SureVM may suspend an account, connection or node according to the level of risk if a term expires without renewal, payment is overdue, acceptable use rules are seriously violated, infrastructure security is threatened, third-party rights are infringed or action is required by law.

Where there is no urgent risk, SureVM will explain the issue through an available account contact method or console notice and provide a reasonable opportunity to correct it. If the risk continues, the user refuses to correct it, the violation is serious or immediate action is legally required, SureVM may terminate the relevant service.

Before termination, users should export data they need to retain and revoke team authorizations while access remains available. If no export period can be provided because of a serious security incident, unlawful activity or another situation in which access cannot remain open, SureVM will handle the relevant data according to applicable rules and security requirements.

Users who object to a suspension, termination, payment or credit decision may submit the order number, factual explanation and supporting materials through a console ticket or to support@surevm.com. The parties should first communicate using verifiable records and attempt to resolve the dispute.

These Terms are governed by the laws of the jurisdiction where the platform operator is based. Any dispute that cannot be resolved through discussion must be submitted to a court with jurisdiction in that jurisdiction, unless mandatory applicable law provides otherwise.

SureVM may update these Terms when service features, risk controls or applicable rules change. Material updates will be reasonably announced through the website, console or account notice. Updated Terms apply to new orders, renewals and continued use after their effective date, unless otherwise required by law.