Know the rules before enabling Cloud Mac

Accessing or using the HopVM website, signing in to the console, creating an account, placing an order, or using Cloud Mac means the account holder has read and accepted these terms and the configuration, term, and location conditions stated in the order. If you disagree with any part, stop the ordering process before placing an order.

The account holder must have the legal capacity required to enter into an agreement. When ordering on behalf of an organization, the person placing the order must be authorized by that organization and able to confirm fees, device use, authorized members, and data-processing arrangements. The account holder is responsible for the actions of authorized members within the service.

Account information must remain accurate, complete, and available for necessary identity and order verification. Do not use another person’s identity, impersonate an organization, or use multiple accounts to bypass security controls, billing, or usage limits.

HopVM provides remotely accessible Cloud Mac devices. Each valid order corresponds to a dedicated physical machine and an actual physical node. The service is not a virtual machine, and the processor, memory, and local storage assigned to an order are not sold as shared compute resources.

The exact service scope is defined by the order confirmation, including model, chip, memory, internal storage, billing term, selected location, and add-ons. Remote access may include the macOS graphical interface and command-line environment for development, automated builds, testing, model inference, and media processing.

The service does not include development of the user’s projects, dependency fixes, code reviews, build-script maintenance, or third-party tool licenses. HopVM is responsible for the device and access path covered by the order; the user is responsible for project configuration, tool versions, and validating business results.

Cloud Mac

A Mac device used remotely through a controlled network connection.

Dedicated physical machine

The actual device used exclusively by the order during its validity period.

Location

The service region where the device is located, delivered according to the location selected in the order.

Rental term

The service period calculated by day, week, month, or quarter.

HopVM offers only the three models listed below. Verify the configuration before ordering; do not infer memory or storage specifications from similar names. Available models are HopVM M4 16, HopVM M4 24, and HopVM M4 Pro 64.

All three models are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the Eastern United States, and the Western United States—six locations in total. Catalog combinations are generally available to order; actual availability at checkout is based on the real-time response from the console.

Confirm the rental term, location, storage expansion, and Thunderbolt 5 parallel-connection option. After payment and system verification are complete, the order enters delivery. The order ID, configuration, and status shown in the console are the basis for verification. If the order differs from your selections, submit a ticket before starting business tasks.

After delivery, first verify the device status, system time, disk capacity, current user, and access method before deploying code or importing data. If tasks were run on an incorrect configuration because the order was not verified, stop them and confirm the resolution path with the support team.

All orders are priced and settled in US dollars (USD). The only supported payment methods are USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. Gateway availability is determined by the backend response when the order is submitted.

Model prices are those published in the pricing table above and on the plan page. Add-ons are billed for the same rental term and form part of the order total together with the selected model:

Before payment, the order should clearly list the model, term, location, add-ons, and total due. Users are responsible for checking the receiving network, amount, and order ID. Inquiries about order status should include the order ID shown in the console, but never full payment credentials in email or tickets.

Different terms have independently published prices; do not calculate weekly, monthly, or quarterly prices by multiplying the daily rate. For renewals, configuration changes, or added options, the order details shown when the user confirms the change apply. Items not confirmed by the user are not considered ordered services.

Users may perform software development, continuous integration, automated testing, model inference, transcoding, rendering, and related engineering tasks within the scope of lawful authorization. Tasks must match the order configuration and must not harm the platform, nodes, networks, or the systems and rights of others.

The following activities are prohibited:

• Unauthorized access: Scanning, probing, bypassing authentication, or accessing accounts, systems, networks, or data without permission.
• Malware distribution: Creating, hosting, executing, or distributing programs intended to cause damage, steal, extort, enable covert control, or evade security detection.
• Resource abuse: Using abnormal traffic, malicious automation, sustained attacks, or other means to affect node stability or normal user access.
• Illegal content handling: Storing, generating, distributing, or processing content or data that violates applicable law.
• Infringing others’ rights: Using another party’s code, data, models, media, trademarks, copyrighted works, or personal information without permission.
• Circumventing controls: Deleting, altering, or bypassing access restrictions, logging, order boundaries, or security policies.

When high-risk activity is detected, HopVM may first restrict the relevant session, network access, or device operations to contain the impact and explain the required verification steps through the contact information on the account. Users must cooperate by providing the task purpose, timeframe, and necessary redacted evidence.

Users are responsible for protecting account passwords, connection keys, device access details, and authorized-member lists. Credentials should be shared only with members who need them for work and transferred through controlled methods; do not paste them into public repositories, build logs, chat messages, or unprotected project documents.

When a team shares a device, establish member permissions, project directories, task queues, and handoff records. Revoke permissions and rotate related credentials promptly when a member leaves a project or responsibilities change. Do not save sign-in sessions or connection details on shared devices.

