Rules and responsibilities for Cloud Mac rentals

When you create a ZoomMini account, place an order, complete payment, or use a Cloud Mac service, you confirm that you have read, understood, and agree to be bound by these Terms and the configuration shown on the order page. Users acting for an organization also confirm that they are authorized to accept these Terms and manage orders on its behalf.

You must be legally able to enter into contracts and use the relevant computing resources. You must keep your account details, billing information, and required verification data truthful, accurate, and up to date. You may not impersonate another person, use an unauthorized payment instrument, or use multiple accounts to bypass risk controls or service limits.

Accounts are for authorized personnel only. Customers must securely manage login credentials, SSH keys, and team-member permissions and are responsible for orders, configuration changes, remote connections, and support requests made through their account. If you suspect unauthorized access, immediately restrict the affected credentials and submit a support ticket through the portal.

ZoomMini provides Cloud Macs based on Apple Silicon. Each active order corresponds to one dedicated physical machine, which the customer uses exclusively during the rental term. The service is not a shared virtual machine, and resources from the same order are not mixed with sessions belonging to other customers.

Only two configurations are available: ZoomMini M4 Core with an M4 chip, 16GB of memory, and a 256GB SSD; and ZoomMini M4 Plus with an M4 chip, 24GB of memory, and a 512GB SSD. At checkout, customers can choose Singapore, Japan (Tokyo), South Korea (Seoul), or Hong Kong—4 nodes in total. Real-time availability for each combination is shown in the portal.

Rental terms are available by day, week, month, or quarter. Optional add-ons include +1TB SSD, +2TB SSD, and device-billed Thunderbolt 5 parallel connections. An add-on becomes part of the service only when explicitly selected and confirmed in the order; it is not included automatically with the base configuration.

Service boundaries

• Physical node: ZoomMini operates the physical equipment, node network, and related portal services.
• System use: Customers may use the macOS graphical interface and command line and configure their own development tools, runners, and application environments.
• Customer workloads: Customers manage their own code, repository permissions, signing materials, build caches, application data, and backups.
• Remote access: Connection details, assigned credentials, device status, and rental-term information are determined by the portal.

Orders are priced according to the selected model, node, daily/weekly/monthly/quarterly rental term, and add-ons. All listed prices, invoices, and settlements are in US dollars (USD). Before paying, customers should verify the base configuration, rental term, SSD upgrade, number of Thunderbolt 5 parallel connections, subtotal, and total due.

ZoomMini supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways, payment confirmation, and order status are determined in real time by the backend. Customers must ensure that payment details are accurate and are responsible for processing delays caused by an incorrect address, network selection, or payment information.

Add-ons are listed separately from the base configuration. After confirming an order, customers may not request that equipment usage or service delivery already incurred be disregarded because they did not read the configuration summary, verify the term, or selected the wrong node. If you have a billing question, retain the order ID and payment record and submit a support ticket through the portal.

Device delivery is determined by the order and instance status shown in the portal. After payment is confirmed, an order may progress through pending confirmation, configuring, and ready to connect. Treat the device as delivered only after the portal shows its status, node, connection details, and rental start and end times.

Delivery time depends on order confirmation, the selected configuration, and any required risk verification. The portal confirmation controls. Customers should promptly verify the node, model, and rental term; if the record does not match the order summary, submit a support ticket before deploying workloads.

A renewal does not automatically create a new rental term. Before the current term ends, customers must open the portal to confirm availability, renewal term, add-ons, and amount due, then complete payment. A renewal takes effect only after the system confirms the order and payment; the portal’s real-time result controls.

Customers should monitor the expiration time and move out code, build artifacts, keys, logs, and other data they need to retain before the rental term ends. After expiration, remote access may be disabled and the device may enter the reclamation process. Content not moved in advance should not be treated as long-term storage or backup.

Post-delivery checklist

1. Verify the model, node, rental start and end times, and add-ons.
2. Verify the assigned credentials and SSH host fingerprint, and confirm that the connection target is correct.
3. Rotate necessary credentials, configure SSH public keys, and remove unnecessary access permissions.
4. Run a basic build verification and create independent backups of important code and data.

Customers may use the service only for lawful and authorized development, building, testing, automation, and research. Use of the service must not harm ZoomMini, other customers, the node network, or the systems, data, or lawful rights of any third party.

The following activities are expressly prohibited:

