Scope
This policy applies to information processing that occurs when you visit macvpsgo.com, create or manage an account, configure a cloud Mac order, view host and billing information, or contact our support team by email or console ticket. Service users include visitors, prospective customers, account holders, order contacts, and authorized team members.
The website introduces Apple Silicon dedicated physical nodes, fixed configurations, recurring prices, and node availability. The management console supports account verification, order configuration, payment, delivery information, and ticket management. Support communications help diagnose connection, build, network, storage, and billing issues. Different steps require different information; simply viewing public pages does not require order-level details.
A rented cloud Mac is a dedicated physical node delivered for the customer's use. Code, build artifacts, certificate files, and working directories stored by the customer on the node do not become website operational data under this policy. If a customer voluntarily includes relevant excerpts in a ticket or email, that copy is handled as support material and is subject to this policy's provisions on logs, diagnostics, and retention.
This policy does not replace the customer's own notice obligations to projects, team members, or end users. Customers should determine, based on their business and applicable requirements, what data may enter a cloud Mac, who may access it, and when it should be deleted.
Information We Collect
We collect information needed for the actual use case rather than building an unrelated profile all at once. Visitors who create no account or order generally generate only basic access and device information; information needed to complete a purchase, delivery, or support process is handled only when that process begins.
Account Information
This includes the login email address, verification results, account status, necessary security event records, and contact information the user actively maintains in the console.
Order Information
This includes the selected Go M4 Core, Go M4 Plus, or Go M4 Pro configuration, rental period, node, add-ons, order status, billing records, and delivery-related information.
Device and Browser Information
This includes browser type, operating system category, page requests, language settings, session identifiers, and network information used to investigate abnormal access.
Connection Records
This includes necessary timestamps, sources, and outcome records related to node access, authentication results, session establishment, and service security. It is not collected to read customer code.
Support Materials
This includes order numbers, nodes, reproduction times, error logs, screenshots, network environments, and troubleshooting steps already taken, and enters the support process only after the user submits it.
Communication Records
This includes email subjects, message content, ticket status, staff notes, and resolutions, helping preserve context and reduce repeated questions.
How We Use Information
We use information for service activities directly related to user requests and limit access according to purpose. Our main processing purposes are:
- Service Delivery:Create orders, confirm configurations and nodes, match payment results, provide host delivery information, and maintain subscription and billing status.
- Account Verification:Send and validate verification codes, identify login status, process account recovery requests, and prevent unauthorized access.
- Order Processing:Record the primary configuration, daily, weekly, monthly, or quarterly rental period, SSD or Thunderbolt 5 add-ons, and subsequent order changes.
- Security:Identify unusual logins, abuse, malicious scanning, credential attacks, and conduct that may affect physical nodes or the service network.
- Support:Use the order number, node, time, and error information submitted by the user to diagnose connection, Xcode build, CI runner, storage, or billing issues.
- Compliance:Keep necessary transaction and communication records, respond to legally valid requests, and maintain audit trails related to service delivery.
We do not use code snippets, build logs, or screenshots in support tickets for marketing analysis unrelated to resolving the issue. When internal collaboration is needed, access is limited to the necessary content for staff directly involved in diagnosis, account handling, payment reconciliation, or infrastructure operations.
Payment Information
All orders are settled in USD. Available payment methods are limited to USDT-TRC20 and Visa, Mastercard, or Amex processed by Stripe; the payment gateway actually available is determined by the console in real time.
USDT-TRC20
We may process the order amount, transaction ID, on-chain confirmation status, receiving-address association, and timestamps used to reconcile payment. Transaction data on public blockchains may be processed by independent network participants.
Visa, Mastercard, Amex
Card information is handled through Stripe's payment process. We receive the payment result, amount, currency, transaction reference, and limited card descriptor information needed to complete the order and reconcile billing.
We do not store full card numbers, card security codes, or data that could directly reconstruct complete card credentials. To handle refund reconciliation, payment disputes, billing inquiries, or security reviews, we may retain transaction references and status records returned by the payment processor.
Logs and Diagnostics
To keep the website, console, order flow, and node connections stable and secure, we retain logs necessary for diagnostics. Logs may record request times, response results, error types, authentication events, session status, source network information, and technical identifiers associated with orders or nodes.
Logs help diagnose service errors, analyze unusual access, verify delivery status, and reproduce paths described in support tickets. As part of routine operations, we do not proactively request complete source code, complete build artifacts, or business data unrelated to the issue.
Do not submit passwords, private keys, access tokens, signing passwords, complete payment credentials, or other information that could directly grant access in emails, tickets, screenshots, or logs. If troubleshooting requires configuration details, mask sensitive values and include only the fields needed to reproduce the issue.
If support materials accidentally contain clearly sensitive information, we will restrict access as needed to handle the issue and, without affecting necessary records or legal obligations, take steps to delete, truncate, or redact it. Users may also request cleanup after the issue is resolved.
Retention and Security
Retention periods depend on the processing purpose, account and order status, whether a support issue is closed, whether security risks have been resolved, and applicable record-keeping obligations. Once the purpose is fulfilled and there is no continuing basis for retention, we delete, anonymize, or restrict further use of the information.
Order, payment, and billing records may need to be retained for as long as necessary to complete reconciliation, resolve disputes, and meet related obligations. Account security and authentication records are retained as needed to prevent abuse and investigate unusual events. Support materials are managed according to issue complexity, the likelihood of recurrence, and user cleanup requests.
Access Controls
Data access is limited by role and processing task, preventing unrelated personnel from viewing account, order, or support materials.
Least Privilege
Systems and personnel receive only the permissions needed for verification, delivery, billing, or diagnostics; access is not expanded for convenience.
Transmission Protection
Website and console communications use transmission protection measures to reduce the risk of interception or tampering while information travels over networks.
Incident Response
We record, restrict, investigate, and take necessary follow-up action for abnormal authentication, abuse, unauthorized access, and other security incidents.
No technical or organizational measure can eliminate every risk. Users should use a separate, controlled email address for verification codes, limit team members' node access, regularly clear runner working directories and build caches, and avoid copying long-lived credentials into support materials.
Your Choices and Contact
Users may request access to, correction of, deletion of, or restriction on processing of information related to them, or raise privacy questions. Whether and to what extent a request can be fulfilled depends on account and order status, the requester's relationship to the data, necessary security verification, record-keeping obligations, and other applicable requirements.
-
1
Describe the Request Scope
Specify the categories of information you want to access, correct, or delete, along with the relevant account, order, or support ticket scope. Avoid submitting sensitive materials unrelated to the request.
-
2
Complete Identity Verification
To prevent impersonation, we may require contact from the email address associated with the account or completion of necessary verification in the console.
-
3
Receive the Outcome
We will explain the measures taken, any parts that cannot be completed directly, and the basis for those limitations. Complex requests may require further confirmation of the data scope.
Privacy requests, business inquiries, security reports, and compliance document requests may be sent to support@macvpsgo.com. Users with existing orders may also log in to the console and submit a ticket so the request can be linked to the correct account, order, and processing records.
Do not send node login credentials, private keys, tokens, or signing passwords with a privacy request. If the request concerns a team account, explain your authorization relationship; we may verify your authority before disclosing, modifying, or deleting information.