1. Scope
This policy applies when you visit macudp.com or use the MacUDP console to order a cloud Mac, manage an instance, view bills or submit a support ticket. The website introduces our services, while the console manages accounts and services you have ordered; each involves different types of data.
This policy explains how we handle service management information and files stored on your instance. Account email addresses, orders and support tickets help us provide the service. You control projects, build artifacts and other files stored on your dedicated Mac; renting the service does not make those files platform content.
This policy is governed by the laws applicable in the jurisdiction where the platform operator is based. Any dispute relating to this policy will be handled by the courts with jurisdiction in that jurisdiction. You may first raise a question through the channels listed in section 8.
2. Information we collect and why
Account email address: Used to identify your account, send verification codes, handle sign-in and account security, and notify you about your orders or services. Use an address you can continue to access. We need to verify account ownership when handling an email change or data request.
Order and billing records: Include the selected Mac, node, billing period, add-ons, order total and payment status. We use them to provision instances, reconcile bills, process renewals and resolve transaction disputes. These records show what service you purchased; they do not describe files stored on your instance.
Support ticket content: May include your description of the issue, instance ID, when it occurred, and any screenshots or diagnostic details you choose to provide. We use this information to investigate issues and keep a record of our response. Share only what is needed, and redact passwords, private keys, certificate keys and unrelated personal information before submitting.
Access logs: May include request times, paths, network addresses, browser details and request results. We use this technical information to detect unusual access, troubleshoot connection errors and understand how the website is used. We do not use access logs as a basis for reading files on your instance.
3. Payment information
Services are billed in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. The payment options available at checkout are determined by the response from the payment interface. Stripe processes card payments; we do not store full card numbers.
For USDT-TRC20 payments, we record only the transaction hash and amount as payment details and link them to the relevant order to verify payment. On-chain transaction records and order records held by us are separate. Deleting your account with us does not delete an on-chain transaction.
If you need help with a payment issue, provide your order number, the approximate payment time and the relevant transaction details. Do not send full card numbers, security codes, wallet private keys or recovery phrases through a support ticket or email. We check payment information only to verify the transaction and handle the related bill.
4. Data on your instance
Each cloud Mac is a dedicated physical Mac mini assigned to one customer, not a virtual machine. You control the project repositories, signing certificates, provisioning profiles, build artifacts and work documents stored on your instance. We do not read the contents of these files.
You are responsible for managing instance access credentials, team member permissions and data backups. If team members in different time zones take turns using the same machine, agree on who is responsible for uploading, exporting and deleting files. Keep account activity records separate from responsibility for storing project files.
For technical troubleshooting, we start with the instance ID, node, time of the issue and connection symptoms. Any logs or screenshots you choose to submit become part of your support ticket; remove unrelated file contents and sensitive credentials first. If you need to export data, do so while your instance service is active and check that your backup can be read.
5. Data locations
Data on your instance is stored on the physical Mac at the node you select. The five available nodes are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the US West Coast. Check your selected node before paying, and make sure it meets your team's requirements for storing project files, customer materials and other data.
When you connect from another region using a remote desktop, SSH or file transfer, data travels between your access network and the selected node. Where team members are located does not automatically change where instance data is stored or move an instance between nodes.
To change nodes, create a new instance at the destination node and migrate and verify your files yourself. Node selection applies to data on your instance; it does not mean that account, billing, payment processing and support ticket records are handled only at that node. Contact us before submitting sensitive materials if you need details about how we handle this service management information.
6. Retention and deletion
We retain account information for as long as needed to provide account services. We keep order, billing and payment verification records for as long as needed to complete transactions, resolve disputes and meet applicable record-keeping requirements. Support tickets and access logs are retained for support, security and troubleshooting purposes. Because retention periods vary by data type, this policy does not give one timeframe for all data. You can ask us about the retention arrangements for information associated with your account.
Before your instance expires, export any files you need to keep and verify your backup. After expiry, the instance enters the service termination and data-clearing process. Once the service has ended, the previous customer's data is cleared before the instance is prepared for a later customer. An expired instance is not backup storage, so do not rely on being able to connect to it or recover files afterward.
To request account deletion, submit a console support ticket or email our support address and specify what you want deleted. We will verify account ownership and check whether you have an active instance, an outstanding bill or an ongoing transaction dispute, then explain any steps you need to take first. Deleting an account and clearing instance files are separate actions. Tell us if you also want to terminate an instance and delete its data.
Information that must be retained under applicable record-keeping requirements or because of an unresolved dispute will not be deleted immediately just because you close your account. We limit its handling to the relevant purpose. Before you submit a request, you may ask which categories of information we retain and why. Once instance data has been cleared, you should not expect it to be recoverable.
7. Cookies and analytics
The console uses cookies, browser storage or similar technologies to maintain your sign-in session, support necessary security checks and remember interface preferences. Disabling or clearing this storage may sign you out, require you to verify again or remove saved preferences.
The website uses same-domain analytics to record page visits and key interactions, such as starting an order, viewing support content or expanding an answer. This helps us understand which content helps users complete tasks. Analytics covers how pages and flows are used; it does not collect project files from your dedicated Mac or require you to submit file contents as analytics data.
You can manage cookies, site data and permissions in your browser settings. When you finish using the console on a shared device, sign out and clear the relevant site data. Simply closing a tab may not end your session. Clearing browser storage does not automatically delete your server-side account or billing records.
8. Your rights and how to contact us
You can request access to, correction of or deletion of information associated with your account. You can also ask how specific information is used, how long it is retained and how your request is being handled. If you are signed in, submit a support ticket in the console. If you cannot sign in, contact us at support@macudp.com.
Include your account email address, the type of request, any relevant order or instance ID, and the specific information you want to access, correct or delete. Do not include your password or full payment credentials. To protect your information from disclosure to others, we need to verify that you are associated with the account and may ask for additional details directly relevant to your request.
If your request involves an active instance, tell us whether you want to keep the service and back up your files first. We will handle your request based on its scope, the results of verification and applicable requirements, then reply through the original ticket or by email. If any information cannot be deleted immediately, we will explain why and what happens next.
9. Policy updates
We will update this page if our service processes, the types of information we handle or applicable requirements change, and revise the version and effective date accordingly. We will communicate significant changes that affect accounts or existing services through channels related to the service, such as the website, console or account email.
Review the relevant sections before creating an instance, moving to another node or submitting sensitive support materials. If you have questions about an update, contact us through a console support ticket or by email. Requests to access, correct or delete information should still be submitted through the channels described in section 8.