Cloud Mac Rental Terms of Service

Service definition

MacRents provides Cloud Mac services rented by the day, week, month, or quarter. Each active rental corresponds to one dedicated physical Mac mini, giving the user exclusive access to that device’s compute, memory, and local storage resources throughout the rental term. The device is not a virtual machine sharing compute resources with other renters.

The service includes the Mac mini model listed in the order, network access from the selected node, delivery of connection details, order and instance management in the console, and support directly related to use of the service. The confirmed order determines the exact chip, memory, storage, rental term, node, and add-ons.

Service boundaries

• Users may operate the rented device through the macOS graphical interface or command line and install the software required for their workloads.
• Users are responsible for configuring and lawfully using project code, build tools, dependencies, automated tasks, and access policies.
• Network performance depends on the user’s location, carrier routing, destination service, and selected node; different connection paths may perform differently.
• Software licenses, third-party subscriptions, and external service charges not expressly listed in the order are not included in the device rental fee.

Accounts and eligibility

Registration, contact, and order information submitted by users must be truthful, accurate, and kept current. Anyone ordering for a team or organization must have authority to make that decision and manage authorized users.

Users must securely protect account credentials, login verification codes, host keys, access tokens, and remote connection details. Credentials must not be shared publicly or given to unauthorized people. Orders, configurations, and instance actions performed by an authorized user in the account are treated as valid actions of that account.

What to do if you detect unusual activity

1. Immediately stop using any credentials that may have been exposed, and rotate the relevant keys or tokens.
2. Sign in to the console and review orders, instances, bills, and recent support records.
3. Submit a ticket through the console with the order number, node, time range, and redacted logs.
4. If you cannot sign in temporarily, use support@macrents.com to contact support.

To protect accounts, devices, or other users, MacRents may apply temporary access safeguards when it detects clearly unusual logins, credential abuse, or high-risk actions, and may require the account holder to complete necessary verification.

Orders and delivery

Before placing an order, users should verify the model, chip, memory, base storage, node, rental period, and add-ons. Once an order is placed, the order confirmation page and console records govern the service details. Four nodes are currently available: Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Real-time availability for each combination is shown in the console.

Order delivery typically includes an instance record, host connection details, and required initial credentials. After receiving the connection details, users should complete the first connection, key setup, credential rotation, and source-address restrictions promptly. Delaying security configuration does not change how the confirmed rental term begins.

Order management rules

• Order status, instance details, subscription records, and bills are managed in the console.
• For technical issues involving a specific order, use a console ticket linked to that order rather than sending a description that cannot identify the instance.
• When users request configuration changes, the available options, charges, and effective method are determined by the operation page.
• To change the node, model, or rental period after confirmation, submit a ticket first to verify what can be done; do not assume the original order can be converted unconditionally.

Pricing and payments

All plans, add-ons, orders, and bills are priced and settled in US dollars (USD). Available payment methods are USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. The checkout page shows the gateways and payment steps currently available.

Before submitting payment, users should verify the currency, order total, rental period, node, base model, and add-ons. Payment methods may require different confirmation steps. Payment completion is determined by the order page record, not by a payment screenshot or activity record generated only on the user’s side.

Bill review

Base model charge

The Mac mini configuration and rental period selected for the order.

Storage add-on charge

Applied only when additional SSD capacity is selected, and shown for the chosen period.

Thunderbolt 5 multi-device charge

Applied per device only when multi-device linking is selected.

Order total

The USD total of the base model and selected add-ons; the final amount is shown on the checkout page before submission.

To verify payment records, users should provide the order number, payment method, transaction time range, and amount shown on the order. Never send complete card details, keys, verification codes, or other sensitive information that could directly provide access to funds or accounts.

Renewals, cancellations, and refunds

Before ordering, users should confirm that the rental period, configuration, node, and add-ons fit their current workload. The applicable rules shown on the order page before submission directly determine whether the order can be canceled, how it can be renewed, and whether a refund may be available.

Renewal does not automatically ensure that the existing workload, software environment, or data will continue to meet later requirements. Before renewal, users should check the remaining term, project plan, storage usage, build queue, and team access arrangements, and keep an independent backup of important data.

Information required for a request

• The order number and specific instance requiring attention.
• The request type, such as renewal review, cancellation request, or payment-record review.
• The relevant rental period, node, and add-ons.
• Only the minimum information needed to explain the request; do not include project secrets or complete credentials.

Refund requests are reviewed against the order status, resources delivered, period used, and applicable rules shown at checkout. Payment confirmation times may depend on the selected payment method, and the result will be provided through a console ticket or support email.

Acceptable use

