Privacy is not an afterthought. Data use should be verifiable.

This policy applies to visits to vmrunner.com and to the necessary data processing involved in learning about, ordering, and managing dedicated Apple Silicon physical nodes through this website. Covered activities include browsing public pages, generating inquiry emails from the contact page, submitting support requests, accessing the console to manage orders, and the identity, security, and operational record processing required to deliver Cloud Mac services.

After you leave this website for the console, data directly related to account login, order configuration, billing reconciliation, node delivery, and ticket handling continues to be processed under the principles described in this policy. The chip, memory, storage, rental period, and node city for a specific order are determined by the order record confirmed by the user.

VMRunner collects only the data needed for access, inquiries, support, and service delivery in each context. Users should not submit private keys, full access tokens, certificate passwords, or unredacted configuration files in support requests.

If you provide a workload, target node, rental period, memory, or storage requirements on the contact page, these fields are used to generate structured inquiry content. Review the message before sending it and remove confidential information unrelated to the issue.

Data processing is tied to specific service actions. Each purpose has its own data scope; visiting a public page does not automatically cause technical information to be used in an unrelated order process.

Service delivery

Confirm the VMRunner model, rental period, node city, and storage add-ons selected by the user, then create the corresponding delivery record.

Identity and security checks

Verify that logins and sensitive actions match the account status, identify anomalous requests, and retain necessary security incident records.

Support response

Use the order ID, timestamp, reproduction steps, and redacted logs to diagnose connection, build, signing, network, or toolchain issues.

Billing reconciliation

Reconcile USD orders, payment results, billing periods, and confirmed add-ons, and handle billing discrepancies or transaction-status inquiries.

Performance diagnostics

Analyze request errors, page responses, and node service logs to distinguish issues caused by local networks, toolchain configuration, or workload.

Compliance records

Retain the necessary records for orders, payment results, security audits, and dispute handling to the extent required by applicable obligations.

All VMRunner orders are settled in USD. Available payment methods are limited to USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The gateway available at checkout is determined by the result returned by the backend.

Data is processed by service providers only when necessary for service delivery, security protection, payment processing, or compliance with legal obligations. Sharing is limited to the data fields required for the specific task, with processing boundaries controlled through access permissions, purpose restrictions, and records.

• Service infrastructure Used to host the public website, process console requests, retain necessary order records, and deliver rented physical nodes.
• Security and operations support Used to identify anomalous requests, control access, track errors, and handle security incidents. Only the data required for the relevant task is accessed.
• Payment processing Used to complete USD payments, return transaction results, and support billing reconciliation. Payment data is handled within the scope of responsibility for the selected payment flow.
• Legal obligations When a valid requirement applies and processing is necessary, the relevant data is processed under the laws of the jurisdiction where the platform operator is established.

VMRunner does not operate by selling contact information, technical information, or order-related information, and does not expand shared data fields for purposes unrelated to the services.

Retention periods are determined separately for service delivery, billing reconciliation, security audits, dispute handling, and legal obligations. Data that no longer needs to be retained is deleted or anonymized when the applicable period ends.

Backup copies may be removed gradually according to the established rotation cycle. Data entering the removal process is not used for new business purposes, and access remains restricted.

You may request access to, correction of, or deletion of applicable data, and ask about its processing purposes, source, retention status, and sharing scope. To prevent disclosure to the wrong person, VMRunner performs the identity and order-reference checks necessary for the request.

VMRunner uses access controls, least privilege, activity records, and necessary identity checks to ensure that data is processed only by people and systems needed for delivery, support, billing, or security tasks. Users should also protect their console credentials and submit only redacted information directly relevant to the issue in support requests.

• Least privilege

  Access is assigned by role and task; data unrelated to the processing purpose is not opened for convenience.

• Traceable processing

  Necessary records are retained for key account, security, and service operations to support anomaly investigation and verification of processing activities.

• Version updates

  When this policy changes, we update the current version information and retain necessary version records when the processing scope or user rights change materially.

This policy and the related data processing are governed by the laws of the jurisdiction where the platform operator is established. Any dispute arising from this policy that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction.