Cloud Mac Rental & Usage Terms

Service and eligibility

MiniRent provides remote network access to Cloud Macs. Each device is a dedicated physical Mac assigned to a single customer or its authorized team. It does not share an operating system instance with other customers and is not a virtual machine. The service may be used for Xcode builds, fastlane automation, self-hosted Mac Runners, controlled development environments, and Apple Silicon computing tasks.

Customer and console account

The “customer” is the individual or organization that creates the order and assumes payment and compliance responsibility. The console account is used to view orders, device status, connection details, billing, and support tickets. The customer must have the legal capacity to enter into these Terms. Anyone ordering on behalf of an organization must also have valid authorization from that organization.

• Account details must be true and accurate and updated promptly when a contact or team lead changes.
• The customer is responsible for confirming that team members are authorized to access the device, repositories, build materials, and order information.
• Console credentials must not be shared with unrelated people or used to create or transfer accounts in a way that bypasses access controls.
• Individuals who have not reached the age of independent contracting in their jurisdiction must place orders through a qualified guardian or organization.

The service does not include authorization for software, code repositories, dependencies, signing materials, or third-party pipeline systems deployed by the customer. The customer must independently confirm that its development tools, code, data, and automation workflows have a lawful basis for use.

Orders and delivery

Each order is governed by the model, location, rental term, and add-ons confirmed by the customer. Currently offered models are the base tier (M4, 16GB, 256GB) and the Pro tier (M4 Pro, 64GB, 2TB). Available locations are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States. Both models can be ordered in all five locations.

Available terms are daily, weekly, monthly, and quarterly. Add-ons include +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy chaining. Check the configuration before payment; entering the confirmation step indicates acceptance of the items and charges shown on the order page.

Delivery records

The console record controls the device delivery status, connection-information generation status, rental start and end dates, and subsequent configuration changes. Standard catalog combinations are generally available, while the console provides the real-time result for each order. After an order is completed, the customer should promptly verify:

• Whether the model, memory, and base storage match the order;
• Whether the location is the selected Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or Eastern United States;
• Whether the rental dates and additional storage are correct;
• Whether the connection endpoint, host fingerprint, and device identifier match the console record.

If the configuration or delivery record is inconsistent, the customer must stop writing sensitive materials to the device and submit the order ID, device ID, and a description of the discrepancy through a console ticket. MiniRent will verify the device configuration against the order record and provide the outcome.

Pricing and payment

All charges are stated and settled in US dollars (USD). MiniRent supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateways actually available are determined by the options returned in real time by the backend during checkout.

Charges

The order total consists of the base model, rental term, storage add-ons, and Thunderbolt 5 daisy-chaining option. The breakdown shown before checkout is the billing basis for that order. The customer must verify the blockchain network, card details, payment amount, and order ID, and must not send digital assets from another network to the designated receiving address.

• USDT-TRC20 payments are recognized based on a valid transaction on the designated network and confirmation by the order system.
• Visa / Mastercard / Amex payments are processed by Stripe. MiniRent receives only the payment result needed to complete the order and provide the service.
• Customer-side fees charged by card issuers, payment networks, or on-chain transfers are not automatically included in the MiniRent order total.
• For duplicate payments, incorrect amounts, or failed order matching, submit the order ID and redacted transaction details through a console ticket.

Customers must not make fraudulent payments, forge payment receipts, or dishonestly dispute a service that was delivered as agreed. If payment is reversed, declined, or cannot be verified, MiniRent may pause fulfillment of the relevant order and give the customer an opportunity to verify the payment.

Renewals, changes, and cancellation

The rental term is determined by the order confirmation record. Before the term ends, the customer should review the renewal option, term, and price in the console. A renewal takes effect only after explicit confirmation in the console creates a valid record; without confirmation, the customer is not considered to have accepted a new rental term.

Configuration and location changes

Changing the model, storage, daisy-chaining setup, or location may require data migration, build-environment adjustments, or new connection information. Before submitting a change, the customer must create a verifiable backup and provide the desired configuration, target location, workable time range, and business-impact details.

• Model changes are limited to the MiniRents M4 and MiniRents M4 Pro catalog options.
• Location migrations may be requested between Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States.
• A migration request does not mean that data will be synchronized automatically; the specific steps and outcome depend on the console ticket confirmation.
• After a change is completed, the customer must recheck the host fingerprint, access permissions, dependency versions, and pipeline targets.

Cancellation

Customers can manage renewal selections for terms that have not yet entered the next period in the console. Cancellation does not retroactively revoke a rental term that has already started and been delivered as agreed. Where a refund is legally required, a duplicate payment occurs, or a confirmed service interruption qualifies for service compensation, MiniRent will handle the matter based on payment records, service records, and these Terms.

Permitted and prohibited use

Customers may run development, build, testing, automation, and computing tasks within the scope of lawful authorization. All tasks must respect device resource limits, network operations at the location, third-party rights, and applicable security requirements.

Prohibited activities

