1. Service overview
TestMini provides cloud Mac rentals for users who need a macOS build and development environment. The service runs on Apple Silicon M4 / M4 Pro Mac mini systems. For the duration of your rental, the entire physical machine is dedicated to your order: it is not a virtual machine or a desktop session shared with other users. The service includes allocation of a physical node, remote access, and order management features.
There are currently 5 nodes: Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. Model specifications are listed on the plans page and in your order confirmation. Check the portal for current availability. When choosing a node, consider your network connection: a node’s location alone does not determine remote desktop latency, file transfer speeds, or build times.
After your order is provisioned, sign in to the portal and open the browser-based remote desktop from your instance details. Use the connection method shown for your instance. The macOS desktop and command line are available for setting up your environment, compiling projects, and creating archives. Clipboard and file transfer features depend on the connection method and browser environment; not every local device or action will necessarily be available remotely.
The rental does not include writing business code, guaranteeing project build results, licensing third-party software, or obtaining developer credentials on your behalf. You are responsible for checking that your frameworks, dependencies, toolchain versions, and projects are compatible, and for having the rights needed to use your projects, software, and signing materials. For connection or environment setup issues, see our support guide.
2. Billing periods
Choose from four billing periods: daily, weekly, monthly, or quarterly. The minimum rental period is 1 day. Model prices and add-on prices, including storage upgrades and Thunderbolt 5 daisy-chaining, are listed on the plans page. Before placing an order, check the selected configuration, billing period, quantity, and order total. All charges are in US dollars (USD); we do not quote prices in local currencies in addition to the currency displayed on the page.
Each billing period has its own price. A daily rate multiplied by the number of days is not the weekly, monthly, or quarterly price. Add-ons apply to the configuration selected in your order. Check the checkout confirmation for availability and the amount due. If the listed price, configuration, or total does not match before payment, verify it through a portal support ticket rather than paying an amount you calculated yourself.
Your rental start and end times are based on the order or instance record in the portal. They are not determined by when you first open the remote desktop, run a build, or how long you actively use the machine. Disconnecting, closing your browser, or temporarily not using the machine does not end the order or change your selected period to per-minute billing.
If you need continued access, check the renewal options, renewal price, and new expiry time before your current period ends. For billing questions, cancellation requests, or refund requests on a paid order, submit a support ticket. Our support team will review the payment status, provisioning records, and service delivered. Submitting a request does not mean a refund has been approved, and nothing in these terms limits rights granted to you by applicable law.
3. Payment methods
We accept USDT-TRC20 and Visa / Mastercard / Amex card payments processed by Stripe. Orders are charged in US dollars. Payment gateway availability is determined by the response from our backend; use only the payment option and details shown at checkout for your order.
For USDT-TRC20 payments, check the required network, recipient details, amount, and order reference. Payment is complete only when confirmed in your order record. Initiating a transfer or sending a transaction screenshot does not mean the order has been confirmed. Network confirmation times and fees may affect processing. If the status does not update, keep your transaction hash and submit a support ticket.
Card authorisation and verification are handled by Stripe and your card issuer. If verification is incomplete, authorisation fails, or payment is still processing, check the order status before trying again to avoid duplicate payments. TestMini does not store full card numbers. See our Privacy Policy for information about payment data handling.
If you are charged more than once, the amount is incorrect, or a payment is not linked to your order, provide your order number, payment method, amount, and transaction evidence. Do not send full card details, verification codes, private keys, or other payment secrets in a support ticket or email.
4. Provisioning, renewals, and expiry
Once payment is confirmed, the system assigns a physical node and sets up macOS according to your order configuration. Payment confirmation, node allocation, and environment setup are separate steps; a completed payment does not mean the machine is ready to connect. Check the instance status and connection details in the portal. If the configuration is incorrect or you cannot connect, keep your order number and error details, then submit a support ticket.
Renewals must be completed before the current rental period ends and are subject to the confirmation shown in the portal. An incomplete payment, an unsubmitted renewal selection, or an email asking about renewal does not count as a completed renewal. If you need to change nodes or models, or migrate a project, confirm the process first. Existing orders do not automatically include cross-node migration or transfer of data from the original disk.
If you do not renew before expiry, access to the instance may be stopped, and the node will enter the recovery and disk data deletion process. Before expiry, commit your code, download build artifacts, and back up and remove certificates, provisioning profiles, and other materials you need. Rental disks are not long-term backup storage. Do not rely on being able to access the instance or recover files after expiry.
The timing and scope of data deletion depend on the instance status. These terms do not promise a standard retention period after expiry or a fixed recovery time. Data that has been deleted cannot be guaranteed to be recoverable. If you still need to export files near expiry, check your renewal status and submit a support ticket promptly. Do not wait until access has been stopped to move your only copy.
5. Acceptable use
You must have the right to access and use the code, data, software, and signing materials on your instance, and you are responsible for everything you deploy and run there. Keep your portal credentials, remote access details, and project secrets secure. Grant access only to collaborators who are authorised and need it. If multiple team members use different machines, confirm the order and responsibility for each one.
You may not use the service for unauthorised intrusion, exploiting vulnerabilities, stealing credentials, distributing malware, denial-of-service attacks, sending spam, or other activity that harms third-party systems or networks. You may not bypass access controls, disrupt other nodes, probe unauthorised resources, or obtain the service through fraudulent payment or identity theft.
You may not store, distribute, or process content you are not entitled to use, or engage in conduct that infringes privacy, intellectual property, or other legal rights. When using automated builds, self-hosted runners, or large-scale data jobs, check access permissions and network impact. Access to a dedicated physical machine does not authorise attacks on other systems or use of resources outside your order.
If we identify a security risk or reasonable indications of a violation, we may restrict access, pause relevant tasks, or stop the affected instance based on the risk, and explain our actions through an available account contact method. An urgent risk may require immediate isolation. You can request a review through a support ticket with an explanation of your use and any relevant evidence. Any action should be proportionate to the risk; a single report does not establish that all use of the service is in breach.
6. Availability and interruptions
All nodes operate year-round, 365 days a year. Continuous service does not amount to an unconditional guarantee for every network connection, individual session, or project outcome. Hardware issues, upstream network failures, events beyond our reasonable control, and your own configuration or actions may affect access to a particular instance or the execution of a task.
If you cannot connect, experience an unexpected restart, or have an interrupted build, note your order number, node, when the issue occurred, connection method, error message, and steps already taken. Then submit a support ticket through the portal. Remote desktop lag does not necessarily mean the physical machine has failed; check your local network, connection route, display settings, and workload on the remote machine separately.
If an incident affects your use of the service or requires an emergency response, we will share relevant updates through an appropriate channel, such as a portal support ticket, an account notification, or your registered email address. If we need you to confirm a restart, data migration, or another action that could affect your current tasks, review the scope in the notification. Urgent security actions are handled under Section 5.
We will assess the cause of an interruption, its actual impact, and any follow-up based on the order, instance, and support ticket records. You may use this information to request a billing review or other appropriate resolution. This page does not promise a recovery time, uptime percentage, or fixed compensation multiplier unless one is expressly stated in your order.
7. Limitation of liability
We will provide the rental service with the configuration confirmed in your order and handle issues relating to delivery, connectivity, and billing. You are responsible for promptly checking that your instance matches your order, protecting your access credentials, and saving your project and build artifacts before important operations. Both parties should take reasonable steps to prevent foreseeable losses from increasing.
Whether a project compiles, can be archived, passes signing verification, or meets release review requirements depends on the code, dependencies, authorisation materials, and applicable platform rules. Renting a machine does not guarantee any of these outcomes. Responsibility for problems caused by errors in your project, changes to third-party services, or your own modifications to the system environment must be assessed based on the circumstances. An unfinished task alone does not mean the rental service was not delivered.
We will assess claims involving data loss, additional expenses, or business impact based on service records, causation, and verifiable evidence. Failure to back up before expiry, compromised credentials, and destructive operations performed without confirmation may affect that assessment. This does not waive any liability we are required to accept by law or limit user rights that cannot be excluded or restricted under applicable law.
If you identify a delivery issue, preserve relevant evidence and submit a support ticket promptly instead of repeatedly performing actions that could overwrite logs or damage data. If troubleshooting may involve sensitive information, remove unrelated secrets first and agree on the necessary scope. The Privacy Policy governs the handling of account information and connection logs.
8. Changes and dispute resolution
We may update these terms to reflect changes to service features, billing processes, security requirements, or compliance needs. Updated versions will be published on this page with their effective date. We will notify you through an appropriate account channel about changes that materially affect how you use the service or your existing rights and obligations. Changes to prices on this page will not automatically alter the amount confirmed for an existing order.
Read the terms and order details in effect before placing an order. When renewing or making a new purchase, check the configuration, amount, rental period, and applicable rules again. If you have questions about a change or how it applies to an existing order, submit a support ticket for clarification. A change in page wording alone does not mean that an existing order has been cancelled or extended.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. If a dispute arises, both parties should first exchange order records, relevant facts, and requested resolutions through the support channel and attempt to resolve the matter by agreement. If no agreement can be reached, the dispute will be handled by a court with jurisdiction in that jurisdiction. Any provisions of applicable law that cannot be excluded by contract remain in force.
Send questions about these terms, order disputes, or security issues to support@testmini.com. For existing orders, please sign in to the portal and submit a support ticket. Include your order number, what happened, and how you would like us to resolve the issue so we can link the conversation to the right instance.