1. Home
  2. Terms of Service
Read Before Ordering

Review the rules before enabling your Cloud Mac

These Terms explain the rights and responsibilities of both parties when accessing the website, placing an order, and using MangoVM’s dedicated Apple Silicon physical nodes, including ordering, delivery, renewal, use, data protection, and dispute handling.

Effective date: August 24, 2026 Version: 1.0
Terms Index

Browse by service stage

  1. 01Acceptance and Scope
  2. 02Service Definition
  3. 03Accounts and Authorization
  4. 04Orders and Delivery
  5. 05Pricing and Payment
  6. 06Renewal and Termination
  7. 07Acceptable Use
  8. 08Availability and Service Credits
  9. 09Data and Customer Responsibilities
  10. 10Liability and Disputes

For order, node, or billing issues, sign in to the console and submit a ticket. For general questions about these Terms, email support@mangovm.com.

Open Console
01

Acceptance and Scope of the Terms

By visiting the MangoVM website, placing an order, completing payment, receiving node connection details, or actually using Cloud Mac services, you confirm that you have read and accepted these Terms and the rules on the order confirmation page relating directly to your selected configuration, rental term, region, and add-ons. Anyone acting for an organization must ensure they have the appropriate authorization.

These Terms cover website browsing, Cloud Mac orders, node delivery, use during the rental term, renewals, changes, technical support, billing, and resource reclamation after the rental term ends. Privacy information processing is covered in thePrivacy Noticeand security responsibility boundaries are covered in theData Protection Notice.

Page descriptions, plan pages, order confirmations, and these Terms together form the service agreement. If an order contains more specific configuration or implementation conditions confirmed by both parties, those terms apply only to that order; all other terms remain in effect.

02

Service Definition and Product Scope

MangoVM provides Apple Silicon Cloud Macs available for rental by term. Each valid rental corresponds to a dedicated physical machine and physical node; resources are not shared with other customers, and the product is not a virtual machine. During the rental term, customers may use the macOS graphical interface, command line, and their own development toolchains.

The current catalog contains two configurations: the performance configuration has M4 Pro, 64GB memory, and 2TB SSD and is named MangoVM M4 Pro. The base configuration has M4, 16GB memory, and 256GB SSD and is named MangoVM M4. Available regions are Singapore, Tokyo, Seoul, and Hong Kong—four node regions in total. Catalog combinations are generally available to order; real-time availability is shown in the console.

Current Cloud Mac configurations and term pricing
Configuration Daily Weekly Monthly Quarterly
MangoVM M4M4 · 16GB · 256GB $19.1 $51.5 $95.3 $259.2
M4 Pro · 64GB · 2TBMangoVM M4 Pro $60.4 $163.2 $302.2 $822

Catalog information on the website helps customers choose a plan. The final order must specify the model, rental term, node region, add-ons, and amount due. MangoVM will not replace a confirmed configuration with descriptions that are not included in the order.

03

Accounts, Credentials, and Authorized Use

Customers must provide account and contact information that is true, accurate, and usable, and update it promptly when it changes. Account holders are responsible for managing console login credentials, node access keys, authorized members, and credentials used by automated systems.

Customers may authorize team members or automated tasks to use the service, but account holders remain responsible for actions within that authorization, including software installation, network configuration, data deletion, build tasks, resource consumption, and ticket instructions. If unauthorized access, credential exposure, or incorrect permissions are discovered, rotate the relevant keys immediately and notify the support team through a console ticket.

  • Least privilege:Grant access only to the people and systems required for the task.
  • Separate credentials:Use distinguishable credentials for different people, Runners, and automated tasks.
  • Audit trail:Retain records of key logins, builds, deployments, and permission changes.
  • Secure transfer:Do not transmit private keys, passwords, or signing materials through public pages, public code repositories, or unprotected messages.
04

Orders, Rental Terms, and Delivery

Rental terms are available by day, week, month, or quarter. Before placing an order, customers should verify the model, memory, storage, region, term, storage add-ons, and number of Thunderbolt 5 connections. An order is established when the console displays confirmation and payment is successfully completed.

