Review delivery, usage, and data responsibilities before enabling your Cloud Mac

By visiting this website, creating an account, placing an order, completing payment, or beginning to use a physical node delivered by VMArm, you confirm that you have read, understood, and agreed to these terms and related policies. Anyone acting for an organization also confirms that they are authorized to accept these terms and manage orders on the organization’s behalf.

If you do not agree to the current terms, stop creating orders or using the node. Viewing public content alone does not mean VMArm has accepted a purchase request; the service relationship is established by the order details, payment confirmation, and node delivery records together.

VMArm provides Cloud Mac dedicated physical machines powered by Apple Silicon. Each valid order corresponds to an independent physical node in the selected configuration, with resources not shared with other orders through virtual machines. Delivery is based on the model, memory, storage, node region, add-ons, and rental term confirmed in the order.

The current catalog includes VMArm M4 Core (M4, 16GB, 256GB) and VMArm M4 Plus (M4, 24GB, 512GB). Available nodes are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West. Catalog combinations are normally orderable; real-time availability is determined by the portal.

The service does not include third-party software licenses, code repository access, signing materials, business data migration, or app publishing operations not specified in the order. You are responsible for confirming that your project dependencies and software licenses meet the relevant provider’s requirements.

Before placing an order, verify the contact details, model, node, billing term, additional storage, and daisy-chain quantity. After payment is confirmed, the system begins node allocation and initialization. A typical order takes about 4 minutes from payment confirmation to connection details being generated.

1. About 1 minute
   Payment confirmation

   Verify the order amount, payment status, and corresponding order ID.

2. About 1 minute
   Node allocation

   Match a dedicated physical node to the selected model and region.

3. About 1 minute
   System initialization

   Prepare the system environment and verify basic access status.

4. About 1 minute
   Connection details generated

   Provide the node address, account information, and next-step access in the portal.

About 4 minutes is the typical process time and is not a guaranteed completion time for every order. If order details conflict, payment cannot be matched automatically, risk signals require review, or the configuration needs confirmation, VMArm may conduct a manual review and request the necessary information through a portal ticket or support email.

All fees are charged in US dollars (USD). Supported payment methods are limited to USDT-TRC20 and Visa, Mastercard, or Amex (via Stripe). Actual gateway availability is determined by the backend response at checkout.

Actual prices for the model, term, and add-ons are based on theplan pageand checkout confirmation shown before the order is submitted. Before paying, verify the order amount, currency, payment network, recipient details, and order ID. For issues caused by selecting the wrong network, entering incorrect information, or making duplicate payments, submit verifiable transaction records through a support ticket.

An order enters delivery only after its payment status is confirmed and matched to the corresponding order. Payment processors may perform necessary verification for transaction security; VMArm processes only the information required to confirm, deliver, and reconcile the order.

Node usage rights are calculated by the day, week, month, or quarter confirmed in the order. A renewal takes effect only after you confirm it and the associated payment status is valid. Before the current term ends, check the expiration time in the portal and allow reasonable time for payment confirmation and data migration.

When a term ends without a confirmed renewal, node access may be stopped. Do not treat post-expiration access as a data retention solution or rely on a single backup made near expiration. Important code, build artifacts, certificates, and business files should be stored continuously in an independent location.

Submit cancellation requests through a portal ticket, specifying the order ID, cancellation scope, and preferred handling time. Terms already started, node resources already delivered, and add-ons already enabled will be reviewed based on the order status and actual performance. A cancellation request does not automatically reverse confirmed payments or completed delivery.

Within the scope of lawful authorization, you may use the node for iOS, macOS, and visionOS development, Xcode builds and archiving, TestFlight upload preparation, CI/CD self-hosted runners, Unity iOS builds, and local model experimentation.

You must not use the node to carry out or assist with any of the following:

