Cloud Mac Rental Service Terms

Agreement and eligibility

By creating an order in the console, confirming the configuration, completing payment, renewing a node, or accessing the delivered Cloud Mac, you accept these terms electronically. If you disagree with any provision, stop the order before payment; orders already in use remain subject to the version displayed and accepted at the time of purchase.

Account and identity information

• The email address, billing details, order purpose, and contact information you provide must be truthful, accurate, and kept active so you can receive delivery updates, security notifications, and billing records.
• You must protect your console login credentials and must not share them with anyone who is not authorized to manage the order. Configuration changes, renewals, and support tickets submitted through a valid account are treated as actions authorized by the account holder.
• If you notice unusual account access, compromised credentials, or unauthorized order activity, change your credentials immediately and submit a support ticket through the console or email support@minideploy.com.

Ordering on behalf of an organization

Anyone ordering on behalf of a company, team, or other organization confirms that they have the necessary authority to accept these terms, use the organization’s payment method, and manage related workloads. They must also ensure that members using the node understand the access-control, backup, and acceptable-use requirements. Unclear internal authorization or incorrect permission assignments do not affect the validity of a confirmed order.

Service definition

MiniDeploy Cloud Mac provides a dedicated physical machine delivered to order, not a virtual machine. During the active rental term, each tenant exclusively uses the chip, memory, built-in storage, and system environment of the assigned Mac mini; computing resources on the device are not shared with other tenants.

An order is defined by four fields: model, region, rental term, and add-ons. The current base model is M4 Core, configured as Mac Mini M4 / 16GB RAM / 256GB SSD. Available regions are limited to Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Western United States. Final assignment depends on real-time inventory when payment is confirmed.

Resources included in an order

• The physical node, base storage, rental period, and selected storage or interconnect add-ons explicitly listed on the order confirmation page.
• The system account, temporary credentials, and necessary node address information used to access the node.
• The ability to manage the order, renewals, node status, and support tickets through the console during the rental term.

Items outside the order

Software licenses, third-party development-tool subscriptions, code repositories, artifact storage, domains, external network connections, and internal team-permission management are not automatically part of the service unless listed in the order. You are responsible for confirming the license terms, version compatibility, and configuration requirements of software your workflow depends on.

Delivery and access

After payment is confirmed, the system locks the resources, prepares the system, and issues credentials in sequence. Standard delivery takes approximately 4 minutes: payment confirmation about 30 seconds, resource locking about 30 seconds, system preparation about 2 minutes, and credential issuance about 1 minute. These timings describe the normal process and are not a second-by-second guarantee for every order.

Availability criteria

Delivery is considered complete when the console shows that the node has been assigned and provides a valid node address, system account, and temporary credentials, and the node responds through an available SSH or remote desktop method. If your local network, client settings, or access-source restrictions prevent a connection, first follow the troubleshooting sequence on the support page to rule out local connectivity issues.

First-login checks

1. Confirm that the node ID, region, and order configuration in the console match your purchase record.
2. Use the temporary credentials for the first connection, then immediately replace them with unique, strong credentials.
3. Check the chip, memory, storage capacity, system time, and network connectivity.
4. Restrict SSH and VNC access sources as needed, and remove temporary keys you no longer use.
5. Before deploying project data, run a small build or connection test to confirm that the toolchain and connection meet your expectations.

Orders, renewals, configuration records, and support requests are managed in the console. You must check the expiration time before the rental term ends; the account holder is responsible for consequences resulting from missed notices, incomplete renewals, or incorrect console operations.

Pricing and rental terms

Prices are shown for four fixed periods—day, week, month, and quarter—and are all denominated in USD. The system calculates the order total from the selected model, period, and add-ons. No model, term price, or custom quote not listed on the plans page is available. Before submitting payment, verify the region, rental term, storage capacity, and number of Thunderbolt 5 interconnects.

Billing confirmation rules