• Conducting, assisting with, or promoting activities that violate applicable rules, or processing data or content that is clearly unlawful in origin.
• Scanning, probing, accessing, or controlling third-party accounts, devices, networks, or services without explicit authorization.
• Launching denial-of-service attacks, malicious traffic, credential stuffing, bulk spam, or any other activity that disrupts network stability.
• Bypassing authentication, access restrictions, risk controls, billing mechanisms, or node security measures.
• Distributing malware, concealing the source of an attack, or using a device as a relay for unauthorized access or data theft.
• Infringing the intellectual property, privacy, trade secrets, or other protected rights of a third party.
• Disassembling or modifying physical equipment without authorization, interfering with node facilities, or attempting to control a device not covered by the current order.

Customers must set reasonable concurrency, retry, and rate limits for automated tasks. If a script runs out of control, abnormal traffic occurs, or credentials are exposed, immediately stop the relevant workload, rotate secrets, and retain necessary redacted logs.

ZoomMini targets 99.9% availability for nodes operating continuously 365 days a year. This target measures whether the physical node, node network, and necessary control services operated by ZoomMini can support customer access to a delivered device.

Unavailability caused by customer actions, system configuration, application failures, invalid credentials, code or dependency issues, local networks, remote clients, third-party repositories, or force majeure is outside ZoomMini’s service target. Interruptions caused by a customer restarting or shutting down the device, deleting permissions, or changing network configuration likewise do not constitute platform unavailability.

If a customer believes the service did not meet the target, they must submit a support ticket through the portal with the order ID, node, start and end times of the impact, connection method, reproduction steps, and redacted logs. ZoomMini will assess the scope using node records, control-service records, and the information provided by the customer.

Eligible requests may receive service credits after review. Service credits can be applied to future eligible ZoomMini service charges and are not redeemable for cash. The amount depends on the affected order, duration of the impact, and review outcome.

If payment is overdue, reversed, account verification is incomplete, a material risk event occurs, acceptable-use rules are violated, or required by applicable rules, ZoomMini may, based on the level of risk, restrict order operations, suspend remote access, isolate affected workloads, or terminate the service.

Where an issue can be safely corrected without increasing risk, ZoomMini may require the customer to complete payment, rotate credentials, stop a prohibited task, or provide necessary verification through the specified process. For ongoing attacks, unauthorized access, data destruction, evasion of security controls, or conduct that may affect other nodes, ZoomMini may take protective measures first and then notify the customer through account records or the support process.

A suspension does not automatically extend the rental term or waive valid charges incurred before the suspension. If suspension results from customer misconduct, nonpayment, or the customer’s own security incident, the customer remains responsible for migrating data, preserving evidence, and handling its workloads.

Customers may choose not to renew. Before ending use, remove access permissions that are no longer needed, migrate necessary data, and review outstanding invoices and tickets. After termination, customers must not continue attempting to access the original device address or use connection credentials that are no longer valid.

ZoomMini is responsible for the physical nodes, node network, order records, and control services within its control. Customers are responsible for account permissions, system configuration, code, repository tokens, SSH keys, signing materials, application data, build results, workload legality, and independent backups.

Customers should use least-privilege access, unique credentials, and verifiable backups, and promptly revoke access when a team member leaves, device use changes, or a compromise is suspected. Customers are responsible for losses caused by failing to back up data, misconfiguring systems, running incompatible software, or disclosing credentials to unauthorized persons.

When either party claims a breach or loss, it must provide reasonable information identifying the order, scope of the event, and time affected, and first attempt to resolve the matter through the support process. Notices may be sent to support@zoommini.com, and existing customers may alsolog in to the portal to submit a support ticket.

To the extent permitted by applicable rules, ZoomMini’s liability for the service is limited to direct, verifiable losses related to the affected order. ZoomMini is not liable for indirect losses, anticipated profits, business opportunities, customer data that was not backed up, or third-party claims arising from customer workloads, except to the extent liability is mandatory under applicable rules.

The formation, interpretation, performance, and dispute resolution of these Terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first seek to resolve disputes through good-faith communication. If negotiation fails, either party may bring proceedings before a court with jurisdiction in that jurisdiction.

If any provision of these Terms is found to be unenforceable, the remaining provisions will continue in effect. ZoomMini may update these Terms due to changes in service scope, risk controls, or applicable rules. Material updates will be communicated through a visible notice on the platform or an account notification, and the updated Terms apply to orders created or continued after they take effect.