If you detect an unusual login, unknown session, permission change, or suspected key exposure, immediately stop affected tasks, revoke the relevant credentials, preserve the time, location, and redacted logs, and submit a ticket through the console. Use support@hopvm.com for security reports, compliance-document requests, and general inquiries.

HopVM targets 99.9% service uptime. All locations are provided on a 365-day continuous-operation basis. Status records for the past 90 days describe node connectivity and closed service events; they do not guarantee the performance of an individual project, tool, or network exit.

Uptime verification is based on HopVM node status, device records, and access-path logs. A user’s local network, incorrect credentials, project configuration, intentionally stopped tasks, third-party development-tool failures, and user-caused interruptions do not count as platform downtime.

If a user believes the target uptime was not met, they must submit a request through the console within 30 calendar days after the relevant service event is closed, including the order ID, location, occurrence time and time zone, duration, reproduction steps, and redacted error output. Requests without a matching order or accurate timeframe require additional information before verification.

When verification confirms eligibility, compensation is determined by the affected order, actual impact duration, and the applicable conditions of these terms. Force majeure, user actions, and external network events beyond the platform’s control are excluded. Do not transmit access credentials or complete project data through public email when submitting a compensation request.

Users are responsible for managing their code, dependency caches, build artifacts, model files, media assets, keys, and other project data. Cloud Mac is a working device, not a sole storage location for project data. Keep independent copies of important content and verify that they can be restored.

During the rental term, users should set export frequency according to project risk. Long-running builds, inference, and transcoding tasks should preserve reproducible commands, dependency versions, log summaries, and intermediate results so work can resume after connection changes or task restarts.

Before the rental term ends, or before voluntary cancellation or service termination, complete necessary exports, stop background tasks, revoke temporary credentials, and delete sensitive files that are no longer needed. After access ends, do not assume that data on the device remains available.

For collaborative work, clearly assign data owners, export leads, handoff times, and artifact locations. Keeping files only on the desktop, in temporary directories, or in build caches is not a verifiable backup.

1. Save source data Sync code, configuration, and input assets to controlled storage.
2. Export artifacts Verify that archives, installers, model outputs, and finished media can be read correctly.
3. Revoke credentials Remove temporary tokens, connection keys, and member authorizations.
4. Document the handoff Record the last successfully completed task, unfinished work, and data locations.

An order may enter a restriction, suspension, or termination process because payment is incomplete, payment verification fails, a significant security risk arises, acceptable-use rules are violated, the rental term ends, or the user cancels. The applicable action for each reason is determined by the order status and ticket notification in the console.

Orders with incomplete payment do not proceed to normal delivery. If a delivered order presents a security risk, HopVM may first restrict affected access or tasks and then require the account holder to verify identity, purpose, and relevant logs. Restoration after verification and risk resolution depends on the actual review outcome.

When canceling voluntarily, users should first confirm that business tasks have stopped, artifacts have been exported, and authorizations have been revoked. A cancellation request does not automatically extend access and must not be used to delay data migration.

When the rental term naturally ends, device access changes according to the order status. Users who need continued access should review the order and confirm the next term before the current term ends; availability of the requested combination is based on the console’s real-time response.

HopVM may terminate the relevant service in cases of serious violations, ongoing risk, or refusal to cooperate with necessary verification. Order, payment, and security records that must be retained will be handled only as required for service operations, dispute handling, and legal obligations.

Each party is responsible for conduct within its own control. HopVM’s responsibility is limited to the device covered by the order, node status, and platform access path; users are responsible for project code, dependencies, keys, member authorization, task parameters, data copies, and business results.

Problems caused by third-party development tools, external code repositories, dependency sources, the user’s local network, configuration errors, or unauthorized member actions should first be allocated according to the actual cause. Platform service issues supported by logs, order records, and a defined timeframe are handled under the service-event and compensation process in these terms.

To the extent permitted by applicable law, lost profits, lost anticipated revenue, loss of goodwill, expanded losses caused by unsaved data, and other indirect losses are excluded from service compensation. Mandatory legal requirements prevail.

If force majeure or an external event beyond the platform’s reasonable control occurs, both parties should promptly mitigate the impact, preserve necessary evidence, and communicate recovery conditions. Such events do not change the user’s responsibility to protect credentials, preserve data copies, and stop high-risk tasks.

Notices relating to these terms, an order, or the service may be sent through account records, console tickets, or support@hopvm.com Notices must include an identifiable order ID, factual timeline, requested action, and redacted evidence, and must not include passwords or complete private keys.

These terms are governed by the laws of the jurisdiction where the platform operator is based. In a dispute, the parties should first seek resolution through written notice and verifiable records; if negotiations fail, the dispute will be submitted to a court with jurisdiction in that jurisdiction.

If any part of these terms is found unenforceable, the remaining provisions remain effective. When HopVM makes a material change, the published version will state its scope; changes do not retroactively alter confirmed configurations or prices for orders completed before the change.