Understand each party’s responsibilities before placing a Cloud Mac order

Acceptance of Terms and Account Eligibility

By creating an account, placing a Cloud Mac order, completing payment, or beginning to use a physical node, you confirm that you have read, understood, and agreed to be bound by these terms and the order confirmation. If you act for a team, company, or other organization, you confirm that you are authorized to accept these terms on its behalf and are responsible for communicating the applicable rules to actual users.

Account information must be truthful, accurate, and kept up to date. You must promptly update your name, contact email, billing information, and details relevant to order fulfillment. You may not impersonate another person, use misleading information, or create multiple accounts to bypass usage limits. We may request information directly related to order delivery, payment confirmation, or security audits.

Accounts may be used only by authorized personnel. You must assign clear permissions to team members and are responsible for orders, configuration changes, node operations, and support requests made under your account. If login details are exposed or you detect unusual access or an unauthorized order, change your password immediately and contact our support team through a console ticket.

Service Scope and Delivery

MacMLab provides Cloud Mac environments for development, builds, and experimentation. Each valid rental corresponds to one physical node delivered as a dedicated physical server, not a virtual machine. You may use the macOS graphical interface and command-line environment through supported remote connection methods, and configure development tools and build tasks within the scope of your order.

Only the following two configurations are currently available. Every order is subject to the model shown on its confirmation page:

MacMLab M4 16

M416GB memory256GB SSD

MacMLab M4 24

M424GB memory512GB SSD

Both models are available in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Availability, delivery details, and optional add-ons for each combination are based on the real-time information returned by the console. Equipment, software licenses, data migration, environment configuration, support for third-party development tools, and business outcomes not listed in the order are not included by default.

Ownership of the physical node hardware does not transfer through rental. You receive the right to use the node during the order period. You may not dismantle the equipment, resell access, bypass access controls, or interfere with the infrastructure hosting the node in any way.

Orders, Periods, and Changes

Cloud Mac orders may be placed by the day, week, month, or quarter. Each order must specify the model, physical node region, rental period, and selected add-ons, including additional SSD capacity or the number of Thunderbolt 5 connections. The record displayed before payment and confirmed by you governs the order.

Placing an order does not mean delivery is complete immediately. The order must pass payment-status confirmation and configuration checks, and the console will provide the actual availability information. If order details are incomplete, payment has not been confirmed, or additional information is required for a security check, the order status will be updated in the console and you must complete the required steps as instructed.

After a period begins, changing the region, model, or underlying storage may require a new order or data migration. Before making changes, you should back up business data and confirm that your toolchain, cache directories, and automated tasks can be reconfigured on the target node. A change takes effect only after the console generates a new confirmation record.

If you want to continue using the service, submit a renewal through the method provided in the console before the current period ends. An unconfirmed renewal request, an intention expressed only by email, or an unpaid transaction does not constitute a valid renewal. After the period ends, access rights and data handling will follow the order status and these terms.

Fees, Payment, and Renewals

All orders are priced and settled in US dollars (USD). Supported payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The available payment gateway, payment steps, and payment status are determined by the console.

The total order amount is based on the selected model, period, region, and add-ons. Before paying, verify the currency, network type, recipient details, and final amount. When using USDT-TRC20, you must confirm that the transfer network is correct and bear the processing risks caused by an incorrect network, address, or other payment information. Card transactions are verified through the applicable payment-processing chain according to each party’s responsibilities.

Where applicable rules require taxes, transaction-processing fees, or other legally payable amounts, those items will be shown during confirmation. You are responsible for providing accurate billing information and for any reporting and payment obligations arising from your location or business arrangements. Unless the order confirmation expressly states otherwise, the rental fees shown on the page do not automatically include external costs you are responsible for.

Payment status is determined by the payment processor’s result and the console record. An on-chain broadcast, card authorization, or debit notification does not necessarily mean that the order has been confirmed. If you experience a duplicate payment, incorrect amount, or a status that remains unchanged for an extended time, submit the order number, transaction ID, and a redacted payment summary in a support ticket. Do not send complete card details or private keys.

Acceptable Use

You may use Cloud Mac only for lawful and authorized development, builds, testing, automation, remote work, and experimentation. You must not harm the platform, other users, network services, or the systems and rights of third parties.

The following activities are expressly prohibited:

• Illegal activity:Using the service to conduct, assist with, or conceal activities that violate applicable rules, or to process data that clearly lacks a legitimate source.
• Unauthorized access:Scanning, probing, bypassing, or attempting to enter accounts, devices, networks, interfaces, or data that you are not authorized to access.
• Malicious code distribution:Creating, hosting, executing, or distributing code or payloads intended to damage, steal, extort, or conceal control.
• Resource abuse:Generating sustained abnormal network traffic, evading resource limits, interfering with infrastructure, or affecting the normal operation of other nodes.
• Infringement of third-party rights:Copying, distributing, or processing protected content without permission, impersonating others, or violating privacy, intellectual property, or other lawful rights.
• Uncontrolled resale or sharing:Reselling node access without written confirmation, publicly exposing connection credentials, or allowing unidentified people to share an account.