Users may use the service only for lawful and authorized development, testing, building, automation, remote collaboration, and experimentation. Users must ensure that their code, data, software licenses, network access, and automated operations comply with applicable rules and are responsible for tasks run under their accounts.

Prohibited activities

• Attempting to access accounts, devices, networks, systems, or data without authorization.
• Distributing malicious code or deploying software intended to steal credentials, damage data, or evade access controls.
• Launching or assisting with network attacks, scanning, denial-of-service activity, brute-force attempts, deception, or traffic amplification.
• Abusing network or compute resources through unusually sustained loads, uncontrolled automated tasks, or other means that affect the platform or other connected parties.
• Infringing another person’s copyright, trade secrets, privacy, or other lawful rights.
• Falsifying identity, order, payment, technical-log, or material support-request information.
• Circumventing platform account safeguards, access controls, resource boundaries, or risk-response measures.

When conduct creates a clear risk to devices, networks, platform security, or third-party rights, MacRents may restrict the relevant connection, isolate an affected instance, or suspend high-risk actions, and will notify the user of verification requirements through the account contact details. Serious or repeated violations may result in termination of the service.

Data and offboarding

Users are responsible for managing project files, source code, build artifacts, model files, configurations, certificates, keys, and logs on the rented device. MacRents provides the device and connectivity, but users should maintain independent, recoverable, and tested backups appropriate to the importance of each project.

Data responsibilities during the rental term

• Store only necessary data on the device and appropriately encrypt sensitive files.
• Use key-based connections where possible, and restrict authorized people and source addresses.
• Regularly check storage capacity, backup integrity, and recovery steps—not merely whether a backup task has run.
• Promptly revoke access and rotate keys when leaving a project, after team changes, or when credentials may have been exposed.

Pre-offboarding checklist

1. Export source code, build artifacts, logs, and configurations that need to be retained.
2. Verify that backups can be read from an independent location and sample-test recovery of critical projects.
3. Revoke external-service tokens, deployment keys, and automated Runner registrations.
4. Delete sensitive files, temporary credentials, and no-longer-needed project data from the device.
5. Confirm that pipelines, scheduled tasks, and persistent agents no longer dispatch jobs to the device.

After the rental term ends, continued access to the original device may not be available. The storage media will be cleared and necessary checks performed before the device is reassigned. Users must not treat post-term device access as a backup or migration strategy.

Service availability and changes

All nodes target normal operation 365 days a year. Hardware failures, network incidents, security risks, upstream connection problems, natural events, and other factors beyond reasonable control may still affect an individual device or connection path.

When an incident affects the service, MacRents will assess the situation and, as appropriate, isolate the issue, inspect hardware, verify network paths, validate recovery, and notify users. To speed diagnosis, users should include the order number, node, incident start time, duration, affected protocol, and redacted test results in their ticket.

Service change principles

• Material changes involving core order configuration, billing, or user workflows will be explained through the website, console, or account contact details.
• To address urgent security risks, clear abuse, or an expanding outage, the platform may first apply necessary isolation and protective measures and then complete the incident record.
• Issues caused by a user’s software upgrades, network rules, key changes, automation scripts, or incorrect configuration should first be addressed by reverting the change and providing reproducible details.
• The status of third-party networks, payment processing, and external development services may affect the relevant steps, but does not change the recorded MacRents service scope in a confirmed order.

Liability and disputes

Each party is responsible for the accounts, configurations, actions, data, and authorization decisions within its control. User configuration errors, untested automation scripts, delayed backups, exposed credentials, unauthorized team actions, and issues with third-party services must not be treated as instructions from MacRents regarding those actions or results.

To the extent permitted by applicable law, responsibility for lost profits, lost business opportunities, indirect or consequential losses, and data loss made worse by the user’s failure to maintain recoverable backups will be determined based on the cause of the incident, each party’s ability to control it, actual records, and reasonably foreseeable impact. No allocation of responsibility excludes liability that applicable law does not permit to be limited.

Issue-resolution sequence

1. The user should first submit a console ticket with the order number, facts, time range, desired resolution, and necessary evidence.
2. The parties will review order records, activity logs, payment records, and technical information and seek to resolve the disagreement through direct communication where possible.
3. If further action is needed, the parties may pursue dispute resolution under the laws of the jurisdiction where the platform operator is based.
4. Disputes that cannot be resolved through discussion may be submitted to a court with jurisdiction in that jurisdiction.

If any part of these terms is found unenforceable, the remaining provisions will continue to apply. MacRents’s failure to immediately enforce a right does not constitute a permanent waiver of that right. Any supplementary agreement relating to a specific order must be supported by verifiable written records from both parties.