1. Scope and updates
This policy covers information processing when you visit the VPSOmni website, create and use an account, rent a remote Mac desktop, make a payment, or contact support by email or through a Console ticket. The service provides dedicated physical Mac mini systems with Apple Silicon M4 / M4 Pro, each assigned to one customer for remote use—not a virtual machine.
This policy distinguishes between service information we process to fulfil orders and project content you store on your dedicated Mac. These have different purposes: providing the service requires us to verify your account and order, but that does not mean we inspect your source code, signing certificates, or project files.
We will update this page if our service processes or information practices change. We will notify you through the website or Console about significant changes to the information we collect, how we use it, or how you can exercise your rights. Please review the current version before continuing to use the service. Where applicable law applies, we follow the laws of the jurisdiction in which the platform operator is based. Any related disputes will be handled by courts with jurisdiction in that same jurisdiction.
2. Information we collect
Account information: Your email address, information needed to verify your account and sign in, and any details you choose to provide help us verify account ownership and provide account services. Use an email address you can continue to access. Never send your password, verification codes, or private keys by email or support ticket.
Order and billing information: Your selected model, location, billing period, add-ons, order number, service dates, amount due, and payment status help us provide the service you purchased, verify billing, and process renewals. We handle these records separately from development files on your dedicated Mac.
Support content and access logs: We process issue descriptions, attachments, contact details, and support correspondence that you choose to provide in tickets or emails. To verify access and troubleshoot problems, we also process service-related IP addresses, access times, browser or client details, sign-in results, and error records. Before sharing screenshots, redact credentials, source code, and personal information that are not relevant to the issue.
3. Boundaries around project content on your dedicated Mac
Your dedicated Mac does not share its system, disk, or keychain with other customers. We do not inspect the source code, certificates, project files, or simulator caches stored on your machine, use them for website analytics, or treat them as advertising or marketing material.
If troubleshooting requires a build log, error screenshot, or configuration excerpt, share only the minimum information relevant to the issue. Files you attach to a ticket or email are handled as support materials; that is different from the platform accessing your development environment to inspect files. If an error code or redacted log is enough to explain the issue, you do not need to send your entire project.
A dedicated machine is not an automatic backup. You remain responsible for managing repository credentials, certificate private keys, and project backups. Before you finish, revoke repository access you no longer need, export files you want to keep, and remove sensitive information that should not remain on the remote machine.
4. How we use and protect information
Service setup and billing: We use account, order, and payment information to match your rental configuration, provide the physical node you selected, and display service dates, bills, and renewal details. This information is needed to complete your purchase and provide the service; we do not need to read your project source code.
Security and customer support: Sign-in and access records help us detect unusual access, verify account ownership, troubleshoot connection errors, and resolve service disputes. Ticket content you provide helps us reproduce issues, communicate outcomes, and keep relevant support records. A support request does not require you to hand over all your development credentials.
Access to information is limited to what is needed for the relevant task, with appropriate access controls for account verification, service operations, and troubleshooting. If a service provider, such as a payment processor, needs to process information, we share only what is necessary for that task. We handle requests for information as required by applicable law. If you suspect someone else is using your account, contact us through the support channel listed on this page and change the relevant credentials as soon as possible.
5. Payment and settlement
We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. All payments are settled in US dollars (USD). Available payment gateways are determined by the response from our backend. Before paying, check the order, amount, and gateway details on the checkout page.
Stripe processes card payments; we do not store full card numbers. To verify orders, we process payment status, transaction references, amounts, and necessary billing records. Do not send full card numbers or card security codes in tickets, emails, or screenshots. To ask about a payment, provide your order number and transaction reference.
For USDT-TRC20 payments, we record only information needed to confirm the transaction and match it to your order, such as the transaction reference, amount, and confirmation status. On-chain transaction records are publicly viewable. Deleting an account or support records does not delete transactions from the public blockchain. If a payment has not been matched to your order, provide the order number and transaction reference—never send wallet private keys or recovery information.
6. Data retention, deletion, and account closure
We retain account, order, billing, security log, and support records only as needed to provide the service, verify transactions, resolve disputes, and meet applicable legal requirements. Different types of information serve different purposes, so we do not apply one fixed retention period to everything. Information that is no longer needed will be deleted or de-identified.
When a rental expires without renewal, the service stops. This does not mean files will remain available for retrieval or that the disk is erased as soon as the service stops. The timing of machine recovery and data erasure depends on the relevant order, expiry notices, and support confirmation; we do not promise a standard additional retention period. Before expiry, back up your projects, export any certificates you need, and remove repository credentials from the remote machine. Do not rely on post-expiry access as a backup plan.
To close your account or request data deletion, sign in to the Console and submit a ticket, or contact support from your registered email address. We first verify account ownership, explain whether an active rental, unpaid bill, or dispute record affects your request, and then confirm what can be deleted. Closing an account, ending a rental, and erasing machine data are separate actions; specify which ones you are requesting. Transaction or dispute records that we are legally required to retain will not be deleted immediately when you close your account.
7. Cookies, local storage, and analytics
The website and Console use cookies or browser local storage to keep you signed in, complete security checks, and save essential interface preferences. These technologies support access to the service. If you block or clear them in your browser, you may need to sign in again, and some session-based actions may no longer work.
We use same-origin website analytics to understand page views, traffic sources, and key actions so we can improve our content and checkout process. Analytics data is handled separately from project files on your dedicated Mac and is not used to read source code, certificates, or disk contents. Do not enter passwords, private keys, or other unnecessary sensitive information in page query parameters, ticket titles, or similar fields.
You can view, limit, or clear this website’s cookies and local storage in your browser’s site data settings. Clearing browser data will not sign you out of your platform account or delete existing order and billing records. To ask about analytics data or how it is processed, contact us through the privacy request channel.
8. Your rights and contact
Where permitted by applicable law, you can ask how we process information about you, access or correct your account details, request data deletion or account closure, or object to or restrict certain processing. In your request, identify the relevant account and information, and tell us what action you would like us to take. You do not need to provide project source code to make a privacy request.
Existing users can sign in to the Console and submit a ticket. If you cannot sign in or prefer email, contact us at support@vpsomni.com. We suggest using “Privacy request” as the subject. Please use your registered email address where possible and include any relevant order references. We will first verify your identity to prevent your account information from being shared with anyone else. If we need additional information, we will explain why; we will never ask you to send a password or verification code.
We handle privacy requests based on identity verification, the scope of the request, and whether it involves an active service or a legal retention requirement. We do not promise a fixed completion time before reviewing the request. If we cannot fulfil it in full, we will explain why, what types of information must still be retained, and how you can follow up.