Cloud Mac Rental Terms of Service

GPUMini provides dedicated physical Cloud Mac rental services for development, automated builds, and experimental workloads. Each delivered instance corresponds to one physical Mac node reserved exclusively for that order. It is not a virtual machine, and its processor, memory, or system-disk workspace is not shared with other tenants.

The service includes order configuration, node initialization, delivery of connection details, instance status management, billing records, and support tickets. Through the console, users select a plan, rental period, node, and add-ons, then use the macOS graphical interface or command-line environment through approved remote connection methods after delivery.

The service does not include project development, code review, guaranteed build results, third-party software licenses, repository permission configuration, or hosting of business data. Optional software, storage expansions, or Thunderbolt connection options must follow the settings and charges shown on the order confirmation page.

Users must provide accurate, reachable information suitable for receiving security notifications and securely protect console credentials, node connection credentials, keys, and recovery information. Orders, configuration changes, tickets, and node operations initiated under an account are considered actions of the account holder or an authorized representative.

For team use, the account holder must define authorization scopes, grant access only to members who need it, and promptly revoke access when a member leaves the project, changes roles, or may have exposed credentials. Shared passwords, credentials stored on public devices, keys committed to public repositories, and node details forwarded to unrelated people all increase the risk of unauthorized access.

If you detect an unusual login, unknown order, exposed credential, or unexpected node behavior, immediately update the relevant credentials and use a console ticket or email support@gpumini.com with the order identifier, time of occurrence, and steps already taken. Do not submit account passwords, private keys, or unredacted sensitive data.

Users may choose daily, weekly, monthly, or quarterly rental periods. Before an order is placed, the confirmation page lists the selected plan, physical node, rental period, storage expansion, Thunderbolt 5 option, amount due, and available payment methods. Review each item before paying.

Each device model has its own catalog price for each billing period; a price for one period cannot be treated as a simple fixed multiple of another. The amount shown on the order confirmation page governs this transaction. If you return to change the model, node, period, or add-on, the amount is recalculated from the selected catalog options.

The model-and-region combinations in the node catalog are based on the real-time availability returned by the console. Payment does not allow users to substitute configurations not included in the order. To upgrade storage, change a Thunderbolt connection option, or adjust the rental period, first submit the new configuration or a support request, confirm the impact on current tasks and data migration, and then proceed.

The rental period begins at the service start time recorded for the order. Before the period ends, users should archive projects, migrate data, and remove connection credentials. Handle renewal before the current period ends to avoid interrupting long-running tasks.

GPUMini supports only two payment methods: USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are priced and settled in US dollars (USD). The payment gateway actually available is the one returned by the console at checkout.

Users must ensure that the payment amount, network, recipient details, and order identifier match the checkout page. After broadcasting a digital-asset transfer, retain the transaction ID for verification. Card-payment verification and results are returned through the applicable payment flow. If incomplete payment details prevent automatic order matching, submit the order number and a redacted payment receipt through a console ticket.

Applicable taxes, bank fees, blockchain transfer fees, and other charges imposed by a payment provider are shown during payment or borne by the user, as applicable to the user’s circumstances. GPUMini retains transaction-linked records necessary to deliver orders, reconcile finances, and meet legal obligations. See thePrivacy Policy.

Users may use nodes for lawful software development, automated testing, continuous integration, builds, remote development, and computing experiments. All activities must comply with applicable laws, software licenses, repository rules, and authorization agreements between the user and third parties.

Users must not use the service for unlawful activity, unauthorized access, credential theft, malware distribution, denial-of-service attacks, scanning or attacking unauthorized targets, bypassing access controls, intellectual-property infringement, unlawful content distribution, or sustained abnormal use of network or system resources that affects node infrastructure.

Users must not attempt to access other tenants, management networks, underlying scheduling systems, or devices outside the order. They must not remove configurations necessary to identify hardware, record delivery status, or keep the node operating. Security research, stress testing, and network scanning are permitted only within targets for which the user has explicit authorization.

When systems detect activity that may affect infrastructure security or third-party rights, GPUMini may ask the user to explain the purpose, provide proof of authorization, or stop the relevant processes. Users must help preserve necessary logs, isolate risky workloads, and avoid sending unredacted keys, customer data, or repository credentials in communications.

After order confirmation, the system initializes the node according to the selected model and region and updates delivery status in the console. Upon delivery, users should verify the host details, configuration, system time, disk space, and connection method, then run a repeatable test build to confirm that the environment meets their requirements.

All nodes are designed to run continuously 365 days a year. If hardware failure, network disruption, a security incident, infrastructure risk, or force majeure occurs, GPUMini may take necessary emergency action, including isolating connections, restarting relevant components, moving service processes, or temporarily restricting affected operations, with progress reported through console status or tickets.

