1. Home
  2. Privacy Policy
Data Processing Scope

Privacy Policy

This policy explains how DPLYMAC handles information through its content website, inquiries, order management, payment records, and technical support. We collect data only as needed for clear business purposes and provide channels to request access, correction, deletion, or restricted processing.

Effective date: September 6, 2026 Version: 1.0 Language: Simplified Chinese
Contents

Browse by processing activity

  1. 01Scope
  2. 02Information We Collect
  3. 03Purposes of Use
  4. 04Payment Data Processing
  5. 05Cookies and Basic Analytics
  6. 06Sharing and Processing by Service Providers
  7. 07Data Retention and Security
  8. 08International Processing and User Rights
  9. 09Policy Updates and Contact

Signed-in users can submit privacy requests linked to their orders through the console, making identity verification and processing tracking easier.

Submit a request in the console
01

Scope

This policy applies to information processing when you visit deploymac.com, read product and node details, contact us through the public support email, or register, verify your identity, place orders, manage devices, view billing, and contact support through the order management console.

The content site primarily provides information about Cloud Mac, dedicated physical machines, nodes, pricing, and operational documentation. The order management console handles account authentication, order confirmation, device delivery details, rental management, billing, and tickets. These workflows serve different functions, but necessary records may be linked by order ID, account email, or ticket number to identify the same user, verify an order, or resolve a technical issue.

This policy does not replace the privacy rules for software, code repositories, build jobs, or third-party services that users deploy on their Cloud Mac. Users are responsible for ensuring that their code, test data, and build artifacts come from lawful sources and are used with appropriate permissions.

02

Information We Collect

Depending on the specific steps required for access, ordering, and support, we process the following categories of information. We do not ask users to submit data unrelated to the matter at hand.

Access and security logs
This may include request time, pages visited, network address, response status, session identifiers, and records of unusual access, used to serve pages, diagnose issues, and detect abuse.
Device and browser information
This may include browser type, operating system category, language preference, screen and device type, and other basic technical information used for compatibility checks and interface adaptation.
Inquiry and form fields
This may include contact email, intended use, target node, estimated rental term, build concurrency, memory and SSD requirements, and notes submitted by the user.
Account and order information
This may include account email, verification records, order ID, selected model, rental term, node, add-ons, order status, and necessary delivery records.
Support communications
This may include ticket subject, issue description, incident time, node, redacted logs, attempted actions, replies, and issue status.

Before submitting logs, screenshots, or configuration snippets, remove passwords, private keys, certificate passphrases, recovery codes, and other sensitive credentials that could directly grant system access.

03

Purposes of Use

We use information only for clear business purposes and with an appropriate basis. Key purposes include:

  • Provide the service:Display content, create accounts, record configuration choices, confirm rental terms and nodes, deliver device information, and operate the console.
  • Verify orders:Link payment records and order IDs to accounts, and confirm the model, node, add-ons, and order status.
  • Handle support requests:Reproduce issues using device configuration, node, time, and command output, document troubleshooting, and respond to users.
  • Protect security:Detect unusual logins, automated abuse, malicious requests, and unauthorized access attempts, protecting accounts and the service environment.
  • Improve documentation:Aggregate common issue types and revise unclear or error-prone instructions without disclosing user identities.
  • Meet necessary obligations:Retain order, billing, security, and dispute records required by applicable obligations or business recordkeeping.

If information will be used for processing materially different from the original purpose, we will assess the new basis and, where needed, provide additional information or obtain authorization.

04

Payment Data Processing

All orders are settled in USD. We currently support USDT-TRC20 and Visa / Mastercard / Amex via Stripe; the available gateway is shown in the console.

To verify orders and manage billing, we may retain the order amount, currency, payment method category, payment status, transaction reference, creation and confirmation times, and records needed for refunds or disputes. For card payments, complete payment credentials such as card numbers are handled by the relevant payment process; we receive only the results and limited reference information needed to confirm the order.

