HexVM Terms of Service

Acceptance of Terms & Service Definitions

These terms apply to the HexVM website, console, order pages, Cloud Mac services, physical nodes, add-ons, and support provided by email or ticket. Visiting the public website does not constitute an order; an order is formed after payment is confirmed and the corresponding service record is created.

Service scope

Cloud Mac

macOS computing resources accessed remotely over the network. HexVM services are provided on independent Mac mini physical nodes; processors, memory, and system disks from a single order are not split across virtual machines.

Physical node

An independent device assigned to a valid order. During the rental term, the order holder is responsible for the software, code, credentials, build jobs, and member permissions on the node.

Add-ons

SSD expansion or Thunderbolt 5 parallel configurations listed on the order confirmation page. Add-ons are tied to the corresponding node and rental term and cannot be used separately from the primary service.

Support services

Issue intake, diagnosis, and handling related to order confirmation, node connectivity, hardware status, billing, and platform features. Code logic, third-party tool configuration, and the customer’s own pipeline design do not automatically constitute a node failure.

Order of precedence

The model, region, rental term, add-ons, and total due shown on the order confirmation page form the specific record for that order. If the specific order record differs from general information, the content displayed at confirmation and submitted by the user prevails; applicable mandatory legal requirements take precedence.

Accounts & Eligibility

Anyone creating an account or placing an order must have the capacity required to enter into and perform these terms. When acting for a team or organization, the operator confirms that they have appropriate authorization to manage orders, nodes, and support requests on its behalf.

Registration Information & Account Responsibilities

• Registration information, order contacts, and billing details must remain truthful, accurate, and usable for service notifications.
• Account holders must protect login credentials, recovery information, SSH keys, and temporary connection credentials, and must not grant console access to unauthorized persons.
• Team members may operate nodes only within their authorized scope. When responsibilities change or a member leaves the team, console access, node access, and repository access should be revoked promptly.
• Orders, renewals, node operations, and ticket submissions made through an account are generally treated as actions of the account holder or an authorized member.
• If you discover an unusual login, exposed credentials, or an unknown order, update the relevant credentials immediately and report it through a console ticket or the support email.

Orders, Pricing & Billing

Cloud Mac services are available with daily, weekly, monthly, or quarterly terms. Each order is governed by the model, region, term, add-ons, quantity, and total shown on its confirmation page. All fees are priced and settled in U.S. dollars (USD), with no conversion to other currencies.

Available Models & Order Records

Pricing confirmation rules

• Selecting a model, region, or add-on does not create an order. The final order is governed by the confirmation page shown before submission.
• The same model is priced separately for each term; short-term pricing is not automatically extrapolated to longer terms.
• SSD expansion and Thunderbolt 5 parallel configurations are added to the order according to the unit, quantity, and term shown on the confirmation page.
• If applicable, discounts, service credits, or account balances are listed separately in the total due; items not displayed are not considered committed.
• Actual node availability is returned in real time by the console. Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, U.S. East, and U.S. West are the six regions currently listed.

Review your order before payment. Requests to change a mistakenly selected region, model, term, or add-on will be handled based on whether delivery has started, whether the service has been used, and whether the change is technically possible.

Payment Rules

HexVM supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The available payment gateway is determined by the result returned by the backend when the order is submitted; all orders are settled in U.S. dollars (USD).

Payment confirmation

• Card payments are governed by the payment processor’s result and the order status. Node delivery will not begin until verification is complete.
• When using USDT-TRC20, verify the network, receiving details, and amount due. Once the payment record receives valid confirmation, the order enters the delivery process.
• If the payment result is unconfirmed, the amount does not match the order, or the transaction cannot be identified, the order remains incomplete. You can check the result in the console and submit a ticket for review.
• A failed payment does not create a valid rental term or ongoing usage rights for the corresponding node. When paying again, rely on the new confirmation page.

Taxes & Payment Records