• Scanning, probing, accessing, or attempting to control unauthorized accounts, devices, networks, repositories, or services;
• Creating, distributing, or running malicious code intended to damage, steal, extort, conceal control, or evade security detection;
• Misusing SSH keys, access tokens, signing materials, payment credentials, or other authentication information;
• Infringing copyrights, trade secrets, privacy rights, data rights, or other legitimate third-party rights;
• Disrupting the stable operation of location networks, the control plane, other devices, or support systems;
• Falsifying origins, concealing attacks, bypassing resource limits, or helping others engage in any conduct listed in this section;
• Using the service for fraud, unsolicited bulk communications, or other unlawful activity.

If the customer discovers compromised credentials, an uncontrolled automation task, or possible unauthorized access to a device, they must immediately revoke the relevant permissions, stop affected tasks, preserve redacted logs, and report the device ID and incident time range through a console ticket.

Availability and support

MiniRent’s service target is 99.9%. All locations are designed to run continuously 365 days a year. Availability statistics are based on verifiable device-connection and service records and exclude impacts caused by force majeure, customer actions, customer-deployed software, third-party development tools, the customer’s network, or unapproved configuration changes.

Incident verification and service compensation

If the customer believes a service interruption has occurred, they must submit the device ID, location, start and end time range, connection method, error messages, and redacted logs through a console ticket. MiniRent will determine the incident scope using control-plane records, device records, and the information provided by the customer. Eligible service compensation applies only to confirmed service interruptions and is calculated under the service terms in effect at the time and the corresponding order record.

Support is available only through console tickets and support@minirents.com. To speed up diagnosis, technical issues should be submitted through a console ticket first with reproducible steps. Email is intended for account-access assistance when the console cannot be accessed, pre-sales confirmation, security reports, or requests for compliance materials.

Data and account responsibility

The customer is responsible for the code, build artifacts, signing materials, repository tokens, environment variables, dependency caches, logs, and backups they upload, generate, process, or download. MiniRent provides the device and connectivity but does not replace the customer’s version control, key management, member-access approval, or business backup processes.

Minimum security requirements

• Use a dedicated SSH public key and verify the host fingerprint on the first connection;
• Apply least-privilege access and reasonable expiration periods to repository tokens and automation variables;
• Do not place unredacted passwords, private keys, or long-lived tokens in scripts, build logs, or ticket text;
• Promptly revoke access when a member leaves, responsibilities change, or the device’s purpose changes;
• Maintain recoverable backups of code, configuration, artifacts, and necessary logs independently of the rented device;
• Before the rental ends, migration occurs, or the device is returned, delete temporary credentials, sensitive materials, and unnecessary caches.

The customer should retain backups that demonstrate successful data recovery, not merely a message confirming that a copy task succeeded. For workflows dependent on third-party repositories, certificate services, or pipeline systems, the customer should also prepare recovery plans for access loss, version changes, and upstream outages.

If MiniRent’s help is needed for troubleshooting, the customer must first redact access tokens, keys, personal information, repository URLs, and business data from logs. MiniRent will not ask customers to submit passwords or private keys by email or ticket.

Suspension, termination, and liability limits

If the service presents a clear security risk, prohibited use is suspected, payment cannot be verified, third-party rights face an urgent threat, or the customer’s tasks are disrupting normal operations at a location, MiniRent may take measures proportionate to the risk. Where practicable, MiniRent will explain the reason through the console record or account contact information and give the customer an opportunity to provide additional materials or correct the issue.

Suspension and termination

Measures may include suspending specific tasks, restricting connections, isolating an affected device, or pausing an order. After addressing the risk, verifying payment, or correcting the violation, the customer may request a review by submitting a ticket. For serious unlawful conduct, malicious attacks, continued disruption, forged payments, or repeated violations after notice, MiniRent may terminate the relevant orders and account access.

Before service termination or rental expiry, the customer must export necessary data, revoke team permissions, and remove sensitive materials. If access must be restricted immediately because of a security incident, data-export capabilities may be affected by the response measures.

Scope of liability

To the extent permitted by applicable law, each party is responsible for direct losses caused by its own breach, unlawful conduct, or failure to meet reasonable security obligations. Results caused by defects in customer code, customer error, changes to third-party tools, customer network failures, missing effective backups, or unauthorized configurations are the responsibility of the party able to control the relevant risk.

No liability limitation excludes or restricts liability that cannot legally be limited or excluded. When making a service-related request, the customer must provide order records, the incident time range, an impact description, and verifiable materials so both parties can confirm the cause, impact, and applicable handling.

Events beyond control

If performance is delayed by natural disasters, public-infrastructure failures, government action, severe cyberattacks, or other events beyond reasonable control, the affected party must mitigate the impact and resume performance where practicable. Such events do not excuse payment obligations that are already due or affect rights that cannot legally be excluded.

Updates to these Terms

MiniRent may update these Terms when service features, billing processes, security requirements, or legal obligations change. The updated version will show a new effective date. Changes that materially affect customer rights or obligations will be announced through visible console information or account contact details. Continuing to order a new term after the change takes effect constitutes acceptance of the updated Terms.

Governing law and dispute resolution

These Terms are governed by the laws of the jurisdiction where the platform operator is based, without affecting mandatory rights that the customer has by law and cannot waive by contract. In a dispute, the parties should first negotiate in good faith using order, payment, device, and support records. If negotiation fails, either party may bring proceedings before a court with jurisdiction in that jurisdiction.