1. Scope
This policy applies to the vmfly.com website, the console and VMFly's cloud Mac rental services. It covers browsing the website, registering and signing in, configuring and paying for orders, using dedicated physical nodes, and submitting support tickets.
We distinguish between account and transaction information used to operate our services and customer data you store on a physical Mac. The latter includes code repositories, signing certificates, configuration files, build caches and build artifacts. Renting a node does not transfer ownership of this data to VMFly.
Please read this page to understand how we handle data before using our services. If you manage an account on behalf of a team, make sure you are authorised to provide the relevant contact information and that everyone using the node understands the backup, credential-handling and disk-erasure rules that apply when a rental ends.
2. Information we collect
Account and login information. To identify accounts, verify sign-ins and protect access, we process account email addresses, verification and login records, and relevant request details such as timestamps, IP addresses and necessary device or browser information. These records help us assess account access; they do not mean we read project files on your node.
Support tickets and communications. When you request support by email or through the console, we process the contact details, node ID, issue description, time of the error and log excerpts you provide. Before sending anything, remove passwords, private keys, signing certificate contents and access tokens. Troubleshooting usually requires only the relevant lines around an error, not your entire code repository.
Billing and payment records. We process orders, billing periods, amounts, payment status and the records needed to verify transactions. Payments are accepted only in USDT-TRC20 or by Visa / Mastercard / Amex (via Stripe), and are settled in US dollars. Records may include a USDT-TRC20 transaction hash or transaction identifiers and payment status returned by Stripe. VMFly does not store full card numbers or card security codes.
3. Data on your node
Each node is a dedicated physical Mac, not a virtual machine. You own the code, certificates, project configuration and build artifacts stored on it. We do not access or read this customer data, or use it for model training, content analysis or marketing.
During your rental, you are responsible for managing team access, connection credentials and backups. VMFly does not treat a node's disk as an off-site backup. Before moving a node, ending a task or reaching the end of your rental, copy any repositories, certificates and artifacts you want to keep to storage under your control. When submitting a support request, please provide redacted error information where possible.
When a node expires without renewal, service stops and the entire disk is erased before the node is assigned to another customer. Data erased from a node cannot be restored through an account data access or deletion request. Closing an account and clearing node data are separate processes. If you still have an active node, check your order status and export any data you need first.
4. How we use information
Providing and operating nodes. We use account, order and node-related information to confirm rentals, assign physical machines, provide console access, and manage renewals and expirations. Operational records and hardware troubleshooting rely primarily on service records; routinely accessing your project files is not part of how we provide the service.
Verifying payments and handling support requests. Order amounts, payment status and transaction records help us confirm payments, reconcile bills and resolve payment issues. We use the support information you provide to investigate reported issues, document how they are handled and keep the context for any follow-up on the same matter.
Protecting accounts and reviewing security events. Necessary login and access records help us detect unusual sign-ins, investigate misuse and trace security incidents. Access to these records is limited to what is needed for our work. We do not sell information collected to provide our services or use customer data on your node for other purposes.
5. Sharing with third parties
We share only the information needed with payment processors to complete transactions. For example, when a card payment is processed through Stripe, the order amount, currency, transaction identifiers and payment result are shared. Card details are submitted during payment processing and are not stored as full card numbers in VMFly account records.
For USDT-TRC20 payments, we use the transaction hash to verify the relevant order. Records on the blockchain are governed by the public network's own mechanisms; deleting your VMFly account records will not remove on-chain transaction records. Do not include confidential project information in public transaction notes or unnecessary communications.
We do not sell personal information or share your code, certificates or build artifacts with payment processors. If we receive a legally valid information request, we verify its scope in accordance with applicable requirements and limit any disclosure to what is necessary.
6. Retention and deletion
While your account is active, we retain the account, order and support records needed to provide our services. Retention periods vary by record and purpose: login records support access security, support records help us resolve and follow up on issues, and billing and payment records are used to reconcile transactions and meet applicable record-keeping requirements. We do not keep all data indefinitely.
After an account is closed, information no longer needed to operate the account will be deleted or anonymised. Records relating to open orders, payment disputes, security investigations or legal retention requirements may be kept only for as long as needed to resolve the matter or meet the applicable retention period. We will delete them once those reasons no longer apply. This policy does not promise a single retention period in days for all records; you can ask us about the retention scope and basis for data associated with your account.
To request deletion, contact support through a console ticket or from your account email. Include the account email address, the types of data you want deleted and any relevant order IDs. We will verify that you own the account before explaining what can be deleted and which records must be retained. Do not include passwords or private keys in your request. A deletion request does not replace the need to back up your node data before it expires.
7. Cookies and analytics
The website and console use essential cookies or similar local storage to maintain sign-in status, verify sessions and support basic security features. These mechanisms identify your current session; they do not access files on your physical node. Disabling essential cookies may prevent you from staying signed in or require you to complete identity verification again.
Basic usage analytics help us understand page visits, referral sources and feature usage so we can improve our content and service workflows. Analytics do not include your code, signing certificates or build artifacts, and should not include confidential information entered in an issue description.
You can view, clear or restrict cookies and site storage in your browser settings. Clearing them may end your current session, so you might need to sign in again. Clearing data in your browser only affects website storage on that device; it does not automatically delete your account, billing records, support tickets or data on a node's disk.
8. Your rights and contact
You can request access to information associated with your account, correction of inaccurate information, deletion of data that is no longer needed, or closure of your account. Visit our Contact us page to find out what to include. You can also submit a support ticket in the console or email us at support@vmfly.com.
To prevent data from being disclosed to someone who is not authorised to access it, we may ask you to make your request from your account email or provide information that helps us verify ownership of an order. Specify the type of request, the relevant account or order, and what you want us to address. If transaction settlement or applicable record-keeping requirements affect your request, we will explain why and what we can still do. We will not ask you for your node password as proof of identity.
This policy is governed by the laws of the jurisdiction in which the entity operating this platform is established. Any dispute concerning this policy will be submitted to the courts with jurisdiction in that jurisdiction. We will update this page if our data-handling practices change. We will notify you of significant account-related changes by email or through the console. You can also use the contact options above to ask about the policy currently in effect.