1. Service overview
RemoteMini Cloud Mac provides remote access to a dedicated physical Mac mini. For the rental period, the entire machine is assigned to one customer—not a virtual machine—and its CPU, unified memory, and base SSD are not shared with other customers. The only plan currently available is Remote M4: Mac mini M4 · 16GB unified memory · 256GB SSD. You receive remote use of the machine for the agreed rental period, not ownership of the hardware.
We offer nodes in Singapore, Tokyo, Seoul, and Hong Kong. Select a location when ordering; availability is shown in real time in the console. Data is not migrated between regions after a node is provisioned. To switch regions, back up your data first, then provision a node in the new location. Your existing environment will not move automatically.
The macOS graphical interface and command line can be used for development, builds, testing, and other lawful tasks. Remote desktop performance also depends on your network, client, and distance from the selected node. A remote setup may not suit work that requires offline access, real-time audio monitoring, or direct connections to professional peripherals. You’re responsible for checking the licences, subscriptions, and terms for any third-party software you use; renting hardware does not grant software licences.
2. Accounts and acceptable use
Provide a valid email address where you can receive service notices. Keep your console account, node credentials, and access keys secure, and change the initial password as soon as you receive your connection details. If your team shares an order, you’re responsible for managing member access and sharing credentials securely. Dedicated hardware doesn’t remove your responsibility to protect your account.
You must not use a node for unauthorised access, distributing malware, fraud, spam, intellectual property or privacy violations, unlawful access to or distribution of data, or any other activity that violates applicable law. Network scanning, security testing, and data processing require appropriate authorisation and must not disrupt other systems or services.
You’re responsible for having the necessary rights to process any code, assets, models, files, or tasks you upload, and for setting up backups, access controls, and software updates. If credentials are exposed, you notice an unusual login, or you suspect misuse, rotate the affected credentials immediately and contact us through a console ticket. Don’t send passwords, private keys, or full payment card details through public pages or regular email.
We may restrict access when there is a reasonable security risk or suspected unlawful use, and explain the reason where permitted by law. Restrictions will be proportionate to the risk. To ask about an investigation or restore access, submit a ticket from the original account with your order details and relevant information.
3. Billing and payments
The base plan is available by the day, week, month, or quarter, at the listed prices of $19.8/day, $53.4/week, $98.9/month, and $269/quarter. Shorter terms work well for quick trials, but cost more per day. For longer-running workloads, compare the monthly and quarterly options. The term you select, add-ons, amount due, and rental start and end dates are those shown in the order confirmation and corresponding invoice before you submit your order.
The +1TB SSD, +2TB SSD, and Thunderbolt 5 daisy-chain options are billed separately based on your selected configuration and are not included in the base plan price. Before paying, check each item, quantity, term, and node location. To change an active configuration, submit a ticket first to confirm what’s possible, the cost, and when the change will take effect. A new configuration price does not automatically replace the price on your existing order.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All charges are in US dollars (USD); available payment options are confirmed by the payment gateway. For USDT-TRC20, check the network, receiving address, and amount required for your order. Card transactions are subject to approval by your card issuer and payment processor. A payment you’ve initiated does not mean service is active until it has been confirmed.
If you’re charged twice, your order status hasn’t updated after payment, or you have a question about an amount, keep your invoice number and payment receipt or transaction hash, then submit a ticket through the console so we can check. For full term pricing and add-ons, visit the Plans. Your payment is based on the order you confirm, not on usage suggestions elsewhere on the site.
4. Renewals, expiry, and data release
Use the rental end time shown in the console as the source of truth, and complete renewal and payment confirmation before then. Check the console for any outstanding renewal invoice, the end time after renewal, and your order status. Paying by card before does not mean future terms will renew automatically or that a later charge will succeed.
Before expiry, export your code, build artifacts, assets, model weights, and any configuration you need, and make sure your backups can be restored. Service notices don’t replace checking your expiry date. Email filters, inbox settings, or failed payments can affect notices and renewal confirmation. If you need more time, arrange it before your current term ends—not after you lose access.
If your rental period ends without a confirmed renewal, node access may be stopped and data on the node will enter the release and deletion process. We don’t promise an additional retention period after expiry or recovery of data once deleted. Don’t assume that paying after expiry means your files will still be there. To check the status of a specific order, contact us through a console ticket.
Before switching nodes, rebuilding your environment, or ending your rental, migrate your data yourself. Node files are handled differently from account and billing records. For information about how the latter are retained and your related rights, see our Privacy Policy. Deleting files from a node does not also delete transaction records that must be retained by law.
5. Uptime commitment and service credits
Nodes run 365 days a year, and we commit to service availability of 99.9%. For context, 0.1% of a 30-day month is about 43 minutes. This calculation helps explain the commitment; it is not a scheduled downtime period or a live monitoring report for any particular node.
If monthly availability falls below 99.9%, we’ll calculate service credits based on the verified time below the commitment. Credits apply to service time for the affected instance; they are not cash compensation calculated from project revenue, build counts, or business losses. We’ll confirm the scope, start and end times, and credit amount after reviewing your ticket.
To request a review, sign in to the console and submit a ticket with the instance ID, affected start and end times and time zone, connection or task errors, and troubleshooting steps you’ve already tried. Keep relevant logs, but don’t send passwords, private keys, or unrelated personal information. We’ll check the incident against information from the node.
Issues with your local network or client, connection problems caused by changes you make to system or access settings, and impacts caused by events beyond reasonable control are assessed according to their actual cause and are not automatically counted as platform downtime. A laggy remote display alone doesn’t show that a node was unavailable. First follow the connection troubleshooting steps on the Support page, then send us details that let us reproduce the issue.
6. Refunds
To cancel an order or request a refund, submit a console ticket with your order number, proof of payment, and reason for the request. We’ll assess unprovisioned orders, duplicate payments, billing errors, and services already used separately. Submitting a request does not mean a refund has been approved or that your rental period is paused.
For an active service, we’ll review the provisioning status, actual usage, reason for the request, and applicable law. Not using the remote desktop, ending a project early, or changing how you use the service does not automatically entitle you to a refund for the unused days. For service availability disputes, first verify the impact and any applicable credit under Section 5, then we’ll determine whether any other remedy applies.
For an approved refund, we’ll explain the amount, return method, and information required in your ticket. The time it takes to arrive also depends on the payment provider. For USDT-TRC20 refunds, check the receiving address and network. For card refunds, never share your full card number in email or a support ticket. Any mandatory refund or consumer rights under applicable law remain unaffected by these terms.
7. Limitation of liability
We’re responsible for providing the dedicated physical node, remote access, and support included in your order. You’re responsible for your local devices and network, tasks and configuration on the node, third-party software licences, and backups of your business data. Dedicated resources mean you don’t share hardware with other customers, but they don’t guarantee how long a program will take, the scale of a model run, software compatibility, or a particular business outcome.
We’ll respond to service issues based on verifiable causes and impacts. Service credits for availability below our commitment are handled under Section 5. Where a third-party system, your own actions, or events beyond reasonable control are involved, responsibility will be assessed accordingly. Any limits on liability apply only to the extent permitted by applicable law and do not exclude liability that cannot legally be limited or excluded.
Don’t use a node as your only copy of important data. Set up independent backups and validate your results before long-running tasks, major releases, or large-scale asset processing. If you find a data issue, preserve the current state and relevant logs, then submit a ticket with the time and steps involved. Avoid repeatedly reinstalling or overwriting files, as this can make the issue harder to investigate.
8. Changes and governing law
These terms take effect on the date this version is published. If we make a material change to our service scope, billing, or data handling, we’ll update the public terms and notify you appropriately through the site or your account. An update to listed prices does not automatically change a confirmed order. Changes affecting an active rental period will be handled under the order terms and applicable law.
These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises from the service or these terms, both parties should first try to resolve it by ticket or email. If they can’t reach an agreement, either party may refer the dispute to a court with jurisdiction in that same jurisdiction. Any rights granted to users by applicable law that cannot be excluded remain in effect.
If you have a question about these terms, your order, or the scope of the service, customers with an order should first sign in to the console and submit a ticket so we can link it to your instance and invoice. If you can’t sign in or need to contact us in writing, email support@remotemini.com. Describe your question and include any relevant order details. We’ll reply through the appropriate channel.