To assess abnormal activity, we may review necessary account, order, connection, and infrastructure logs, but providing infrastructure does not make us responsible for reviewing your business content. You must ensure that your code, data sources, automated tasks, and team operations comply with applicable rules and the license terms of the third-party tools you use.

Data, Backups, and Credentials

You retain the applicable rights to source code, build artifacts, test data, caches, configuration files, and other business data written to Cloud Mac, and you are responsible for confirming that you have the authorization required to process that data. The platform processes this information only as necessary to provide the node, fulfill orders, troubleshoot issues, conduct security audits, and comply with legal obligations.

You must establish a verifiable backup process yourself. Important repositories, build artifacts, certificate materials, and configuration inventories should not be stored on a single physical node alone. We recommend verifying recovery procedures after the initial deployment and creating an independent backup before changing models, moving regions, ending a period, or making large-scale environment changes.

You are responsible for securely managing passwords, development-tool accounts, certificates, private keys, signing credentials, deployment tokens, and automation keys. Sensitive materials should be isolated by project and environment, access should be limited to those who need it, least-privilege access should be used, and credentials should be rotated promptly after personnel changes or suspected exposure. Do not ask support personnel to receive, store, or manage complete sensitive credentials on your behalf.

When a rental ends, an order is terminated, or a node is reset, data on the node may no longer be accessible. Except for data services expressly included in the order confirmation or another written agreement, the platform does not serve as the repository for your business backups. You must export your data before access ends and verify that the exported files can be read normally.

Availability and Service Adjustments

Nodes are designed to operate normally 365 days a year. The 99.9% availability target measures periods during which a node cannot be accessed normally due to platform-controlled infrastructure within the applicable measurement period. Whether the target applies and the exact measurement scope must be confirmed against the valid order, incident records, and support ticket.

Downtime caused by your own configuration errors, invalid credentials, code or automated tasks exhausting resources, your network, third-party tool failures, user error, restrictions resulting from violations of these terms, or events beyond reasonable control is not counted as a platform-controlled infrastructure failure.

If you cannot connect or a node behaves abnormally, first record the order number, region, time, symptoms, reproduction steps, and redacted logs, then submit a support ticket through the console. Availability is assessed by comparing platform monitoring, node records, and the support-ticket timeline. Once the applicable conditions are met, the form and amount of compensation are determined by the order record, impact, and review outcome. Compensation is not automatically converted to cash and will not exceed the applicable fees for the affected order.

For necessary reasons such as responding to security incidents, isolating urgent failures, meeting legal obligations, or preventing further impact, the platform may temporarily restrict some access or adjust the delivery method. Where possible, we will provide updates through account notifications, console status, or support tickets.

Suspension, Termination, Liability, Disputes, and Updates

If payment remains unconfirmed, account information is materially false, there is a risk of abnormal access, acceptable-use rules are violated, infrastructure security is affected, or you refuse to cooperate with a necessary review, the platform may restrict operations, suspend a node, or terminate the relevant order based on the level of risk. Where circumstances permit, we will explain the reason and required steps. If continued access could cause harm, protective measures may be taken first, followed by notice.

You may stop renewing according to the order status. Ending use early does not automatically change the billing result of a confirmed order unless the order record, applicable rules, or written confirmation by both parties provides otherwise. Before termination, you should export your data, revoke automation keys, remove remote-access authorizations, and retain necessary order and payment records.

To the extent permitted by applicable rules, the platform is responsible for its controlled infrastructure and confirmed deliverables. For losses caused by user configuration, user data, third-party software, external networks, unauthorized account activity, or failure to maintain required backups, responsibility is determined according to each party’s actual control, fault, and verifiable records. Any liability assessment is based on the affected order, direct loss, and the extent permitted by applicable rules.

Notices concerning orders, nodes, or payment status may be sent through account messages, console status updates, support-ticket records, or the account contact email. You must keep your contact information current and promptly review notices relating to service status, security matters, and updates to these terms.

These terms are governed by the laws of the jurisdiction where the platform’s operating entity is located. In a dispute, both parties should first provide order records, a timeline, and specific requests through a support ticket or support email and attempt to resolve the matter through negotiation. If negotiation does not resolve the dispute, either party may bring a claim before a court with jurisdiction in that jurisdiction.

We may update these terms when our service structure, billing processes, security requirements, or applicable rules change. Updates that materially affect user rights or obligations will be communicated through reasonable means. Updated terms apply to orders placed after the stated effective date. Existing orders are governed jointly by the order confirmation, the update notice, and applicable rules.