Cloud Mac Dedicated Physical Node Rental Terms

OrbVPS provides Cloud Mac systems for remote use. Each active order corresponds to one dedicated Apple Silicon physical node: an exclusive physical machine, not a virtual machine. The node specifications, region, rental period, and selected add-ons together form the order details.

The service includes product information on the website, ordering and node-management features in the console, the hardware listed in the order confirmation, necessary network access, and issue handling through tickets or the support email. It does not include licenses for software installed by the user, third-party development-tool fees, code-repository fees, or equipment and services not listed in the order.

The registrant must have the capacity required to enter into and perform this agreement and must provide truthful, accurate, and reachable account information. When ordering for a team or other organization, the operator must confirm that they have the necessary authorization.

• Information accuracy:Keep the account name, work email, order contact, and billing details current. Update them promptly when anything changes.
• Access security:Users are responsible for protecting login credentials, SSH private keys, VNC credentials, and recovery information. Sensitive credentials must not be placed in public repositories or public build logs.
• Authorized users:Teams may allow members to use a node for legitimate business purposes, but the account holder remains responsible for those members’ actions, software, and network activity.
• Incident reporting:If you discover unauthorized access, exposed credentials, or abnormal control of a node, immediately rotate the relevant credentials and report the incident through a console ticket.

Actions resulting from voluntarily shared credentials, weak passwords, public keys, or failure to promptly revoke access for departing members are treated as actions within the account’s authorized scope unless reliable contrary records exist.

Before ordering, users should confirm the model, region, rental period, and add-ons. The current OrbVPS catalog includes three models: Orb M4 16, Orb M4 24, and Orb M4 Pro. Regions include Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Real-time availability for catalog combinations is determined by the console.

An order enters delivery after payment status is confirmed, necessary risk checks are completed, and a node record is created. The node address, connection method, and service status are provided through the console. After receiving delivery information, users should promptly verify the model, memory, storage, and region.

Console status records show order processing, node activation, renewal, and termination. If the page differs from screenshots saved by the user, the combined result of backend order records, payment records, and node runtime records prevails.

All prices are displayed and settled in US dollars (USD). Available payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateway actually available is determined by the console.

• Order amount:The amount due consists of the selected model, rental period, region, and add-ons and is shown before payment.
• On-chain payment:When using USDT-TRC20, users must verify the network, address, and amount. Losses caused by choosing the wrong network or transferring to the wrong address cannot be automatically corrected through node service records.
• Card payment:Visa / Mastercard / Amex payments are processed through Stripe. OrbVPS retains the order status needed to fulfill the service and does not store complete card details.
• Taxes and fees:Taxes payable by the user under applicable rules, card-issuer fees, and on-chain transfer fees are not node rental charges collected by OrbVPS.

Initiating payment does not mean the order is complete. Wait until the console shows a successful status. For duplicate payments, incorrect amounts, or statuses that remain unchanged for an extended period, retain the order number and payment proof and submit a review through a console ticket.

Nodes are provided for the daily, weekly, monthly, or quarterly period confirmed in the order. Users should check the renewal time and payment status before the current period ends. Renewal success is determined by the new-period record generated in the console.

Changing the model, region, or base hardware may require creating a new node and migrating data; it is not an instant specification switch on the original node. Before confirming a change, users should assess migration needs for repositories, build caches, keys, artifacts, and automation tasks.

Rental periods already underway, completed physical configuration work, and used add-ons are handled according to the order status and applicable rules. A change takes effect only after the corresponding record appears in the console.

Users may use Cloud Mac for lawful software development, automated builds, testing, remote creative work, and model experimentation. Use must not harm other customers, network facilities, node hardware, or third-party rights.

• Do not engage in unlawful activity or store, process, or distribute content prohibited under applicable rules.
• Do not scan, probe, bypass, or attempt to access accounts, devices, networks, services, or data without authorization.
• Do not distribute malicious code, operate malicious traffic, send abusive messages, or use nodes for destructive automated activity.
• Do not continuously consume network capacity, storage interfaces, or external devices in a way that affects facility stability, and do not evade reasonable security restrictions.
• Do not alter hardware identifiers, disassemble equipment, interfere with monitoring components, or attempt to change physical connections or data-center-side configurations.
• Do not use the service to infringe software, code, creative assets, trademarks, trade secrets, or other protected rights.