• The base model price and selected add-ons are calculated separately and shown in an order summary that can be reviewed before payment.
• Each period is an independent pricing unit. Use the period selected at checkout rather than calculating weekly, monthly, or quarterly prices from the daily rate.
• Thunderbolt 5 interconnects are billed per unit and apply to multi-machine workflows explicitly configured in the order; they are not included by default when not selected.
• Renewals use the order information displayed and confirmed in the console. Recheck the price, node, and add-ons before payment.

Payment and settlement

The service supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) . These are the only two payment methods, and all orders are settled in USD. Available gateways, payment status, and confirmation results are determined by the console backend response.

Payment verification

• When using USDT-TRC20, verify the network, recipient details, and order amount carefully. Associate the on-chain transfer record with the corresponding order.
• For Visa, Mastercard, or Amex payments, the payment result is determined by the authorization or failure status returned by Stripe.
• If a payment shows as processing, do not submit payment again for the same order. Refresh the console status first; if it remains unchanged for an extended period, submit the order number and payment time in a support ticket.
• For billing issues, provide the order number, amount, payment time, and a redacted record suitable for verification. Do not send full card details, private keys, or account passwords by email or support ticket.

If an order is not confirmed because of incorrect payment information, an incorrect on-chain network, issuer refusal, insufficient funds, or payment risk controls, the resources will not enter the formal delivery process. After confirming successful payment, use the order status in the console to determine whether node preparation has started.

Acceptable use

Cloud Mac may be used for lawful, authorized development, builds, testing, experimentation, and media workflows that do not harm the platform, node network, or third-party interests. You are responsible for commands run under your account, installed software, uploaded data, network requests, and automated tasks.

Prohibited activities

• Conducting illegal activity or storing, processing, or distributing content prohibited by applicable law.
• Scanning, probing, bypassing, or attempting to access any account, system, network, interface, or data without explicit authorization.
• Creating, deploying, or distributing malicious code, or conducting phishing, credential theft, extortion, destruction, covert control, or security-detection evasion.
• Affecting the node network, console, or other users through sustained abnormal traffic, automated abuse, offensive requests, or other means.
• Infringing copyrights, trademarks, privacy rights, trade secrets, or other third-party rights.
• Reselling, subletting, or sharing node access with unauthorized people in a way that makes the actual operator or responsible party impossible to identify.
• Tampering with resource identifiers, evading billing controls, interfering with audit records, or attempting to exceed the hardware and access boundaries of the order.

Automated builds, self-hosted runners, test bots, and batch jobs are allowed, but configure concurrency limits, failure-exit conditions, log rotation, and disk quotas to prevent runaway loops from exhausting storage or generating persistent abnormal network requests.

Data and backups

You are responsible for managing project source code, databases, model files, signing materials, keys, build caches, media assets, logs, and output artifacts on the Cloud Mac. Dedicated physical resources do not replace version control, off-site backups, or your team’s data-recovery process.

Minimum backup requirements

1. Sync source code to a repository you control and verify that critical branches can be checked out from another environment.
2. Store signing materials, keys, and environment variables in encrypted form; do not keep them only on one node.
3. Create independent copies of large models, media assets, and build artifacts according to recovery objectives, and record integrity checksums.
4. Create a verifiable recovery point before system upgrades, disk repartitioning, major toolchain changes, or bulk deletion.
5. Export data before the rental term ends, including repository commits, artifact downloads, key revocation, and removal of temporary access permissions.

After the rental term expires, the order ends, or the node is reclaimed, do not continue relying on the device as the only copy of your data. If you need more time to export data, confirm a renewal while the current term is active rather than waiting for access to be restored after expiration.

Availability and incident handling

All nodes operate normally 365 daysa year, with no prearranged downtime periods. The platform continuously provides node networking, power, device status, and console management; your actual remote experience may still be affected by your local network, carrier routing, client configuration, and workload resource usage.

