1. Scope
This policy applies to how OSXFlow processes personal information when providing services through osxflow.com and the associated console. This includes browsing the website, registering and signing in, renting a dedicated physical Mac mini, making payments and renewing rentals, and getting support by email or through console tickets.
We distinguish between two types of data: service-management information, such as account details, orders, and payment status; and work data you store on your Cloud Mac, such as source code, build artifacts, certificates, model files, and other project data. These types of data are used and handled differently, as explained below.
This policy describes how information is handled and does not change your rights to your own data. Use the contents to find a specific section. To request access, correction, or deletion, follow the instructions in Section 7.
2. Information We Collect
Account information. We collect the email address you use to register, sign in, receive verification codes, and get service notifications, along with records needed to protect account security. If you contact support by email or ticket, your issue description, order number, and attachments are also included in support records.
Order records. We retain records related to service delivery and billing, including your selected model, node, billing period, storage expansion or parallel configuration, order amount, payment and renewal status, and related service records. This information helps us confirm what you purchased and which machine we need to deliver and manage.
Payment information. We accept USDT-TRC20 and Visa / Mastercard / Amex processed by Stripe. All payments are in US dollars (USD); available payment gateways are determined by the response from our backend. Stripe processes card details, and we do not store full card numbers. For USDT-TRC20, we record only the transaction hash for verification and link it to the order's payment status.
Essential technical records. We process essential request, security, and error records to maintain sign-in sessions and investigate issues. Do not include passwords, SSH private keys, full card details, or unrelated project files in support tickets or emails. If you need to share logs, remove sensitive information first.
3. How We Use Information
Service delivery and node management. We use account and order information to link your rental to your account, assign a physical node, provide connection details, and show your service period and renewal status. Your contact email is not shown in node details visible to other users.
Billing and ticket support. We use payment status to verify orders, resolve billing issues, and confirm renewals. Ticket details help us investigate reported issues, verify which service is affected, and document how they were handled. Support staff should access only the service-management information needed to resolve the issue.
Security monitoring. Essential access and security records help us detect unusual sign-ins, protect accounts, and investigate abuse. We do not sell your personal information or use source code, certificates, or model files on your Cloud Mac for ad profiling or model training.
4. Data on Your Cloud Mac
You own the data you upload, create, or store on your Cloud Mac. Your service runs on a dedicated physical machine, not a virtual machine; its CPU, GPU, and unified memory are not shared with other renters. We do not access your project files on the machine or use them as website analytics data.
You are responsible for managing project access, connection passwords, SSH keys, and certificates. When reporting an issue, share the node ID, error message, and redacted logs where possible. Do not include your entire project, private keys, or connection credentials in public descriptions or email subject lines.
When your rental ends, the entire disk is erased before the machine is assigned to the next user. Before your rental ends, export any source code, build artifacts, models, and configuration you want to keep. Do not rely on account deletion or end-of-rental processing as a backup. Account deletion, removal of order records, and erasure of machine data are separate matters; specify what you want removed when making a request.
5. Cookies & Analytics
We use only essential cookies and anonymous analytics. Essential cookies maintain sign-in sessions, help secure requests, and retain necessary interface settings. They are not used for cross-site ad tracking.
Anonymous analytics help us understand page visits and navigation so we can improve our content, navigation, and signup process. Analytics should not include your passwords, verification codes, SSH private keys, payment credentials, or files stored on your Cloud Mac, and are not used to read your projects.
You can view, clear, or restrict cookies in your browser. Clearing essential cookies may end your session, so you may need to sign in again. Restricting them may also affect sign-in and checkout in the console. For questions about analytics, contact us by email as described in Section 8.
6. Data Storage
Work data on your Cloud Mac is stored at the physical node you select. Available nodes are in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the eastern United States. When choosing a node, consider your team's location, working hours, and data storage requirements.
Node locations refer to work data on the machine. They do not mean that account, order, ticket, and payment-processing records are all stored on the same machine or in the same location. Payment processing also involves information needed by Stripe or to verify USDT-TRC20 transactions; choosing a node does not move payment processing onto the machine.
We limit retention according to how information is used: account information supports account services, order and payment records support transactions and billing, and ticket and security records support customer service and audits. When information is no longer needed and no applicable retention requirement applies, it should be deleted or anonymized. You can ask us about retention of information associated with your account.
7. Your Rights
Access and correction. You can access information associated with your account and request corrections to inaccurate details. First, check your account and order information in the console. If you cannot make the change yourself, sign in to the console to submit a ticket, or email support@osxflow.com from your registered address and tell us what you want to access or correct.
Account deletion. You can request deletion of your account and related personal information that is no longer needed. Before submitting a request, export any data on your machine that you want to keep and check for active rentals or outstanding billing matters. To prevent someone else from impersonating you, we will verify account ownership as needed, but we will never ask you to send a password or private key by email.
A deletion request does not mean all transaction records disappear immediately. We handle separately any information still needed to fulfill an order, verify a payment, resolve a dispute, or meet applicable retention requirements, and will explain what cannot be deleted right away. When you submit a request, specify whether you want access, correction, or deletion, and identify the relevant account and order. Do not send unrelated sensitive information.
8. Contact & Updates
For privacy questions, data rights requests, security reports, and compliance documentation inquiries, email support@osxflow.com. If you already have an account, you can also sign in to the console and submit a ticket. Tell us what your request concerns. If it relates to an order, include the order number. Do not include passwords, verification codes, or private keys.
This is version 1.0 and takes effect on the date this policy is published. The initial release covers account and payment information, data on your machine, cookies, data storage, and data rights requests. If we make significant changes to how information is handled, we will update the version information on this page and notify you through an appropriate service notice.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Any dispute relating to this policy will be handled by a court with jurisdiction in that jurisdiction.