The order confirmation page displays the total due for that transaction. Taxes, reporting, or internal reimbursement requirements payable by the user under applicable law are the user’s responsibility; if the transaction requires necessary billing information, the user must provide accurate details. Payment results, order numbers, and billing records may be used to verify service ownership and resolve disputes.

Delivery, Renewal & Cancellation

After payment confirmation, the system performs node assignment, status checks, and credential generation in sequence. The typical process takes about four minutes, with payment confirmation, node assignment, system checks, and credential delivery generally taking about one minute each. This timing describes the general process; the console result determines the actual order status.

Delivery start & term calculation

• Service is considered delivered once the node has been assigned, passed basic checks, and connection information has been provided to the order account.
• The order record determines the start and end of the term. Failing to log in promptly, run build jobs, or keeping an application open does not pause the term.
• After the first connection, promptly update temporary credentials, record the host fingerprint, and verify the required Xcode and command-line environment.
• If the delivery information cannot be used, stop high-risk operations first and provide the node ID, region, time of occurrence, and error details for investigation.

Renewal

Renewals must be completed through the console before the current service expires. Once a renewal order is formed, the new service period is governed by the confirmation page. Renewal pricing, add-ons, and payment results follow the order record displayed at renewal and are not automatically locked to the historical order.

Cancellation & Expiration Release

Cancellation requests may be submitted through a console ticket. If the node has not been delivered, HexVM will review the payment status and delivery progress; if the node has been delivered, charges already incurred will be handled according to the order and services consumed. Cancellation does not automatically reverse a completed valid payment.

When the service expires without a completed renewal, node usage rights end and the node enters the release process. Before expiration, export your code, build artifacts, logs, and other required data, revoke team-member permissions, and remove your own credentials. After release, you cannot continue relying on the original connection information to access the device.

Acceptable Use Policy

You may use the node for lawful development, builds, testing, automation, remote production, and Apple Silicon environment validation. You must ensure that your code, data, software licenses, and network activity comply with applicable law, authorization limits, and these terms.

Prohibited conduct

• Attempting to access nodes, accounts, networks, storage, or control planes not covered by the current order.
• Distributing malware, ransomware, or credential-stealing tools, or using the node for unauthorized scanning, intrusion, or control activities.
• Sending spam, generating denial-of-service traffic, bypassing network restrictions, or continuously consuming resources in a way that disrupts other customers or platform operations.
• Uploading, copying, distributing, or building content that infringes another person’s intellectual property, privacy, or other lawful rights.
• Bypassing access controls, altering node identification information, concealing an attack source, or obstructing security investigations and incident response.
• Reselling account access, sharing complete credentials, or allowing an unauthorized third party to control the node.
• Using the service for fraud, unlawful transactions, data theft, or other activities that violate applicable law.

Enforcement measures

When high-risk activity is detected, HexVM may take necessary measures based on the scope of the risk, including restricting connections, isolating tasks, requiring credential updates, suspending the affected node, or terminating the service. Where safe contact is possible and the risk permits, we will explain required remediation through account notifications or tickets; in cases involving an ongoing attack, apparent unauthorized access, or potentially escalating harm, we may control the risk first.

You must cooperate by providing reproducible information and redacted logs. Do not send actual private keys, complete access tokens, or complete passwords through tickets or ordinary email.

Service Targets & Incident Handling

Availability assessment

When you report that you cannot connect or perform a basic task, first check your local network, account status, node status, host information, and authentication method. A node or platform issue within HexVM’s control that is confirmed to continuously affect the service associated with the order may be included in the incident impact scope.

Events outside the platform’s responsibility

• Unavailability caused by the user shutting down the device, deleting critical system files, or incorrectly changing network or permission settings.
• Issues with the user’s local network, carrier link, repository service, dependency source, or other external system.
• Incorrect credentials, expired keys, software conflicts, code defects, build configuration errors, or exhausted task resources.
• Force majeure, widespread public-network outages, government action, or other events beyond reasonable control.
• Necessary restrictions imposed to prevent risk from escalating after the user violates the acceptable use rules.