USDT-TRC20 transactions may be publicly searchable on the blockchain. We process the transaction ID, amount, confirmation status, and order association only as needed to verify the order, and do not require users to repeat wallet information unrelated to verification in a ticket.

05

Cookies and Basic Analytics

The website and console may use necessary cookies or local storage to maintain login sessions, preserve security status, remember language and interface preferences, and prevent repeated entry within the same workflow. Disabling necessary cookies may prevent login, order management, or security checks from working properly.

We may perform basic traffic analysis to understand page views, entry pages, device categories, loading errors, and document usage. Results help improve page structure, compatibility, and instructions and are not used to profile code or build content inside Cloud Mac.

You can use browser settings to view, delete, or restrict cookies and clear locally stored preferences. After clearing them, you may need to select your language, start a session, or sign in again.

06

Sharing and Processing by Service Providers

We do not sell user information as a standalone product. We share only the minimum information needed for service delivery, security, payment processing, necessary compliance activities, or explicit authorization, and only with service providers responsible for the relevant tasks.

Processing categories may include infrastructure operations, email delivery, payment processing, security protection, logging, and troubleshooting. We limit accessible fields by purpose and control access through permissions, confidentiality requirements, and processing agreements.

Where records must be provided under applicable obligations, we verify the requester, authorization scope, and information category and narrow disclosure where permitted. For organization accounts, an authorized administrator may view information related to that organization’s orders, devices, and tickets within their permissions.

07

Data Retention and Security

Different information is retained for different periods based on its purpose. Sessions and temporary security states are generally kept only as long as needed for functionality; inquiry and ticket records are retained for issue handling, review, and service improvement; order, payment, and dispute records are retained for the periods required by business records and necessary compliance obligations.

When the purpose is fulfilled and there is no necessary basis for continued retention, we delete, anonymize, or restrict further use of the information. Backup records may remain during the established rotation period, with access restricted, and are removed when rotation is complete.

We use measures such as tiered access controls, authentication, activity logs, permission reviews, transmission protection, and anomaly detection to reduce the risk of unauthorized access, alteration, disclosure, or loss. Only personnel or system components that need the data for their duties may access the relevant scope.

Users should also protect account verification information and remote access credentials and avoid pasting sensitive content into public repositories, chat logs, or unredacted tickets. If you detect suspicious account activity, change your credentials promptly and submit a ticket through the console.

08

International Processing and User Rights

To provide Cloud Mac across nodes, order management, and support, information may be processed outside your location by systems or service providers responsible for the relevant tasks. We apply necessary safeguards based on data category, purpose, and access permissions and limit access to the minimum needed to provide the service.

Where applicable, you may request a copy of information associated with your account, correction of inaccurate information, deletion of data no longer needed, restriction of specific processing, or object to how information is processed. Some order, security, or billing records may not be immediately deletable because of necessary obligations. In that case, we will explain the limitation and stop unrelated use.

When submitting a request, use the email associated with your account and specify the request type and relevant order ID or communication records. To prevent impersonation, we may require account verification, but we will never ask you to send remote access passwords, private keys, or other sensitive credentials by ordinary email.

The laws applicable to this policy are those of the jurisdiction where the platform operator is established. Disputes that cannot be resolved through communication may be submitted to a court with jurisdiction in that jurisdiction.

09

Policy Updates and Contact

This policy takes effect on September 6, 2026. If the purposes of processing, product workflows, payment routes, or explanations of user rights materially change, we will update this page’s version and effective date and provide notice of the change where appropriate.

For privacy questions, email support@deploymac.com. Users with an account or order are encouraged to submit a ticket through the console and include the order ID so we can verify identity and link the processing record.

State the information you want to access, correct, delete, or restrict in your request. We will assess it based on the completeness of the information, identity verification results, scope of impact, and applicable obligations, then provide the outcome.

Privacy request access

Explain your request and the relevant records clearly

For existing orders, submit a ticket through the console first. For general policy questions, contact us through the sole public support email.

Submit a console ticket Email Support