1. Scope
This policy applies to the cloud Mac rental, account management, order and billing, and support services available on vpsmerge.com and through its portal. It covers information processed when you browse public pages, register or sign in, rent a dedicated physical machine, or contact us by email or through a support ticket in the portal.
This policy distinguishes information needed to operate the service from customer data stored on an instance. Account email addresses, orders, and support tickets are used to provision and manage the service. Projects, build artifacts, certificates, and other files you store on a physical node are instance data; their handling is described in Section 4. Each dedicated physical machine is a physical computer, not a virtual machine, and is not shared with another customer.
You decide how to use and what to submit to software and services that you install, configure, or connect to on your instance. Review their data handling practices before connecting them. This policy covers VPSMerge's own processing when providing its services.
2. Information we collect
Account information: The email address you use to register, verify your account, sign in, and contact us, along with necessary account verification and security records. Make sure you can receive email at this address so you can get verification codes, order notifications, and replies to your requests. Do not include email verification codes or instance passwords in public feedback.
Orders and billing records: The selected plan, billing period, node, storage and other add-ons, order ID, amount, payment status, and renewal history. We use this information to provision the relevant physical node, reconcile bills, and manage service time. It does not mean we need to access your project files.
Support tickets and email: The subject, message, instance ID, timeframe, and diagnostic materials you choose to provide. Logs may contain file paths, repository names, or access tokens. Before sending them, remove personal information and secrets that are not needed to investigate the issue. For build failures, share the relevant error output rather than your entire project.
Access logs: IP addresses, access times, request paths, browser or device details, and error records generated by requests to the website and portal. We use these records to detect unusual access, troubleshoot failed requests, and protect account security. They are not used to read files on your instance.
3. Payment information
Services are priced and billed in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. The payment gateways available at checkout are determined by the response from our backend.
Stripe processes card payments. We do not store full card numbers. To confirm payment and resolve billing issues, we retain necessary order references, amounts, payment statuses, and payment transaction IDs. Do not send full card numbers or card security codes by support ticket or email.
For USDT-TRC20 payments, we record only the transaction hash and amount needed to reconcile the order, and link them to the relevant order. A transaction hash can be used to locate a transaction on the blockchain and should not be treated as anonymous information. Do not post payment screenshots containing information linked to your personal order on public pages.
4. Instance data
Projects, files, build artifacts, and configurations on a dedicated physical machine belong to the customer. VPSMerge does not read this content or use it for analytics or model training. Information needed to operate the service, such as orders, allocation, and connection status, is handled separately from project files on your instance.
If you need help troubleshooting an issue, provide the relevant error information through a support ticket. A support ticket alone does not authorize support staff to access all of your projects. If assistance requires access to instance content, we will first clarify the scope, and you can decide whether to provide the relevant materials or grant access.
When an instance is released at the end of a rental, its disk is erased. The next customer does not receive the previous customer's projects or files. Export any data you want to keep before the instance is released, and make sure your backup works. Erasing the disk does not also delete personal billing, order, or support records; these operational records are handled as described in Section 5.
Teams should manage instance credentials, repository access tokens, and build-signing materials according to their access policies. When a team member leaves, a pipeline is migrated, or credentials may have been exposed, promptly revoke the relevant access and rotate the credentials to protect your projects and artifacts.
5. How we use and retain information
We use information only to provide and protect our services. This includes verifying accounts, assigning dedicated physical nodes, processing payments and renewals, responding to support requests, investigating unusual access, and meeting applicable record-keeping obligations. Processing a bill or support ticket does not expand our access to instance data.
Account details are retained while the account is in use. Order, payment, and billing records are retained for as long as needed to provide the service, reconcile transactions, and meet applicable retention obligations. Support tickets and emails are kept as needed to resolve issues, review disputes, and support necessary service audits. Access logs are retained as needed for security investigations and troubleshooting.
Retention periods depend on the type of data, its purpose, and applicable obligations; we do not keep all information indefinitely. When the purpose for processing has been fulfilled and there is no longer a valid reason to retain the information, it will be deleted or anonymized. Data on an instance is handled through disk erasure after the instance is released, as described in Section 4.
You can ask us about the categories of data we hold about you, the basis for retaining it, and the applicable retention period. If a deletion request concerns transaction records that we are required to retain, we will explain why and to what extent. Those records will not be used for purposes unrelated to their retention.
6. Third parties and international transfers
VPSMerge provides 5 nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the eastern United States. The node you choose determines the service region where your instance's projects and files are stored. Accessing the instance from another region over SSH or VNC, uploading projects, or downloading build artifacts may involve international data transfers.
Information may be processed by relevant service providers when needed to handle payments, send email notifications, or deliver infrastructure. Stripe processes card payments. Information shared with third parties is limited to what they need to provide the relevant service. We do not send your instance's project files to payment processors.
Choosing an instance node does not automatically mean your account, billing, and support records will be stored in the same region. If your team has specific data residency, data processing, or compliance review requirements, email us before ordering with the data categories, desired node, and any restrictions so we can confirm whether the service meets your needs.
We do not sell personal information. Where third-party processing or international transfers are involved, we apply appropriate access controls and safeguards as required. You can ask about arrangements related to the services you use by contacting us as described in Section 9.
7. Your rights
You can ask to access personal information we hold about you, correct inaccurate information, delete information that is no longer needed, or export available account and service records. If we process information on the basis of your consent, you can also ask to withdraw it. Withdrawal does not affect processing already completed.
Submit a support ticket through the portal or email us from the address linked to your account at support@vpsmerge.com. Include the type of request, your account email, and any relevant order or instance ID. You do not need to provide a password, verification code, or complete payment credentials with your initial request.
To prevent someone else from claiming your data or having your account deleted by mistake, we may first need to verify your identity. Once verified, we will handle your request as required and let you know the outcome. If the request is unclear, concerns someone else's information, or conflicts with a necessary retention obligation, we will explain why and what we can do.
Exporting personal information is not the same as backing up your instance disk. Download your projects, cached dependencies, and build artifacts while the instance is still accessible. Deleting your account or ending the service may affect future access, so complete any necessary backups before confirming an instance release or information deletion.
8. Cookies and analytics
The website and portal use essential cookies or browser storage to maintain sign-in sessions, support security checks, and remember interface preferences. These mechanisms help identify a session and protect account actions; they are not used to access project files on physical nodes.
Website analytics help us understand page visits, feature usage, and errors. Analytics may include page paths, access times, browser information, and button interaction events. Source code, certificates, and build artifacts on your instance are not used as analytics data.
You can view, restrict, or clear this site's cookies and local storage in your browser settings. Clearing sign-in data may require you to verify your email again. Blocking essential storage may prevent sign-in, checkout, or session persistence from working properly. For questions or requests to restrict non-essential analytics processing, contact us by email.
9. Policy updates and contact
We may update this policy as our services, data handling practices, or applicable requirements change. The updated version and its effective date will be published on this page. We will provide appropriate notice through the website, portal, or your account email if there is a significant change to how we handle data. Review the relevant sections when adding services or changing how you use them.
For privacy questions, requests to exercise your personal information rights, and data security reports, contact us at support@vpsmerge.com. If you have an account, you can also sign in to the portal and submit a support ticket. Include the subject of your request, account details, and relevant dates, and avoid attaching unrelated project files or secrets.
This policy is governed by the laws of the jurisdiction in which the platform operator is established. Any dispute arising from this policy should first be discussed through the contact channels above. If it must be resolved through legal proceedings, it will be brought before a court with jurisdiction in that jurisdiction.