Hardware or network incidents

In the event of hardware failure, regional network disruption, a power incident, or another unexpected problem, the platform will diagnose the node and may restore access, handle the hardware, or adjust resources based on node status. Provide the node ID, time of occurrence, connection method, client city, reproduction steps, and redacted logs to help distinguish node failures from client connectivity issues.

Resource adjustments may involve reissuing credentials, changing the access address, or moving the workload to an available device after your confirmation. When data is moved, confirm that backups exist first and assess synchronization time, toolchain paths, and access-source rules.

Regional inventory changes

Inventory in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Western United States changes dynamically as orders are allocated and released. For orders submitted but not yet locked, the final console status controls. Before changing regions, reassess remote-desktop latency, repository location, artifact transfer paths, and the cost of synchronizing large datasets.

Suspension and termination

To protect nodes, the platform network, other users, and third-party interests, the platform may impose access restrictions proportionate to the risk when a clear risk or rule violation exists. The basis may include verifiable order status, security records, network behavior, support-ticket materials, and applicable legal requirements.

Circumstances that may trigger restrictions

• The order expires, renewal is incomplete, payment fails, or billing status cannot be confirmed.
• Unauthorized access, malicious-code distribution, resource abuse, or infringement prohibited by these terms.
• Compromised account credentials, unusual access sources, or node behavior indicating an immediate security risk.
• Materially false information provided by the user, or an organization order placed without the necessary authorization.
• The platform receives a binding legal request requiring it to restrict resources or retain necessary records.

Process

When circumstances permit, the platform will notify you by account email or through the console of the issue type, required materials, and available corrective steps. Stop the relevant tasks, protect existing data, revoke compromised credentials, and provide an explanation as requested. If the risk continues, the violation is serious, corrective measures are not completed, or legal requirements require action, the affected order may be terminated.

Urgent security incidents may require access to be restricted before facts are verified. A restriction does not change your responsibility to back up and export data before the rental term ends; restoration of access depends on whether the risk has been resolved, node status, and the applicable process.

Liability and disputes

The platform is responsible for providing the Cloud Mac resources specified in the confirmed order, node-management records, and support process. You are responsible for your workloads, client network, account permissions, third-party tool configuration, software licenses, data backups, and usage. When handling an issue, logs, timestamps, and reproducible results should be used to distinguish the effects of platform resources, user configuration, and external dependencies.

Third-party tools and indirect losses

Xcode, fastlane, repository clients, VNC clients, build dependencies, and other third-party software are controlled by their respective providers, including their versions, licenses, and functionality. The platform may help identify node-environment issues, but changes to third-party tools, interfaces, or licenses do not automatically constitute failure to deliver Cloud Mac resources.

To the extent permitted by applicable law, neither party is liable for reasonably unforeseeable indirect, opportunity, or lost-profit damages, or for losses increased by the other party’s failure to meet backup and security obligations. Direct losses should be assessed in light of the actual order, verifiable records, causation, and whether the affected party took reasonable steps to mitigate the loss.

Reporting and resolving issues

1. First submit a support ticket through the console with the order number, node ID, time of occurrence, reproduction steps, expected result, actual result, and redacted logs.
2. For billing issues or inability to access the console, email support@minideploy.comand retain order materials suitable for verification.
3. The parties should first negotiate in good faith based on order records, node logs, and communications, defining the scope of the dispute and an actionable solution.
4. If negotiation does not resolve the issue, these terms are governed by the laws of the jurisdiction where the platform operator is based, and the dispute will be submitted to a court with jurisdiction in that jurisdiction.

Updates to these terms

When these terms are updated because of changes to service processes, product configurations, security requirements, or applicable rules, the page will show a new effective date. Material changes affecting existing orders will be communicated by account email or through the console. Updated terms apply to orders submitted or expressly renewed after their effective date, except where applicable law requires otherwise.