Cloud Mac Rental Terms

Visiting this website, placing an order, completing payment, receiving connection details, or using a device constitutes the user’s acknowledgment, understanding, and acceptance of these Terms of Service and the rules shown in the order interface. Anyone acting for a team or organization must confirm that they have authority to accept these terms and manage its orders.

These terms are observed by the user and the entity operating the platform. Matters involving applicable law, contract interpretation, and dispute resolution are governed by the law of the jurisdiction where the platform operator is established. Disputes that cannot be resolved through reasonable communication will be handled by a court with jurisdiction in that jurisdiction.

If you do not agree to these terms, stop creating orders or using the service. If you have created an order but have not completed the next steps, you may contact us through a console support ticket or email support@deploymini.com with your order details and specific issue.

DplyMini provides dedicated physical Cloud Mac rentals. Each valid order corresponds to the physical node specified in the order; the device is not a virtual machine. The configuration, storage, node region, and rental period are determined by the confirmed order.

The current catalog includes two available configurations: DeployMini M4 16 and DeployMini M4 24. Additional storage and Thunderbolt 5 linking are separate options; only items explicitly selected and confirmed in the order are included in delivery. Network addresses, connection parameters, and node-side information are based on the actual delivery record.

The service provides a macOS graphical interface and command-line environment for iOS/macOS development, CI/CD, automated builds, testing, and experiments permitted under these terms. You are responsible for confirming that your project’s software versions, dependencies, licenses, memory, storage, and regional connectivity match the selected configuration.

Before placing an order, verify the model, memory, base storage, additional storage, target node, and rental period. Nodes are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West; both models can be ordered in all five locations. Actual availability is determined by the console’s real-time response.

After order confirmation, the delivery status, device details, connection address, rental term, and available management actions are recorded in the console. After receiving the delivery information, promptly verify that the order matches the device record. If the configuration, region, or rental term is incorrect, stop writing important data and submit a console support ticket.

Use the order-linked management entry in the console. Do not modify the connection target or delivery parameters based on information from an unknown source. For remote connection procedures, see the support guide.

The service uses only the daily, weekly, monthly, and quarterly prices listed on the plan page and order confirmation screen. The selected period is the billing unit for that order and does not imply automatic conversion, splitting, or substitution between other periods.

All device, additional storage, and Thunderbolt 5 linking charges are billed and settled in USD. The order total consists of the model, period, node catalog options, and add-ons you select. The final amount is the confirmation shown before you submit the order.

Assess the expected task length before confirming your order. As the rental period approaches its end, allow enough time to export artifacts, migrate project data, revoke temporary credentials, and arrange any continued use.

DplyMini supports only USDT-TRC20 and Visa / Mastercard / Amex via Stripe. Available payment gateways are determined by the backend response when the order is submitted; all amounts are priced and settled in USD.

Verify the payment network, order amount, recipient details, and transaction status. For USDT-TRC20, ensure the selected network matches exactly. For cards, complete the required verification in the payment interface. If an issue results from incorrect input, selecting the wrong network, or duplicate payment attempts, retain the transaction ID and submit a console support ticket immediately.

Do not include complete payment credentials in support requests. To locate a payment, you may provide the order number, transaction ID, payment time, amount, and a redacted screenshot. The platform processes only the transaction status and associated identifiers necessary for order fulfillment, accounting reconciliation, security review, and applicable obligations.

You may use the device for lawful software development, builds, testing, automation, data processing, model inference validation, and audio/video work. You must comply with applicable law, intellectual property rules, software licenses, cybersecurity requirements, and reasonable-use limits.

You must not use the service for unauthorized access, malicious scanning, credential theft, malware distribution, cyberattacks, bypassing access controls, intellectual property infringement, or other unlawful activity. You must not disrupt the node network, platform systems, upstream services, or other users’ normal use.

Persistent abnormal network usage, traffic that materially affects node stability, attempts to bypass technical limits, or concealing high-risk uses may trigger a security review. If asked to cooperate, provide a task description, time, target scope, and redacted logs related to the incident, and promptly stop actions that could increase the impact.