Delivery includes order confirmation, node preparation, status updates, and provision of connection details. Customers should check the delivery status, node address, account credentials, and access-control information in the console. Delivery time depends on the real-time status shown in the console; the website does not promise delivery within a fixed number of minutes.

Connection details are provided only to verified accounts. After receiving them, customers should first verify the node identity, then choose SSH, an encrypted remote connection, or a CI/CD Runner based on their workload. First-connection and troubleshooting steps are available in theSupport Documentation.

Order verification sequence

Model and specifications → Node region → Rental term → Add-ons → USD amount → Delivery status. If order information is inconsistent, pause further configuration and submit a console ticket.

05

Pricing, Add-ons, and Payment

All orders are priced and settled in U.S. dollars (USD). MangoVM supports only USDT-TRC20 and Visa, Mastercard, or Amex through Stripe. Actual payment channels are determined by the result returned by the console.

The order total consists of the selected model’s term price, rental duration, and add-ons. Customers should verify the details before payment. After payment, the order ID, amount, term, and transaction status shown in the console are the primary references for billing assistance.

Optional add-ons and term pricing
Add-on Daily Weekly Monthly Quarterly
+1TB SSD $2.9 $7.7 $14.3 $38.9
+2TB SSD $5.8 $15.4 $28.6 $77.8
Thunderbolt 5 connections (per machine) $1.7 $4.6 $8.5 $23.1

Plan and price changes will not retroactively alter a confirmed current order term. For renewals or configuration changes, customers should rely on the new term details displayed before confirming the action. Full pricing information is available in theRental Plans.

06

Renewal, Changes, Expiration, and Termination

A renewal takes effect only when the customer confirms it in the console and the related payment is processed. Before renewing, verify the node, configuration, term, add-ons, and amount again. An unconfirmed renewal intention, email inquiry, or incomplete payment process does not constitute a valid renewal.

Changes to add-ons such as storage expansion or Thunderbolt 5 connections may require node configuration changes. Before making a change, customers should stop related tasks, verify mounted paths, and complete necessary backups. Whether a change can be made during the current term depends on the options available in the console and the implementation conditions confirmed by the support team.

Before the rental term ends, customers must migrate their code, build artifacts, logs, keys, and other necessary data. After expiration, node access and resources will enter the reclamation process according to the order status. The applicable outcome of early termination is determined by the order conditions shown when the termination action is submitted.

If a customer seriously violates the Acceptable Use rules or continues to threaten node or network security, MangoVM may take necessary measures, including restricting access, suspending related tasks, or terminating the service. Measures will be determined based on the scope of risk, urgency, and verifiable records.

07

Acceptable Use Rules

Customers must use the service within the laws applicable in the jurisdiction where the platform operator is based and ensure that their software, data, automated tasks, and network activity do not infringe the lawful rights of third parties. The following activities are prohibited:

  • Conducting unlawful activities, or storing, processing, or distributing content clearly intended for unlawful activities.
  • Unauthorized access to, probing, scanning, or control of other accounts, devices, systems, or networks.
  • Creating, deploying, or distributing malicious code, or intentionally bypassing security controls or access restrictions.
  • Using nodes to launch denial-of-service attacks, bulk spam, credential attacks, malicious scraping, or other forms of resource abuse.
  • Infringing another person’s copyright, trademark, trade secrets, privacy, or other lawful rights.
  • Interfering with data-center networks, platform services, other customers’ tasks, or the support team’s normal work.

Customers must reasonably limit concurrent tasks, monitor unusual processes, and configure necessary authentication and access controls for public-facing services. If a task may affect external parties, stop the relevant processes first, preserve logs, and then use a console ticket to describe the time range, process information, and measures taken.

08

Availability Target and Service Credits

MangoVM’s service availability target is 99.9%. All nodes are operated on the principle of normal service availability 365 days a year. Availability measures the platform-side accessibility of nodes during the rental term and does not mean that customer-deployed software, build scripts, or external networks will always be fault-free.