Incident Reports & Service Credits

Report incidents through a console ticket and provide the order number, node ID, region, time first observed, impact scope, reproduction steps, and redacted logs. After recovery, if investigation confirms eligibility for a service credit, it will be calculated based on the affected node, valid impact duration, and applicable order charges, then added to the relevant account for use on eligible future orders.

A service credit request must be based on a verifiable service incident. Duplicate reports, customer-side configuration issues, and requests that cannot be linked to a valid order are not eligible. The credit result and calculation basis will be recorded in the ticket for review by both parties.

Data, Rights, Liability Limits, Termination & Contact

Customer Data & Node Handling

You retain your lawful rights in code, documents, build artifacts, configurations, and other customer data uploaded to the node. You also confirm that you have the right to process this data and are responsible for maintaining repository backups, artifact archives, key-rotation, and access-audit processes.

HexVM processes relevant data only as necessary to deliver services, handle support requests, secure the platform, and fulfill legal obligations. Before service termination or node release, you should migrate any required content. After release, the platform will clear customer data and connection information attributable to the original order in accordance with its data-handling process.

Platform Materials & Intellectual Property

Rights in the HexVM website interface, console features, brand marks, documentation, page text, and platform software belong to their respective lawful rights holders. Purchasing a service grants you the right to use the relevant features during the valid term and within the authorized scope; it does not transfer ownership of platform materials.

You may not copy platform source code, remove rights notices, impersonate the HexVM brand, or publish platform materials in a way that could confuse the source of the service. Interoperability research expressly permitted by law is not improperly restricted by this section, but it may not be used to access other customers’ data or compromise platform security.

Liability boundaries

Each party is responsible for the accounts, systems, personnel, and actions within its control. HexVM is responsible for providing the physical node, console capabilities, and support process specified in the order; the user is responsible for code correctness, software licenses, member authorization, data backups, build configuration, and management of their own credentials.

In a dispute, recoverable losses must be direct, provable, and reasonably causally connected to the specific breach. Liability that cannot legally be limited is governed by applicable mandatory requirements; liability that may legally be agreed is determined with regard to the affected order, incident duration, each party’s fault, and mitigation measures taken.

Suspension & Termination

• You may end future services by declining to renew or submitting a cancellation request, but you must still pay all charges for orders already formed.
• HexVM may suspend or terminate the affected services for serious violations of the acceptable use rules, continued threats to platform security, false transaction information, or refusal to stop high-risk conduct.
• Termination does not affect obligations concerning orders, payments, data protection, intellectual property, or dispute handling that arose before termination.
• After service termination, stop using the original connection information and clean up local credentials, automation scripts, and runner configurations.

Changes to these terms

HexVM may update these terms due to changes in product features, order processes, security requirements, or applicable law. Updates that materially affect user rights or obligations will be notified through the website, console, or account contact details. Updated terms apply from the time stated in the publication or notice; orders formed beforehand remain governed by their confirmation records and the rules applicable at that time.

Governing Law & Dispute Resolution

The formation, interpretation, performance, and dispute handling of these terms are governed by the laws of the jurisdiction where the platform operator is established, without affecting mandatory provisions that must apply by law. After a dispute arises, both parties should first submit order records, relevant facts, and requested remedies through a support ticket or email and negotiate in good faith.

If negotiation does not resolve the dispute, either party may bring proceedings before a court with jurisdiction in that jurisdiction. During dispute resolution, both parties must continue performing obligations unaffected by the dispute and capable of continued performance.

Contact HexVM

For orders, billing, service incidents, security reports, questions about these terms, or dispute communications, email support@hexvm.com. For issues involving an existing order, sign in to the console and submit a ticket first so the order number, node ID, and handling record can be linked.