1. Scope
This policy covers information processed when you browse udpmac.com, read product information, or contact us through publicly available channels. It also covers information processed when you order, manage, and use UDPMac cloud Mac services through the console. Browsing the site and managing orders while signed in involve different types of information, as explained below.
A cloud Mac is a dedicated physical machine you access remotely during your rental term, not a virtual machine. Project files, build artifacts, and signing materials you store on a node are different types of data from the contact information used to set up an order. Choose what to upload and where to place it in line with your team’s data management requirements.
This policy applies from the effective date shown on this page. Please read the service terms presented when you order together with theTerms of Serviceand your order confirmation.
2. Information We Collect
Contact information you provide
When you email us or submit a support ticket through the console, we process the email address, description of the issue, and any materials you choose to attach so we can identify your request and respond. Do not include passwords, private keys, signing certificates, or unnecessary personal information in your message or in screenshots that have not been redacted.
Information needed to place an order
To order and manage services, we process information such as your account ID, selected machine, rental term, node, add-ons, order, and payment status. Payment is available only through USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), and is charged in US dollars (USD). The console will show which payment gateway is available. The specific fields involved in checkout depend on the interface and processing configuration in use.
Service operation records
To provide nodes and troubleshoot service issues, we may process operational records related to instance status, connection attempts, support tickets, and incidents. Your project files, build logs, and artifacts may contain business confidential information or personal data. Limit access as needed, manage credentials carefully, and redact support materials before sharing them.
Essential site technical logs
When you access the site or console, systems may record request times, URLs, network addresses, browser or device information, and error records to secure access and diagnose issues. The fields actually recorded and the scope of processing depend on the site and service configuration in production; this description does not expand the information we collect.
3. How We Use Information
We use contact information and inquiry details to respond to questions about choosing a service, connectivity, billing, and data requests. Account and order information helps us verify configurations, process orders, deliver rented services, and manage them afterward. Include your order ID and the time an issue occurred so we can match your inquiry to the right service records.
Operational records and essential technical logs help us identify unusual access, troubleshoot connection or service issues, and protect service and account security. Any processing of project files or build artifacts should be limited to what is needed to provide the service or handle a support request you initiated. A sample troubleshooting request does not justify routine access to project content.
We may also process or retain information as needed to meet legal obligations under applicable law. This policy does not authorize using information for purposes not described here. If the purposes change materially, we will update the relevant information first.
4. Sharing and Service Providers
To provide the site, console, physical nodes, and supported payment processes, information may be handled by providers responsible for site hosting, service delivery, or payment processing, each within the scope of its role. Information sharing is limited to what is needed for the relevant task. For example, a payment processor does not need access to your project source code.
The information required and processing involved may vary by payment method. This page does not imply that every payment channel is available, and we will not list specific providers without verifying the current operating configuration. Check the active payment and service configuration for applicable providers and their roles.
If disclosure is required by law, we will handle information within the scope of applicable law and valid requests. If you give third-party tools or collaborators access to a node, you are responsible for checking their permissions and data practices.
5. Retention and Security
Retention periods depend on the purpose of processing, order status, dispute resolution needs, and applicable legal requirements. Different types of information may be kept for different periods; this policy does not promise a fixed deletion timeline that has not been verified. Before your rental ends, make sure you have a plan to export and remove project files, signing materials, and build artifacts.
We restrict access to account, order, and service records according to role, and take steps to minimize unnecessary exposure of personal information and credentials when troubleshooting materials are shared. Before submitting a support ticket, redact tokens, keys, personal information, and project secrets from logs and screenshots.
Every remote development environment requires users to manage access boundaries as well. Keep connection details secure, control sharing permissions, and regularly check which files your CI runners, scripts, and third-party tools can access.
6. Your Requests
To request access to, correction of, or deletion of information about you, visit ourcontact pagefor instructions, or email support@udpmac.com. For requests about an existing order, you can also sign in to theconsoleand submit a support ticket. Tell us what kind of request you are making and provide an order ID that can help us locate the relevant records. Do not send login credentials by email.
We may first need to verify your connection to the relevant account or order to avoid disclosing information to someone who is not authorized to access it. The information you can access, correct, or request to delete depends on its category, processing status, and applicable legal requirements.
We may need to retain some information to complete a valid order, resolve a dispute, or meet legal obligations. A deletion request does not automatically end an active rental term or remove information that must be retained by law.
7. Regional Use and Policy Updates
Available nodes are located in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States. Your choice of node affects the service region where project files and build artifacts stored on your cloud Mac are located. Your team should choose a node based on the project data, collaboration needs, and its own compliance obligations. The location of information processed through the site, console, and payment services cannot be inferred solely from your compute node selection.
We may update this policy if our service features, processing practices, or applicable requirements change. The page will show the new effective date. If a change materially affects how information is processed, we will notify users through a channel appropriate to their relationship with the service so they can review it before continuing to use the service.
If you have questions about data location or the scope of processing, contact us before ordering through ourcontact pageand tell us which node you plan to use and what categories of information you need us to check. The laws applicable to this policy and the handling of disputes are those of the jurisdiction where the platform operator is based, and disputes will be handled by courts with jurisdiction in that jurisdiction.