If OrbVPS detects a clear security risk, abnormal traffic, or activity that may affect facility stability, it may take necessary measures such as restricting connections, isolating a node, or suspending related operations, and may require the user to explain the intended use or complete remediation based on the risk level.

The service objective is not an absolute guarantee for every connection, third-party dependency, or user workload result. Effects caused by the user’s local network, incorrect configuration, credential issues, software failures, unavailable upstream repositories, or user-initiated restarts are excluded from OrbVPS node service interruptions.

When hardware, power, network, or security incidents occur, OrbVPS may perform emergency troubleshooting, including isolating risks, restarting nodes, switching necessary connections, or replacing failed components. The process and recovery outcome are determined by verifiable status records.

For a qualifying service interruption, users must provide the node ID, affected time range, connection tests, and relevant logs after discovery. Once verified, OrbVPS may provide service credit for the corresponding rental period. Credits are not automatically redeemable for cash and do not cover indirect business losses.

Users are responsible for managing code, keys, certificates, provisioning profiles, build caches, build artifacts, models, creative assets, and business data written to a node. A dedicated physical node does not replace version control, off-site backups, or recovery drills.

After the service ends, the node enters an access-revocation and data-processing workflow. Users should not rely on temporary access after service termination to complete migration. Users are responsible for data loss caused by failing to back up, migrate, or verify recovery during the active rental period.

Rights in OrbVPS website branding, page design, product descriptions, operating methods, documentation, and proprietary software belong to OrbVPS or the relevant rights holders. Renting a node does not transfer these rights to the user.

Users retain their rights in code, data, build artifacts, models, and creative assets. To deliver nodes, troubleshoot issues, process orders, and maintain security, the user grants OrbVPS permission to process relevant technical information as necessary. This permission may not be used for purposes unrelated to the service.

User-submitted product suggestions and process feedback may be used to improve the service, but OrbVPS does not thereby acquire ownership of user code, unreleased product plans, or business data. Each party must take reasonable measures to restrict access to and disclosure of non-public architecture, logs, credentials, quotes, and business materials encountered during support.

Before submitting support materials, users should remove personal information, keys, and sensitive business content unrelated to the issue. If a sensitive excerpt is necessary, clearly define its scope and prefer minimal, revocable temporary information.

To the extent permitted by applicable law, OrbVPS’s liability for the service is based on verifiable order, payment, node runtime, and support records. Users should take reasonable steps to mitigate losses, including promptly stopping abnormal tasks, revoking exposed credentials, preserving logs, migrating workloads, and restoring backups.

OrbVPS is not responsible beyond the service scope it controls for losses caused by user configuration, third-party software, external networks, code defects, key management, unauthorized team activity, or failure to perform backups. No limitation of liability excludes or limits liability that applicable law expressly prohibits excluding or limiting.

When making a claim or raising a service dispute, users must notify OrbVPS promptly and provide the order number, node ID, affected time, issue description, verification steps, and evidence of loss. The parties should first review and discuss the matter through the support process.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Any dispute not resolved through discussion will be handled by a court with jurisdiction in that jurisdiction. Mandatory applicable law prevails where it provides otherwise.

OrbVPS may update these terms due to changes in product scope, payment processes, security requirements, or legal obligations. Material changes will be announced through the website, console, or account contact information and will state the effective date of the new version.

Orders confirmed before a change takes effect will generally continue to be fulfilled according to their order records and the rules applicable at that time, except where required by law, necessary for urgent security measures, or separately agreed by the parties. Continuing to order, renew, or use the service after the new version takes effect means that the user accepts the updated terms.

Requests concerning access to, correction, deletion of, or restriction of processing of personal information should also refer to thePrivacy Policy. To protect account and node security, OrbVPS may verify the requester’s relationship to the account, order, or authorization before processing the request.