• Unauthorized access:Scanning, attempting to enter, or controlling systems, accounts, networks, or data without authorization.
• Malware distribution:Creating, deploying, or distributing programs that damage systems, steal information, or bypass security controls.
• Network resource abuse:Launching attacks, sending bulk unsolicited messages, or continuously consuming resources in a way that affects other services.
• Rights infringement:Storing, creating, or distributing content that infringes intellectual property, privacy, or other lawful rights.
• Node security threats:Bypassing access controls, tampering with audit records, interfering with security detection, or changing hardware connections without authorization.
• Reselling access:Reselling node connection credentials or control as a standalone service without written confirmation.

If conduct may endanger a node, network, or other users, VMArm may take necessary measures, including restricting access, preserving logs, requiring remediation, or terminating the relevant order. Measures will reflect the scope and urgency of the risk and verifiable records, with portal notification to the order administrator whenever possible.

You must protect portal login details, system accounts, VNC credentials, signing certificates, access tokens, code repository keys, and runner registration information. Credentials must not be shared through public documentation, unencrypted messages, or build logs accessible to unrelated people.

Organizations should assign access according to least privilege and promptly revoke permissions, update passwords, and rotate tokens when a member leaves a project, responsibilities change, or credentials may have been exposed. Sharing one set of long-term credentials weakens traceability; create distinct accounts and audit records for different roles.

Actions completed with valid credentials are generally treated as authorized account actions. If you discover an unusual login, unknown build task, exposed connection details, or an unexpected configuration change, immediately end the relevant session, update the credentials, and submit a portal ticket with the order ID, discovery time, and steps taken.

You are responsible for code, build artifacts, signing materials, dependency caches, model files, and business data uploaded, created, compiled, or stored on the node. You must ensure that you have the authorization required to process this content and establish an independent backup and recovery plan appropriate to the project risk.

The node’s working directory should not be your only copy of data. We recommend keeping code in a controlled repository, syncing build artifacts to independent storage, storing certificates and recovery materials in access-isolated locations, and regularly verifying that backups can actually be restored. Caches can be rebuilt and should not be covered by the same backup strategy as irreplaceable source data.

Before cancellation, expiration, migration, or configuration changes, export your data and verify the copies. You are responsible for losses caused by deletion, faulty scripts, credential exposure, failure to back up, or failure to verify the recovery process.

VMArm nodes operate continuously 365 days a year. Continuous availability may still be affected by network incidents, hardware failures, security risks, your own actions, upstream infrastructure incidents, or events beyond reasonable control.

VMArm may perform necessary security updates, access restrictions, or incident response to fix critical vulnerabilities, maintain system security, or restore an affected node. When the impact can be assessed in advance, the portal will provide the scope, recommended actions, and status updates; for emergencies that cannot be predicted, VMArm will prioritize risk control and update the record once verifiable information is available.

If the original node can no longer meet security or stability requirements, VMArm may propose a necessary migration plan. You must cooperate in confirming connection details, migration timing, and data readiness. Before migration begins, you must independently preserve your code, certificates, build artifacts, and critical business data.

Your own configuration, third-party dependencies, code defects, external repository status, local network, and client behavior are not part of physical-node availability itself. When investigating an issue, both parties should use node status, connection tests, system logs, build logs, and timestamps to determine responsibility.

Each party is responsible for its conduct regarding order performance, credential management, data backups, and lawful use. For issues attributable to service delivery, VMArm will act based on order records, node status, and verifiable impact; it is not responsible beyond applicable requirements for losses caused by user configuration errors, unauthorized actions, third-party service failures, local networks, events beyond reasonable control, or failure to maintain independent backups.

For a service claim or dispute, first submit a portal ticket or email support@vmarm.comwith the order ID, node, time of occurrence, impact scope, reproduction steps, and redacted logs. Both parties should first compare the records and seek a direct resolution.

The formation, interpretation, and performance of these terms are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through negotiation may be submitted to a court with jurisdiction in that jurisdiction.

VMArm may update these terms due to changes in service processes, security requirements, or applicable rules. Updates that materially affect user rights or obligations will include the version and effective date on the website or in the portal. Continuing to place orders, renew, or use nodes after an update takes effect constitutes acceptance of the updated terms.