1. Service overview
ArmRDP Cloud Mac provides dedicated physical Mac mini rentals. Each rental node is one physical machine reserved exclusively for you during your rental period. Devices are not shared between tenants, oversold or virtualised. You can use the macOS graphical interface and command line for tasks such as Xcode builds, simulator testing, codesign, automated builds and self-hosted runners.
Your order specifies the model, location, rental period and add-ons. Available configurations and setup status are shown in real time in the console. Check the final configuration before placing your order. Illustrative process diagrams and sample build records do not guarantee actual performance, delivery time or build results.
Nodes operate year-round, 365 days a year. You are responsible for project dependencies, toolchain compatibility, signing asset validity and pipeline configuration. Build times vary with codebase size, concurrent tasks and dependency status. Renting a physical node does not guarantee that a project will build successfully or pass release review.
2. Account & setup
Create an account with an email address that can receive messages, and provide accurate order and contact details. We use your account to verify payments and delivery, send service notices and handle support tickets. Keep your email access, login verification codes, host passwords and SSH private keys secure. Do not share these credentials with unauthorised people.
After payment, check your order status and host delivery details in the console. Payment confirmation, order activation and host connectivity are separate statuses, so verify each one. If payment is complete but the order status has not updated, keep the payment record and open a console support ticket. Do not pay again.
After your first login, change the initial password, add your SSH public key and review access permissions. For team use, assign responsibility for credentials and establish a process for revoking access when someone leaves. If you notice an unauthorised login, leaked credentials or an unusual order, rotate the affected credentials immediately and notify us. Never include private keys, full payment card details or active passwords in a support ticket.
3. Billing & payments
Rentals are prepaid by the day, week, month or quarter, and all charges are in US dollars (USD). Before confirming payment, check the billing period, model charge and add-on charges for each order. Listed prices for different billing periods are separate rates; do not calculate another period's price by multiplying the daily rate.
For example, the weekly rate for an ArmRDP M4 Plus is $111.9, and adding +1TB SSD costs $8 per week, making the example order total $119.9 USD. Check add-ons against the billing period for the relevant order. To add or change a configuration mid-term, first review the available options and quoted price in the console, then confirm payment.
We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are confirmed by the backend at checkout. For USDT-TRC20, carefully verify the network, amount and recipient details shown on the payment page. For card payments, check the USD amount due and payment result. A payment screenshot does not confirm payment status.
By placing an order, you confirm the selected configuration and charges. If you have a question about a duplicate charge, incorrect amount or order ownership, provide the order number and payment record so we can investigate. Service charges, add-ons and refunds are handled separately; verbal estimates do not replace the order details.
4. Renewals, expiry & data erasure
To keep using a node, check its expiry date in the console and renew before the rental period ends. Do not rely solely on reminder emails, as filtering or delivery delays may prevent you from receiving them. Check the console record and payment authorisation to confirm whether a renewal is active; a previous payment alone does not mean your rental period has been extended.
When your rental period ends, access may stop and the node may enter the recovery and disk-erasure process. Before expiry, export any files you need beyond your code, including build artefacts, certificate backups and configuration inventories. Verify that these files can be restored from a local or independently managed backup. Do not rely on an expired node as a way to retrieve files.
Before a recovered node is assigned to another customer, its disks are erased to remove the previous tenant's data and credentials. Files cannot be recovered after erasure. Also revoke repository tokens, runner registrations and other authorisations held by the node to prevent active credentials from remaining after your rental ends.
5. Acceptable use
Ensure that you have the necessary rights to run code, store content and access resources on the node. You must not use the service to send spam, mine cryptocurrency, conduct network attacks, scan unauthorised targets, steal credentials, distribute malware or store or distribute content that infringes others' rights. Do not bypass access controls or disrupt other users or network infrastructure.
Run only trusted tasks on automated build systems and runners. Restrict code from external contributors from accessing signing assets, deployment credentials and internal networks. Do not give untrusted tasks unrestricted access to build environments containing sensitive credentials. You are responsible for managing how team members and automated tasks use the node.
If we detect suspected misuse or activity that threatens service security, we may take necessary steps, such as restricting connections, pausing affected tasks or suspending the service. We will explain the action through your account contact details or a support ticket. To request service restoration, provide an account of the issue, steps taken and any necessary proof of authorisation. Further action will be based on verified facts and applicable law.
6. Uptime commitment
ArmRDP Cloud Mac commits to 99.9% monthly uptime. Over a 30-day period, 0.1% represents approximately 43 minutes of downtime. Uptime is calculated for failures that prevent normal node use during an active rental period and are caused by the service. It is not measured by whether an individual build succeeds or by the speed of a particular external network route.
Downtime beyond this allowance is compensated with service time, calculated in proportion to the duration of the outage. Within 7 days of the incident, sign in to the console and open a support ticket with the host ID, affected time period, time zone and verifiable connection error records. We will review the rental period, incident records and supporting information, then confirm the affected period and compensation in the ticket.
Downtime caused by force majeure or your own actions—including shutting down the node, changing network rules, misconfiguring the system, filling the disk or exposing credentials—is not eligible for this compensation. Issues with your local network, client or external dependencies should be distinguished from node failures. If you are unsure of the cause, submit records in a support ticket so we can help investigate.
7. Refunds
For duplicate payments, unexpected payment amounts, services not delivered as ordered or other refund queries, submit a request through a console support ticket. Include the order number, payment record, reason for the request and relevant dates and times. Do not provide full payment card details in a ticket. For on-chain payments, you may include the transaction ID for verification.
Each refund request is reviewed against the relevant order, delivery and usage records. Submitting a request does not mean a refund has been approved or that billing stops immediately. If you want to stop using the service or cancel an order that has not yet been delivered, state this clearly in your ticket. Describe used service, unused rental time and add-ons separately. The eligible refund scope and amount will be determined after review and in accordance with applicable law.
If a refund is approved, we will confirm the refund route, amount and status through the support ticket. The time it takes to arrive depends on payment processing. Service-time credits for uptime incidents are handled under Section 6 and are not automatically converted to cash refunds. These terms do not limit any other rights you may have under applicable law.
8. Liability & disclaimers
We are responsible for providing the physical node service specified in your order and investigating and resolving server-side faults. You are responsible for your project code, third-party tools and dependencies, signing assets, build scripts and data backups. A dedicated physical machine provides an isolated environment, but does not replace your responsibility to secure access permissions, task sources and sensitive files.
If a fault causes an issue, keep relevant error information and take reasonable steps to limit the impact, such as pausing repeated task submissions, keeping a local copy of your code and revoking exposed tokens. Until the cause is confirmed, avoid repeatedly taking actions that could overwrite data or delete signing assets. If you need help, describe what happened in a support ticket first.
Liability is assessed based on the actual breach, verifiable losses and causal connection, in accordance with applicable law. Responsibility for impacts caused by force majeure or your own actions is determined by the actual cause. No limitation of liability applies where liability cannot lawfully be excluded or limited. This section does not waive our obligations to deliver the service, address faults or provide confirmed compensation.
9. Changes & disputes
These terms take effect on the date of publication. We will announce material changes to charges, service scope or user rights on the website, through account notifications or by email, and specify when they apply. Changes to listed prices do not automatically alter charges for confirmed orders. Check the information confirmed at the time for new orders and renewals.
These terms are governed by the laws of the jurisdiction where the platform operator is based. If a dispute arises, first contact us through a console support ticket or email with your order number, a description of what happened and your requested resolution, so we can review and discuss the matter. If it cannot be resolved through discussion, the dispute will be handled by a court with jurisdiction in that jurisdiction.
For questions about these terms, orders, business partnerships or security reports, email us at support@armrdp.com. For questions about an existing order, use a console support ticket so we can link it to the relevant host and payment records. To check a configuration or charges before ordering, review the final confirmation on the order page.