1. Service scope
MacUDP provides cloud Mac rental services at one of 5 locations: Singapore, Tokyo, Seoul, Hong Kong and the US West Coast. Each service is delivered on a dedicated physical Mac mini assigned to one customer only. It is not a virtual machine, and its CPU and memory are not shared with other customers. You are purchasing use of the equipment for the agreed period, not ownership of it.
We currently offer two configurations: UDP M4 16 (M4 / 16GB / 256GB SSD) and UDP M4 24 (M4 / 24GB / 512GB SSD). Your confirmed order determines the specific model, location, billing period and add-ons. Availability is shown in real time in the console. You can use the macOS graphical interface and command line for remote work, builds and file processing. You are responsible for confirming software licences, project dependencies and the resources your tasks require.
After signing in, open the instance details to launch the browser-based remote desktop. A modern browser and reliable internet connection are required. You can also use SSH for command-line tasks. Connection performance depends on your location, network connection and selected service location. Indicative ranges are not guarantees of performance on your individual network. To move to another location, create a new instance there and migrate your data; you cannot simply switch the location of an existing instance.
2. Accounts & acceptable use
When creating an account, provide an email address that can receive messages, and keep your login details, verification codes and instance credentials secure. Account holders are responsible for managing team members’ access and for actions taken by authorised members through the account or instance. If credentials are exposed, you notice an unusual sign-in, or you discover an unauthorised task, promptly revoke the relevant access and submit a support ticket in the console.
You must not use the service for illegal activity, unauthorised access, attack scanning, malware distribution, spam, infringement of another party’s intellectual property or other legal rights, or any other unlawful conduct. Do not disrupt the platform’s or other users’ networks or services, bypass access controls, share your credentials with others, or use the service to conceal harmful activity. Before installing software, processing data or running automated tasks, make sure you have the necessary permissions and comply with applicable rules.
If we identify suspected misuse or conduct that puts service security at risk, we may ask you for an explanation, restrict relevant connections or suspend the instance. In cases of ongoing attacks, clear illegality or an urgent security risk, we may impose necessary restrictions first and notify the account holder afterward. Any action will be proportionate to the risk. You may provide an explanation and supporting evidence through a console ticket. We will review the matter against the order record, relevant logs and any additional information. Confirmed serious violations may result in termination of the service.
3. Billing & renewals
Choose from daily, weekly, monthly or quarterly billing for your Mac. All charges are in US dollars (USD). Both configurations are priced the same across all 5 locations. See rental plans for current prices. Your order will itemise the host charge, selected add-ons and total due. Before paying, check the configuration, location, billing period and amount. Examples shown on the site do not replace the details of your actual order.
Billing starts after payment succeeds. Refer to the order and instance records in the console for the exact start and end times. Billing does not pause automatically if you do not connect to the instance, finish your task early or leave it idle. SSD expansion and Thunderbolt 5 parallel connection are add-ons billed on the same cycle as the host. Check when they take effect, their renewal charges and which order they apply to when confirming your purchase.
To continue using the service, renew before expiry and check that the console shows a successful payment and the new expiry time. Do not assume a renewal is complete just because the payment page has opened or a transfer has been initiated. Before upgrading a configuration before expiry, changing add-ons mid-cycle, cancelling or requesting a refund, confirm through a support ticket whether the change is available, when it will take effect and how charges will be handled. Submitting a request does not mean the change is complete, nor does it automatically stop billing for the current period.
4. Payment
We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe only. All payments are in US dollars (USD). The payment gateways available for a given order are determined by the response from our backend. Pay only through the payment link provided with your order, and follow the amount, network and recipient details shown for that order. Do not reuse payment details from another order.
For USDT-TRC20 payments, check the network, address and amount due. For card payments, complete any verification requested by the payment gateway. If a payment is processing or its status has not yet updated, check the order record before trying again to avoid duplicate charges. Card details are handled by the payment processor; the platform does not store full card numbers.
If an order has not updated after a charge, the amount is incorrect or you have paid more than once, submit a support ticket in the console with your order number, amount, payment time and transaction hash or payment gateway transaction ID. Do not send full card numbers, verification codes, private keys or other sensitive credentials in a ticket or email. Payment status is determined by the verified transaction and order records, not by a screenshot alone.
5. Availability
Our locations operate year-round, 365 days a year, with a 99.9% service availability commitment. Over a 30-day period, this allows for approximately 43 minutes of unavailability. This figure describes how availability is measured. It is not a record of historical monitoring and does not guarantee the latency of each remote desktop session, file transfer speed or build completion time.
Availability is assessed using the verified start and end times of an instance service outage. A continuous outage is counted once; normal operation after service recovery is not included in the outage duration. Unavailability caused by your own shutdown, incorrect configuration, removal of required components, failure of your local network connection or force majeure is excluded from the time for which the platform is responsible. If there is a disagreement about the cause, submit records for review.
Outage time beyond the allowance is credited proportionally as additional service time. Sign in to the console and submit a support ticket to request a credit. Include the instance ID, location, affected time period and time zone, along with connection failure records or screenshots. After reviewing your request, we will explain the outage time counted and the credit provided in the ticket. Credits are issued as service time, not as an automatic cash refund.
6. Data
You are responsible for managing and backing up project repositories, build artefacts, configuration files and other business data stored on your instance. A dedicated physical machine does not include a separate backup service, and copies on the instance are not a substitute for backups stored elsewhere. Before upgrading the system, deleting files, changing your toolchain or moving to another location, make sure your backups can be accessed and record any necessary recovery steps.
When an instance expires or the service ends, its data enters the deletion process. Do not rely on an expired instance as a place to keep files. We do not guarantee a free retention period after expiry or recovery after deletion. Renew or export your data before expiry, and check that the files are intact at their destination. If you need help migrating, submit a support ticket while your service is still active.
Account, order, billing and support ticket records are separate categories of data from files stored on an instance. Stopping use of an instance or deleting its files does not also delete related transaction records. To request access to, correction of or deletion of account information, submit a console ticket or contact support@macudp.com. We may need to verify account ownership and relevant orders before processing a request to prevent unauthorised data actions.
7. Changes & termination
We may update the product catalogue, prices for future billing periods or service processes. If a change affects the main benefits of an existing order, we will notify you by account email or through the console and explain its scope and effective date. Confirmed order configurations and billing records will remain available for reference and will not be changed automatically when site copy is updated.
You can stop renewing or submit a support ticket to request that the service end. Include the instance ID, your preferred end date and whether you have exported your data. Ending use, deleting an instance, cancelling future renewals and requesting a refund are separate matters; confirm the outcome of each. Until your request is confirmed in a ticket, do not assume that cancellation, a refund or a data retention arrangement is in place.
We may suspend or terminate the relevant service if payment is incomplete, the service period expires or a serious violation described in these terms is confirmed. In non-urgent cases, we will explain the reason and the steps you can take. Where an immediate response is required to address a security or compliance risk, we may restrict the relevant service first. Regardless of which party initiates termination, instance data is handled under the expiry and deletion rules above.
8. Liability
We are responsible for providing the use of a dedicated physical Mac as specified in the confirmed order and for reviewing service unavailability and credit requests under these terms. You are responsible for choosing a configuration and location suited to your tasks, obtaining valid licences for the software you run, managing access and keeping recoverable data backups. The service does not replace your team’s own access approvals, version control or business continuity planning.
Build failures, dependency conflicts, third-party software behaviour and local network issues should be assessed according to their actual cause. They are not automatically failures of the device service simply because they occur on a cloud Mac. When reporting an issue, provide steps to reproduce it, the time it occurred and any relevant logs. Do not submit personal information or confidential material that is unrelated to the issue. Each party is responsible for matters within its own control.
To the extent permitted by applicable law, indirect losses, expected profits and data recovery costs arising from your failure to keep backups are not included when calculating service-time credits for availability. These terms do not exclude liability that cannot be limited under applicable law, nor do liability limits replace the need to investigate the cause of a specific failure. If you disagree with a finding or credit decision, add supporting evidence to the original ticket and request a review.
9. Updates & disputes
This page applies to the current release. When we update these terms, we will show the version information on this page. Material changes to the service scope, billing, data handling or other key benefits will be notified by account email or through the console, with details of when they take effect. Updates do not retroactively alter the factual records of completed orders or past transactions.
If you have a question about these terms or an order, sign in to the console and submit a support ticket, or contact support@macudp.com. Include your account email, order or instance ID, the matter in dispute and the outcome you are seeking. Tickets are handled in the order received. We will discuss the matter based on the records available and the information you provide; unverified verbal statements do not replace the order record.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. The parties will first try to resolve disputes through the channels above. If they are unable to reach a resolution, the dispute will be submitted to a court with jurisdiction in that jurisdiction. If any provision is found invalid or unenforceable, the remaining provisions will continue in effect to the extent permitted by applicable law.