You are responsible for protecting your console account, SSH keys, login credentials, build keys, repository tokens, and other access materials. Different people should use individually attributable credentials. Do not share one private key long-term among multiple people or send sensitive information in chat records, public repositories, or ordinary ticket content.

Limit authorization scope, promptly remove access for people who leave the team, and immediately revoke exposed credentials, rotate tokens, and review recent activity when a compromise is suspected. Device operations performed through your account or authorized credentials are managed by you and your team.

If you detect an unusual login, unknown process, changed connection address, or unexpected configuration change, first stop sensitive tasks and save necessary redacted logs and timestamps. Then report it through a console support ticket. Do not send passwords, private keys, or complete payment credentials in a ticket.

You are responsible for project code, models, assets, caches, build artifacts, configuration files, and credentials stored on the dedicated physical machine. The device is an execution environment and should not be your project data’s only backup location.

Keep independent copies of important data and use encryption, access controls, and integrity checks based on sensitivity. When uploading large files or batches of assets, transfer them in batches and verify checksums. Before cleanup, overwriting, formatting, or broad scripts, confirm the target path and a recoverable copy.

Before the rental period ends, export projects and build artifacts, back up necessary logs and configuration, migrate data still in use, revoke temporary credentials, remove unnecessary sensitive content, and check the order’s next steps in the console. Waiting until after the rental ends to begin migration may prevent tasks from completing as expected.

When handling support requests, the platform needs only redacted information directly relevant to troubleshooting. Do not submit complete project datasets, private keys, passwords, or complete payment credentials by email or ticket. See the Privacy Notice.

All nodes are provided with a target of normal operation 365 days a year. Hardware failures, network issues, upstream service incidents, force majeure, or your own actions may still affect device connectivity, task execution, or data transfer.

When a connection issue occurs, check your local network, DNS, target address, port, credentials, remote service, and node status in the console in that order. For ongoing builds, retain logs, exit codes, and the most recent successful run information to distinguish environment, project, and node issues.

When platform assistance is needed, submit an order-linked ticket through the console with the order number, node, time, client environment, reproduction steps, error message, and redacted logs. The platform will investigate and respond based on the incident’s impact and feasible recovery path.

Impacts caused by force majeure, your own actions, your network, your software configuration, or conduct beyond the authorized scope will be handled according to the cause and applicable rules. Both parties should take reasonable measures to limit further impact and retain the records needed to investigate the incident.

If there is a serious breach of these terms, a clear security risk, unresolved overdue payment, interference with a node or other users, refusal to stop high-risk behavior, or a requirement under applicable law to restrict service, the platform may, based on the level of risk, limit relevant operations, suspend access, or terminate the applicable order.

When conditions permit and doing so will not increase security risk, the platform will explain the issue through console records, tickets, or the contact information associated with the user. After receiving notice, promptly preserve necessary data, stop the prohibited activity, and cooperate with the review. An urgent security incident may require restrictions first, followed by additional incident details.

Each party is responsible for the accounts, systems, data, and actions within its control. Responsibility will be determined based on the order, the actual cause of the incident, reasonable measures taken by both parties, and applicable law. Any limitation of liability applies only to the extent permitted by applicable law.

Reduce single points of failure through backups, least-privilege access, credential rotation, task logs, and reproducible deployment scripts. The platform handles node and delivery issues; you handle project data, software configuration, authorization scope, and team-member actions. Together, these form the complete operational responsibility chain.

These terms were last updated on August 21, 2026. The platform may update them due to changes in service scope, order workflows, security requirements, or applicable obligations. Material changes will be announced prominently on the website, in console records, or through contact information associated with the order.

Updated terms apply to subsequent website access, orders, and service use from the effective time shown on the page. Check the current version before creating a new order or changing a long-term usage plan. Continued use of the service means you accept the terms then in effect.

You may send terms, order, billing, security report, or partnership inquiries to support@deploymini.com. For an existing order, device connection, or urgent operational issue, first log in to the console and submit a support ticket so the request can be linked to the order and node records.

When contacting us, provide the issue type, relevant order number, target node, time, and the terms section you want clarified. Do not send passwords, private keys, or complete payment credentials.