Set the boundaries before enabling your Cloud Mac

By placing an order, paying rental fees, connecting to a Cloud Mac, using console features, or otherwise accessing order-related services, you confirm that you have read, understood and accepted these terms. Anyone acting for a team, company or other organization must confirm that they are authorized to accept these terms and manage the relevant orders on its behalf.

You must have the legal capacity required to enter into and perform these terms, and provide HireVM with real, accurate and consistently reachable information. Update the order contact, billing details or team administrators promptly when they change, so that connection details, billing notices, risk checks and support communications are not affected.

If you disagree with any part of these terms, stop placing orders or using the services. For existing orders, first export work data, revoke access and complete any necessary support communication, then stop further use as instructed on the order page.

HireVM provides dedicated Apple Silicon physical nodes for daily, weekly, monthly or quarterly rental. Each order corresponds to one dedicated physical machine; computing resources are not shared with other tenants and the machine is not a virtual machine. You may use the delivered system environment through a graphical desktop, command line or automated tasks.

The current catalog includes only HireVM M4 and HireVM Pro. HireVM M4 includes M4, 16GB RAM and 256GB SSD; HireVM Pro includes M4 Pro, 64GB RAM and 2TB SSD. Available nodes are Singapore, Tokyo, Seoul, Hong Kong and the US West. Actual availability for each combination is shown in real time by the console.

The order confirmation page lists the model, node, rental term, SSD upgrades, Thunderbolt 5 parallel connection count and total USD amount due. Treat the confirmation page as the final configuration for that order; do not schedule production work based only on historical screenshots, cached content or verbal summaries.

Nodes are designed to operate continuously 365 days a year. Remote performance may still be affected by your local network, cross-region links, client settings, code-host response times and third-party software status. Choose a node based on your team and repository locations and intended workload, and verify connectivity before starting production tasks.

All orders are settled in USD. We support USDT-TRC20 and Visa, Mastercard and Amex processed through Stripe. The payment gateways actually available are shown in the console. Before paying, verify the order currency, amount and recipient details, and do not use information that differs from the order page.

Order charges consist of the base model, rental term, selected node and add-ons. Add-ons may include +1TB SSD, +2TB SSD and per-machine Thunderbolt 5 parallel connections. Any configuration or charge not shown on the order confirmation page is not part of that order.

Daily, weekly, monthly and quarterly are distinct order terms, not simple automatic conversions. Choose a term based on task duration: short compatibility checks may suit a shorter term, while continuous builds, long-running runners or ongoing experiments should account for data migration costs, accumulated caches and team scheduling.

Before paying, verify the model, RAM, SSD, node, term, add-on quantities and total USD amount item by item. After payment, retain the order number and check the order status in the console. For billing questions, provide the order number, amount, term and add-on names, but never submit complete payment credentials.

You may use the Cloud Mac for lawful software development, build testing, automation, AI experiments, audio and video processing, and other workloads suited to the configuration purchased. All tasks must comply with applicable rules, software licenses and third-party rights.

The following activities are not allowed:

• Illegal activity Using the service to conduct, assist with or conceal activity that violates applicable rules.
• Unauthorized access Scanning, attempting to access or controlling accounts, devices, networks, code repositories or data sources without clear authorization.
• Malware distribution Creating, hosting or distributing code or content intended to damage, steal, extort or bypass security controls.
• Resource abuse Affecting normal use of a node, the platform or other users through abnormal traffic, destructive tasks or other means.
• Infringement of third-party rights Processing protected code, media, data, trademarks or other intellectual works without permission.

If the system detects activity that may affect platform security, node stability or third-party rights, HireVM may ask you to explain the purpose, stop the relevant tasks or provide necessary order context. The scope of handling will be limited to the minimum information required by the risk.

Users are responsible for securing console accounts, connection credentials, and team-member permissions. After the first connection, update initial credentials, create accounts with least-privilege access, and promptly remove members who no longer work on the project. Never store credentials in public repositories, build logs, or support ticket text.

You are responsible for confirming that installed software, development tools, fonts, plugins, media assets and code dependencies have appropriate licenses. HireVM provides physical nodes and related service capabilities; it does not obtain third-party software licenses required for your workloads.

Arrange code and data backups according to the importance of each task. A dedicated physical machine is not a backup service. Store important repositories, build artifacts, experiment results, media files and configuration records in suitable locations under your control, and verify the recovery path before major changes.

You are responsible for workload configuration, including runner concurrency, build-directory isolation, cache cleanup, disk space, remote-session settings and automation scripts. When an issue occurs, first record the time, node, error message and steps already taken, then troubleshoot according to the Help Center process.

Required steps before the rental ends

1. 1
   Export work data

   Copy code, build artifacts, experiment records, media outputs and necessary configuration.

2. 2
   Revoke external tokens

   Revoke repository tokens, API keys, CI keys and temporary access credentials.

3. 3
   Remove members and tasks

   Stop runners, scheduled tasks and background processes, and remove members who no longer need access.

4. 4
   Confirm order status

   Check the term end time and next steps; do not leave data export until the last moment.

HireVM may update service capabilities and terms based on security controls, infrastructure changes, catalog updates or applicable requirements. We will provide a reasonable explanation of changes that materially affect a current order, allowing you to assess next steps.

When unauthorized access, malicious code, abnormal resource use, payment risk or other potentially harmful conduct is detected, HireVM may take proportionate measures, including limiting relevant tasks, suspending an affected order or requiring verification. Measures will focus on the affected scope and will not expand the collection of information unrelated to the incident.

An order enters expiry processing when its agreed term ends. If you voluntarily stop further use, first export data, revoke tokens, stop tasks and remove members. Stopping use does not perform these actions for you and does not replace your responsibility to clean up third-party software, repositories and data sources.

For an order suspended for violating the Acceptable Use Policy, provide the order number, node, time, purpose and corrective measures taken through a console ticket. Do not submit passwords, private keys, complete payment credentials or unrelated sensitive data in a ticket.

HireVM is responsible for delivery of physical nodes, platform functionality and order support within its control. You are responsible for your local network, client environment, software licenses, workload configuration, code and data backups, team permissions and external service settings. Each party should address issues within its actual control and provide necessary information.

External network congestion, device failures, code-host responses, third-party software defects, upstream service changes and your own actions may affect remote connections or task results. When an issue occurs, both parties should first assess the cause using the order number, node, time, error messages and activity history rather than attributing responsibility solely from a failed task.

To the extent permitted by applicable rules, indirect losses, lost expected profits, lost business opportunities, and losses increased because you failed to maintain reasonable backups or export data promptly will be assessed in light of actual control, foreseeability, causation and mitigation measures taken by both parties.

Notices related to orders, billing, nodes or service use must be submitted through a console ticket or support@hirevm.com . Notices must include the order number, issue category, time, node and steps already taken, but must not include passwords, private keys, complete payment credentials or other unrelated sensitive content.

The formation, interpretation, performance and dispute handling of these terms are governed by the law of the jurisdiction where the platform operator is based. After a dispute arises, both parties should first communicate in good faith through the support channel and retain necessary records. If negotiation fails, the dispute may be submitted to a court with jurisdiction in that jurisdiction.

If any part of these terms is found unenforceable, the remaining provisions continue to apply to the extent enforceable. Failure to exercise a right immediately does not constitute a permanent waiver of that right. Headings are for navigation only and do not change the meaning of the text.