1. Scope and date of this policy
This policy applies when you visit the VPSPull website, register for or use the console, order a cloud Mac, or contact us by email or through a console support ticket. The service provides dedicated Apple Silicon physical machines, not virtual machines. Account management records and work data on your instance are handled separately, as explained below.
This policy was updated on October 13, 2026. The date at the top of this page shows when the current text was last updated. We will update this page if our data practices change. If a material change affects the purposes of processing or your rights, we will notify you through an appropriate service notification channel. Where the law requires consent, we will ask for it separately.
This policy explains how information is handled; it does not replace the model, billing period, node, or price details in a specific order. Check the configuration page before placing an order. For privacy requests, prepare the information described in Section 8 and contact us using one of the channels listed in Section 9.
2. Information we collect
Account and communications. We process the email address you provide to register, sign in, and communicate with us, along with account verification and security settings and support correspondence. Names, team names, issue descriptions, and attachments you choose to include in an email or ticket may also be processed as part of that request. Please share only what is needed to resolve the issue. Never send passwords, verification codes, or complete connection credentials.
Orders and payments. We process service records such as order IDs, models, nodes, billing periods, add-ons, amounts in US dollars, and payment status. The only supported payment methods are USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Stripe processes card details; VPSPull does not store full card numbers or card security codes. For USDT-TRC20 payments, we record the on-chain transaction hash as proof of payment. We do not ask for your wallet's private key.
Console access logs. To detect unusual sign-ins, troubleshoot API errors, and track service operations, we process access times, IP addresses, browser or client information, request results, and related operation records. These logs show which account performed a service operation and when. They are not recordings of your remote desktop and do not mean we continuously read files on your machine.
3. What we do not access proactively
During your rental, project code, build artefacts, assets, models, documents, and remote sessions on your instance are your work data. We do not proactively inspect these files for advertising, profiling, or routine operations, and we do not use your desktop sessions as routine analytics data. You can use the macOS graphical interface and command line for your own work.
If you ask us to troubleshoot an issue and resolving it genuinely requires access to information on your instance, we will first explain what we need to access, why, and how much access is required, then obtain your explicit authorisation. Authorisation must relate to a specific issue, such as checking an error log or a connection setting. Submitting a support ticket does not authorise access to everything on your machine.
You can ask us to narrow the scope of troubleshooting or stop further access. Where possible, provide screenshots, error text, and steps to reproduce the issue with sensitive information removed. Necessary records collected during support are retained under the rules for support materials. Withdrawing authorisation does not affect processing lawfully completed before the withdrawal.
4. How we use data
Providing and managing the service. Account and order information is used to verify your identity, match payments, provision your instance, show connection details, manage your rental period, and process renewals. We use only the information needed to provide the relevant service. Renting a machine does not mean you have to provide personal information unrelated to that service.
Billing and security. Payment status and transaction records help us reconcile payments, resolve billing issues, and investigate unusual payments. Console logs help us detect unusual access, investigate unauthorised activity, and protect accounts. If a dispute arises, we may retain records directly related to it to verify the facts and handle the request.
Service notices and support. We use email and support ticket records to send account verification, order, rental-period, and security notices, and to respond to questions you raise. These notices relate directly to managing the service. Website analytics are described in Section 7; we do not use files or remote session content from your instance to assess page performance.
5. Data storage, retention, and disk erasure
Account, order, payment status, and support records are stored in systems used to operate the service. Your work files are stored on the storage devices of your rented instance. Access to operational records is restricted according to work responsibilities, and we use access controls and appropriate security measures to protect them. Node location and the storage location of account records are not the same thing. If you need to confirm where a specific category of data is stored, please ask before placing an order.
We set retention periods by data category and purpose rather than promising one deletion date for all information. Account details are retained for as long as needed to provide account services. Order and payment records are retained as needed for reconciliation, dispute handling, and applicable legal requirements. Access logs and support attachments are retained only for as long as needed for security investigations, issue resolution, and related obligations. When the purpose ends, information is deleted or processed so it can no longer identify an individual. Information that must be retained by law is subject to restricted use and access.
When a rental ends, the instance disk enters the erasure process before being used for a subsequent service. Erasure does not include keeping a backup for you, nor does it delete order records that must be retained by law. Before your rental expires, export code, assets, certificate files, and any other data you need to storage under your control, then check that your backups open correctly. Do not plan your work on the assumption that data can be recovered after expiry.
6. Third-party processors
Payment processing. If you pay with Visa / Mastercard / Amex, Stripe processes the card information and transaction data needed to handle the payment. We use records needed to match the payment to your order, confirm the payment result, and reconcile accounts. The gateway available at checkout is determined by the checkout interface. The relevant processor handles the payment under its applicable terms.
Infrastructure services. Infrastructure providers may process data needed to provide network, hosting, or system operations support for the website, console, and physical nodes. We limit what we share according to each provider's role. We do not give infrastructure providers account or support materials unrelated to their work, and we do not sell tenant work files to third parties.
If service arrangements involve data processing across jurisdictions, we will apply appropriate safeguards as required by applicable rules. You can ask by email or support ticket about the processors, storage locations, and safeguards relevant to a specific category of data. Please specify the order or scope of your review. We will explain the arrangements for the service you use rather than treating a node name as a description of data flows.
7. Cookies and analytics
The website and console may use cookies or local storage to maintain sign-in sessions, security verification status, language selection, and necessary interface preferences. Session storage lets the system recognise that you have completed verification; it is not used to read your instance disk. You can review and clear this storage in your browser settings, but doing so may require you to sign in again or reselect your preferences.
We use a same-origin Matomo deployment to understand website visits and use of key entry points, such as page views, plan links, and checkout links. Analytics help us improve website information and user flows. They do not record remote desktops or collect instance files, passwords, verification codes, or complete payment details as analytics event data.
Where applicable rules require consent, non-essential analytics will be enabled only after the relevant consent has been obtained. You can restrict cookies in your browser and use the channels in Section 9 to ask about analytics processing or request that non-essential analytics be disabled. Restricting analytics will not prevent you from viewing prices or this policy. Restricting essential session storage may affect sign-in.
8. Requests to access, correct, delete, or export data
To the extent permitted by applicable law, you can ask to access personal information we hold about you, correct inaccurate information, delete information that is no longer needed, or export records relating to you. You can also ask us to restrict or object to specific processing, or withdraw consent. You are responsible for backing up and exporting work files on your instance. A request to export personal information is not a substitute for backing up the entire machine's disk.
Send your request from your registered email address or sign in to the console and submit a support ticket. Include the type of request, the relevant account or order ID, and the data involved. We will verify your identity in a way proportionate to the risk. If we need more information, we will tell you what is missing. Do not include your account password, verification code, card security code, or wallet private key.
After verification, we will handle your request and explain the outcome as required by applicable rules. If certain order, payment, or security records cannot be deleted immediately because of legal obligations, an unresolved dispute, or the need to protect another person's rights, we will explain why they are retained, how processing is restricted, and what alternatives are available. Closing your account or deleting information may affect services you are using. Complete any necessary backups first and specify which services you want to keep.
9. Contact and complaints
For privacy questions, rights requests, security reports, or complaints about data processing, email support@vpspull.com. If you already have an account, you can also sign in to the console and submit a support ticket so we can link your request to your account and order. We will not ask you to submit sensitive information through other email addresses or social channels.
To help us process your request, put “Privacy request” and the type of request in the subject line. In the message, describe the data involved, the relevant order or instance ID, the circumstances, and the outcome you are seeking. Before attaching screenshots or logs, redact keys and unrelated personal information. We will respond as needed to verify and investigate your request. Sending an email or ticket does not mean that deletion, export, or complaint handling is complete.
This policy is governed by the laws of the jurisdiction in which the platform operator is located. Any dispute will be handled by the courts with jurisdiction in that jurisdiction. Nothing in this policy limits any complaint rights or other rights you may have under applicable law. If you have questions about how we handled your request, you can follow up with specific details in the original email or support ticket.