Software installed by the user, firewall changes, modified remote-access settings, deleted system components, exhausted disk space, or altered network configuration may make a node unreachable or cause tasks to fail. To restore a node after user configuration changes, support may request the change time, commands executed, error messages, and redacted logs, then provide steps based on what can be recovered.

If necessary action may affect running tasks, GPUMini will provide a status explanation when conditions allow. Users should still configure recovery mechanisms for long-running builds and store source code, build artifacts, and key configuration in independent locations so that one node is not the sole copy.

GPUMini targets 99.9% availability for each applicable service month. Availability is assessed as the proportion of time during that month when the affected node can normally accept authorized connections and perform basic computing tasks. Relevant events are confirmed using platform status records, infrastructure logs, and support-ticket information.

The uptime target excludes failures of the user’s device or local network, user configuration errors, user-initiated shutdowns or restarts, invalid credentials, exhausted disk space, third-party software failures, unavailable external repositories or dependencies, restrictions resulting from unlawful or high-risk use, and force-majeure impacts beyond reasonable control.

If users believe an event qualifies for service-credit treatment, they must submit a console ticket with the order identifier, node, start time, duration, connection method, error details, and redacted logs. GPUMini will verify platform records and process the matter under the applicable monthly service-credit rules. Service credits apply only to subsequent billing within the relevant service relationship and do not directly alter historical order records.

Users retain the applicable rights to and responsibility for managing project files, source code, build artifacts, certificates, keys, configurations, and business data they upload, generate, process, or export. Users must ensure that their processing has a lawful basis and must not place data on a node without the right to use it.

A dedicated physical node is not a backup service. Users should maintain independent backups, store important code in a controlled repository, sync build artifacts to separate storage, and document the software versions, environment variables, and configuration steps needed to restore a project. Files stored only on a rented node may not be a reliable recovery source after hardware issues, accidental actions, or the end of the rental period.

Before the rental period ends, users should migrate data, download necessary logs, revoke temporary access, remove unneeded sensitive files, and verify that independent copies work correctly. For team handoffs, also record the node, project paths, connection method, task status, and result of the last successful build.

GPUMini processes necessary account, order, device, and log information for delivery, diagnostics, security, and billing support. The Privacy Policy governs the information categories, purposes of use, retention scope, and ways to submit rights requests.Privacy Policy.

GPUMini may restrict relevant operations, suspend node access, or terminate affected services when payment is incomplete, an order presents a risk, an account shows abnormal access, the user violates acceptable-use rules, node activity threatens infrastructure or third-party rights, or action is required by law.

Except where a security risk requires immediate control, GPUMini will use reasonable efforts to explain the reason and available steps through account notifications, console status, or tickets. After identity verification, payment reconciliation, risk remediation, or correction of a violation, GPUMini will assess whether to restore access based on the nature of the event.

During suspension, users must not evade restrictions through new accounts, duplicate orders, proxy access, or other technical means. If secure data export remains possible before termination takes effect, users should migrate data promptly as instructed. Where there is an ongoing attack, unlawful content, exposed credentials, or risk to third-party rights, isolation measures may take priority.

When users decide not to renew, they should complete data migration and credential cleanup before the current rental period ends. Termination does not affect payment, billing, usage records, security-incident handling, or obligations that arose before termination or must continue under applicable law.

Each party is responsible for actions within its control. GPUMini is responsible for providing the Cloud Mac dedicated physical node and related console and support processes described in the order confirmation. Users are responsible for account security, lawful use, software licenses, project configuration, data backups, actions by authorized personnel, and data migration before the rental period ends.

To the extent permitted by applicable law, responsibility for indirect losses, changes in expected revenue, lost business opportunities, or task interruptions caused by the user’s local network or configuration, third-party software, or external services will be determined based on actual causation, each party’s control, and reasonable measures taken. No allocation of responsibility excludes statutory rights that cannot be limited under applicable law.

Notices concerning orders, nodes, payments, uptime, or data processing may be delivered to the account email address, through console messages, or via tickets. Users must promptly update changed contact details. Support requests should include verifiable information and must not contain passwords, private keys, or unredacted data.

These Terms may be updated as service features, billing processes, security requirements, or legal obligations change. Material changes will be announced on the site or in the console. The updated version applies to subsequent orders and continued use from its published effective time; the core configuration and amount of a confirmed order remain governed by that order’s records.

These Terms are governed by the laws of the jurisdiction where the platform operator is established. For disputes, the parties should first seek to resolve the matter in good faith through support@gpumini.com or a console ticket. If no resolution is reached, the dispute will be handled by a court with jurisdiction in that jurisdiction.