ArmVMS Cloud Mac Terms of Service

These terms apply when you access the ArmVMS website, create or manage an order, make a payment, or connect to and use an ArmVMS dedicated Apple Silicon physical node. Visiting the website does not require an immediate purchase; however, creating an order, completing payment, or beginning to use a physical node means that you have read, accepted, and agreed to follow these terms.

If you create an order on behalf of a team, business, or other organization, you confirm that you are authorized to accept these terms for that entity. The entity and its approved node users must follow the account security, acceptable use, data management, and payment rules.

ArmVMS provides dedicated Apple Silicon physical node rental services. The current catalog includes ArmVMS M4 and ArmVMS M4 Pro configurations. Orders can select from five nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States. Actual availability is based on the live status returned by the console.

Each order must clearly record the chip, memory, storage, node, rental term, and add-ons. ArmVMS M4 includes M4, 16GB memory, and a 256GB SSD; ArmVMS M4 Pro includes M4 Pro, 64GB memory, and a 2TB SSD. Any additional storage or Thunderbolt 5 interconnect must be listed separately in the order.

• Resource boundaries:The order provides a dedicated physical machine. Its processor, memory, and local storage are not shared with other users.
• User interface:Users may use the macOS graphical interface, command line, and automated build capabilities described in the delivery information.
• Availability:Nodes operate normally 365 days a year. The console records determine the connection and order status.
• Catalog changes:Later catalog changes do not retroactively modify the model, node, or rental-term records of confirmed orders.

Users must provide accurate, complete account information suitable for service communications and promptly update any outdated details. The account email is used for identity verification, order association, security checks, and necessary notices, and must not be shared with anyone unauthorized to operate the order.

Users must protect console login details, physical node credentials, keys, tokens, and project access permissions. Do not place credentials in public repositories, build logs, shared documents, or unprotected scripts. If you detect an unusual login, unknown order, or exposed credential, immediately rotate the relevant credentials and submit a related ticket through the console.

ArmVMS supports daily, weekly, monthly, and quarterly rental terms. Each term is an independently priced catalog option and must not be treated as an automatic conversion of another term's price. Before payment, users should review the order details and confirm that the task duration matches the selected term.

The order confirmation page is the final configuration check. Review the model, chip, memory, base storage, target node, rental term, additional storage, number of Thunderbolt 5 interconnects, and total order amount. If the selected configuration does not suit the workload after submission, promptly submit a related request through the console and retain the order number.

Unless the order page explicitly shows a new continuous rental record, a single order covers only its confirmed term. If users need to continue using a node, they should review the available options in the console before the current task ends rather than relying on an unconfirmed term for business continuity.

ArmVMS supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All prices, order amounts, and payment records are settled in USD. The payment gateway actually available and the payment status are determined by the information returned by the backend during checkout.

Before confirming payment, users must verify the receiving network, order amount, currency shown on the payment page, and order number. For USDT-TRC20, select the correct network and verify the address; for bank cards, complete the required verification in the checkout flow. Review requests arising from an incorrect network, incorrect information, or duplicate payments will be handled based on the order and transaction records.

Submitting a payment does not replace order verification. If the payment status, order amount, or configuration record does not match, retain the transaction ID and order number and submit a ticket through the console. Do not send complete card details, private keys, tokens, or connection passwords through public channels.

Users may use nodes for lawful software development, iOS and macOS builds, CI/CD execution, remote development, testing, creative workflows, and AI experiments. Users must ensure that they have the necessary rights to use all code, models, assets, dependencies, data, and automated tasks.

Users must not use or assist others in using ArmVMS services for the following activities:

• Illegal activity Creating, running, or distributing programs, content, or business processes that violate applicable rules.
• Unauthorized access Attempting to access accounts, systems, repositories, services, networks, or data without authorization.
• Malicious scanning Performing unauthorized port scans, credential probing, vulnerability exploitation, or bulk enumeration against external targets.
• Service disruption Launching denial-of-service attacks, abnormal traffic, resource abuse, or other activity that affects the stability of nodes, networks, or third-party systems.
• Rights violations Infringing another party's intellectual property, privacy, trade secrets, or other lawful rights.
• Bypassing security controls Circumventing authentication, permission limits, billing processes, node isolation, or security detection mechanisms.

Automated tasks must use reasonable concurrency, timeout, retry, and logging policies. Users must not treat external networks, code-hosting services, or third-party interfaces as unlimited resources simply because they have a dedicated physical node.

Users are responsible for organizing, setting permissions for, and backing up their code, credentials, build artifacts, model files, assets, caches, and business data as needed. A physical node is suitable as a development and execution environment, but should not be the only copy of critical project files.

During the rental term, users should establish external version control and backup processes based on the value of the work. When preparing to migrate, finish a task, or change nodes, confirm that repository commits, dependency lists, build records, exported artifacts, and model files have been moved to a user-controlled location, and remove credentials that are no longer needed.

In the event of a security incident, infrastructure failure, compliance requirement, payment anomaly, account risk, or serious violation of these terms, ArmVMS may take necessary measures based on the scope of impact, including requiring re-verification, restricting specific actions, suspending related access, or terminating the affected service.

Measures will be determined based on the nature of the incident, verifiable records, and potential impact. When advance communication is possible, ArmVMS will explain required user actions through the account email, console notices, or related tickets. When immediate action is needed to control a security risk, necessary restrictions may be applied first, followed by any information that can be provided.

1. 1

   Identify the Issue

   Check the order, account, node status, incident time, and relevant logs.

2. 2

   Limit the Impact

   Restrict related actions according to the risk scope and prevent the issue from affecting nodes or other systems.

3. 3

   Explain Required Actions

   Provide actionable verification, remediation, or information requests through an appropriate channel.

4. 4

   Record the Outcome

   Retain records of actions related to the order and incident for subsequent review.

Before voluntarily ending use, users should export data, remove credentials, and clean up tasks. Access may be terminated for serious violations of acceptable use rules, continued refusal to address security risks, or submission of false account information.

ArmVMS is responsible for providing the dedicated Apple Silicon physical node specified in the confirmed order and related order management capabilities. Users are responsible for project content, code permissions, application configuration, connection credentials, automated tasks, third-party dependencies, data backups, and internal team authorization. Responsibility for an issue is determined by which party controls the relevant system, data, or operation.

Impacts arising from force majeure, user actions, networks controlled by the user, changes to third-party services, unauthorized account use, or the user's failure to reasonably protect and back up data will be handled based on incident records, areas of control, and verifiable information from both parties. Anyone who discovers circumstances that may expand the impact must promptly take reasonable steps to contain it and preserve necessary records.

For information about how data is handled in website, order, and support communications, also readPrivacy Policy. For configuration and term options, seeRental Plans; for connection and troubleshooting resources, seeHelp Center.