99.9% Service availability target
Verified for the affected term Cross-checked against platform records, node status, and ticket materials

Availability verification covers node delivery status and platform-side access capabilities managed by MangoVM. Force majeure, customer actions, customer software configuration, expired credentials, local networks, external public-network links, and restrictions imposed for violations of the Acceptable Use rules are excluded from platform-side downtime.

To request a service credit, customers must submit a console ticket after the relevant billing period ends, including the order ID, affected node, start and end times, connection method, error summary, and necessary logs. MangoVM will determine eligible downtime using platform status records, access records, and customer materials.

Eligible credits are calculated from the service fees paid for the affected term, in proportion to the confirmed downtime relative to the total length of that term. Credits for a single affected term will not exceed the corresponding service fees paid for that term. Credits apply to future valid orders and do not change the customer’s responsibility to back up data and protect credentials.

09

Data, Software, and Customer Responsibilities

Customers are responsible for the code, build artifacts, databases, logs, keys, signing materials, test data, and software they install on their nodes. Customers should maintain independent backups based on business importance and verify that backups can be restored. A node must not be the sole copy of critical data.

Customers are responsible for confirming that the software, SDKs, fonts, media assets, and other content they use are appropriately licensed, and for migrating or deleting the relevant data before the rental term ends. For team collaboration, customers must clearly define who may read signing materials, modify build configurations, export data, and perform deletion operations.

MangoVM performs platform-side access control, authorization reviews, necessary operational logging, and resource reclamation in accordance with the service agreement. Platform operations are performed only as necessary for delivery, incident response, security response, or an explicit customer request, following the principle of least necessity.

During the rental term

Maintain restorable backups, rotate access keys, and retain logs for critical tasks.

Before configuration changes

Pause write operations, verify toolchain compatibility, and confirm that rollback materials are complete.

Before the rental term ends

Migrate code and artifacts, revoke automation credentials, and verify that necessary data has been exported.

10

Liability Boundaries, Changes to Terms, and Disputes

Each party is responsible for its own actions, authorization, data, and legal obligations within the service relationship. MangoVM is responsible for platform-side services as specified in confirmed orders and these Terms. Customers are responsible for their workloads, software licenses, access controls, data backups, authorized users, and content generated through use of the service.

To the extent permitted by applicable law, liability relating to an order will be assessed by considering direct impact, verifiable loss, each party’s sphere of control, and mitigation measures taken. Service credits are handled under Section 8 of these Terms; nothing in any liability determination excludes rights that applicable law does not permit the parties to limit by agreement.

MangoVM may update these Terms due to changes in the product catalog, billing process, security requirements, or legal obligations. Material changes will be communicated through the website, console notifications, or account contact information and will state the new effective date. Updated Terms apply to orders submitted or renewed after their effective date; confirmed terms continue to be governed by the agreement in effect at that time, unless applicable law requires otherwise.

For disputes arising from these Terms or the service, the parties should first submit the order ID, factual timeline, relevant records, and specific request through a support ticket or to support@mangovm.com and attempt to resolve the matter through negotiation. If negotiation fails, the laws applicable in the jurisdiction where the platform operator is based will apply, and the dispute will be handled by a court with jurisdiction in that jurisdiction.

If any part of these Terms is determined to be unenforceable, the remaining parts remain effective. The affected part must be interpreted and enforced, to the extent permitted by applicable law, in the manner closest to its original business purpose.

Review a specific order

Prepare the order ID and issue timeline first

Submit node status, billing, renewal, or service-credit requests through a console ticket. General questions about these Terms may be sent to support@mangovm.com. Do not attach passwords, private keys, or signing materials to emails.

Submit Console Ticket Email Terms Question
Continue After Confirmation

Create an order with the actual configuration and term

Before starting the ordering process, verify the two models, four node regions, USD amount, and required add-ons again.

Rent a Cloud Mac Now View Configurations and Pricing