Acceptance and eligibility
Accessing this website, placing an order, paying fees, receiving connection details, or using a device means that you have read and accepted these terms. If you act for a company, organization, or team, you confirm that you are authorized to accept these terms, place orders, and manage devices on its behalf.
You must have the legal capacity required to enter into and perform a service agreement and must provide truthful, accurate, and reachable contact information. Team account administrators are responsible for informing actual users of these terms and ensuring that their activity stays within the order scope and applicable rules.
If you do not agree to these terms, stop placing orders or using the device. Existing orders, invoices, data exports, and device return matters must still be handled according to the order records and these terms.
Service description
MiniRent provides Cloud Mac rentals by the day, week, month, or quarter. Each active order corresponds to one dedicated physical Mac mini. Its compute resources and local storage are not shared with other tenants, and the service is not a virtual machine product.
Only two models are currently available: MiniRent M4 Core with M4, 16GB RAM, and a 256GB SSD; and MiniRent M4 Plus with M4, 24GB RAM, and a 512GB SSD. Available add-ons include +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy chaining. Availability for a specific order is determined by the configuration page.
There are 5 fixed service locations: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Western United States. Both models are available at all listed locations. Actual availability and delivery progress are determined by the real-time information returned by the console.
| Item | Coverage | Where to confirm |
|---|---|---|
| Device attributes | Dedicated physical Mac mini, not a virtual machine | Order details and device information |
| Rental period | Day, week, month, quarter | Configuration page and order records |
| Available models | MiniRent M4 Core, MiniRent M4 Plus | Plan page and configuration page |
| Service locations | Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, Western United States | Location selection and order details |
Orders and delivery
When placing an order, you must review the model, rental period, location, quantity, and add-ons one by one. The configuration summary shown before submission is for review; after the order is placed, the effective details are the order, payment, and device records generated in the console.
Delivery may include payment confirmation, device assignment, system initialization, connection-detail generation, and status updates. Timing depends on real-time availability and order-processing progress returned by the console. General website descriptions do not replace the order status.
After receiving the device information, promptly verify the model, memory, storage, location, and rental period. If the records do not match the confirmed order, pause sensitive workloads and submit a support ticket through the console with the order number, device identifier, and a description of the discrepancy.
You may not resell device access, split connection credentials for use by unrelated parties, or place orders in a way that conceals the actual user. Internal team authorization should be based on business need and supported by a revocable access-management process.
Pricing and billing
All plans, add-ons, invoices, and refund records are priced in US dollars (USD). Rental periods are priced separately. Select a plan using the period price shown on the configuration page; do not request an unlisted billing method based on your own currency conversion.
Payment methods are limited to USDT-TRC20 and Visa, Mastercard, or Amex via Stripe. Available gateways are determined by the backend response at checkout. Verify the payment network, currency, order amount, and payment status. If you select the wrong network or enter incorrect information, report the issue immediately through a console support ticket.
After an order enters payment confirmation, you can view its billing status in the console. Payment receipts, on-chain transaction IDs, or card payment records must be associated with the relevant order. Do not send complete sensitive information through public channels.
Users are responsible for handling taxes, filings, and internal purchasing approvals according to their own circumstances. If legally required platform-issued billing or transaction-linkage information is needed, submit a request by email to support and include a verifiable order number.
Renewals, changes, and cancellation
The rental period is determined by the start time, end time, and selected period in the order record. If you need continued access, enter the console before the current period ends to confirm the renewal arrangement, fees, and device status. Renewal is not considered completed until confirmation is finished.
Changes to the model, location, storage add-on, daisy-chaining option, or rental period require reconfirmation based on the current order status. Before migrating a device, complete data backups, export the dependency list, revoke credentials, and review the environment. A configuration change is not a promise of uninterrupted data migration.
To cancel early, submit a request through the console and track progress through the support ticket and order status. Periods already started, device configuration already completed, and add-on capabilities already provided will be handled under the order rules confirmed at checkout.
Before the service ends, export your code, build artifacts, logs, certificates, keys, and other necessary data. Content that cannot be retrieved after access is revoked because it was not backed up in time will be handled through the device return process; a cancellation request does not replace the need to back up data.
Acceptable use
Devices may be used for lawful software development, Xcode builds, continuous integration, remote development, automated testing, and AI inference experiments. Control concurrency, storage usage, network connections, and external service calls so that workloads match the ordered configuration.
The following activities are not allowed:
- Scanning, attempting to access, or controlling accounts, devices, networks, repositories, or services without authorization.
- Creating, deploying, or distributing malicious code, or conducting credential theft, extortion, disruption, deception, or security-control evasion.
- Interfering with the normal operation of infrastructure, other orders, or external systems through abnormal traffic, automated requests, or resource contention.
- Uploading, copying, distributing, or processing software, data, media, models, certificates, or other protected content without lawful authorization.
- Using the device to commit fraud, impersonate others, conceal the source of activity, or violate applicable law.
- Bypassing console order limits, access controls, billing processes, or device return procedures.
If potentially harmful activity affecting the infrastructure or a third party is detected, the platform may first impose necessary access restrictions and isolation measures, then investigate using logs, order records, and the user’s explanation. You must cooperate by providing the relevant time range, task type, and redacted diagnostic information.
Account and device security
Protect your console login credentials, device connection details, SSH private keys, code-signing materials, short-lived tokens, and third-party service tokens. Manage credentials separately by person and purpose. Do not distribute them through public repositories, group messages, build logs, or unencrypted files.
Team administrators must establish processes for least privilege, access revocation when members leave, credential rotation, and review of unusual logins. Limit remote access sources to the networks actually required, and promptly close unused services and ports.
Automation pipelines should use short-lived tokens or restricted credentials whenever possible. Store sensitive values in a controlled secret-injection process, and ensure that command output, build caches, and artifact logs do not expose complete secrets. Revoke old credentials when changing runners, repositories, or collaborators.
If you suspect credential exposure, unusual device access, or tampering with order information, immediately rotate the relevant credentials, preserve the timeline and redacted logs, and submit a high-priority ticket through the console. Security reports may also be sent to support@macminirent.com.
Data, backups, and device return
You are responsible for the legality, accuracy, permissions, and backups of your work data, including source code, dependencies, model files, training or inference data, build artifacts, certificates, keys, logs, and temporary caches. A dedicated device does not constitute an automatic backup service.
Save important content to backup locations under your control and regularly verify that backups are readable, contain the required versions, and include the keys needed for recovery. Copying files without verifying the recovery process does not constitute a usable backup.
After the rental period ends, cancellation is completed, or the device enters the return process, existing access will be revoked. The device will then undergo access-credential invalidation, user-data cleanup, and reconfiguration to prevent a subsequent user from accessing data from the previous order.
Before returning the device, complete the following:
- Export code, build artifacts, logs, and configuration inventories that must be retained long term.
- Revoke tokens and keys used by the device from repositories, CI platforms, and third-party tools.
- Confirm that remote sessions are closed and stop any automated tasks, runners, and upload processes that are still running.
- Record any remaining order matters and provide the corresponding device identifier in a console support ticket.
Availability, responsibilities, updates, and contact
Service locations operate continuously 365 days a year. Actual connection quality may still be affected by the user’s local network, cross-region routes, carrier routing, code repositories, artifact storage, and the status of other external services. When connection or performance issues occur, both parties should identify the cause using the time range, path tests, device logs, and task records.
Within the order scope, the platform is responsible for providing device access, operating the infrastructure, maintaining order records, and handling the device return process. Users are responsible for workload configuration, the legality of code and data, credential management, necessary backups, and any third-party tools they choose to use. Responsibility will be assessed based on verifiable records, direct causation, and the extent permitted by applicable law.
Impacts caused by force majeure, public network failures, the user’s own actions, failures of external services controlled by the user, or violations of these terms will be assessed based on the event records to allocate responsibility. Any remedy, fee adjustment, or other outcome must be documented in a traceable support ticket or order record.
These terms may be updated as service capabilities, transaction processes, or legal requirements change. Material changes will be announced through the website, console, or contact information associated with the account. Updated terms apply to subsequent access, orders, or continued use from the stated effective date.
These terms are governed by the laws of the jurisdiction where the platform’s operating entity is located. The parties should first attempt to resolve disputes through the support email or a console support ticket. If no resolution is reached, the dispute may be submitted to a court with jurisdiction in that jurisdiction.
For terms, billing, order, data-processing, or security matters, email support@macminirent.com, or sign in to the console to submit a support ticket. To help us investigate, include the order number, device identifier, time of the issue, expected outcome, and relevant redacted records.