1. Scope
This policy applies to the osxbuild.com website, the OSXBuild console, and the account, ordering, payment-status lookup, instance management and technical support services we provide for cloud Mac rentals. It describes how we handle data when you browse the site, create an account, rent a physical node or contact support.
OSXBuild provides dedicated physical machines, not virtual machines. This policy distinguishes between account and transaction records we process to operate the service, and data you store, create and manage on the machine you rent. Having an entire machine to yourself does not mean account or billing records are stored only on that machine.
Payment processors handle payment information under their own applicable terms. You decide whether to use code-hosting, artifact distribution or other external services you connect to. This policy covers data handling within OSXBuild services only.
2. Information we collect
Account and orders.We process your account email, information needed to verify sign-ins, account settings, and order details such as order number, selected model, node, rental term, add-ons and order status. We use your email for account verification, service notices and support. You do not need to provide personal information unrelated to your rental.
Payments and billing.We process the order amount, billing currency, payment method, transaction reference and payment status to verify payments, invoices and refund requests. Stripe processes card payments; we do not store full card numbers or security codes. We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All payments are settled in US dollars (USD); available payment gateways are determined by the response from our backend.
Connection and access logs.To verify access and investigate unusual activity, we process necessary information such as access times, source IP addresses, request results, connection events, and device or browser details. These logs describe access to the service; they do not mean we read source code or build artifacts on your machine, and we do not record remote desktop screen content.
Support materials.Order details, issue descriptions, screenshots and logs you send by email or through console tickets help us investigate your issue. Before sending, remove access tokens, certificate private keys, passwords and unnecessary personal information. Build logs may also contain file paths, repository names or environment variables, so check them before sharing.
3. How we use information
Service delivery and account management.We use account and order details to verify service ownership, provision the relevant physical node, show instance status, and handle renewals, expiry and other order actions. Necessary service notices are sent to your account email or displayed in the console.
Billing and technical support.Payment status and transaction references help us verify invoices, investigate payment issues and handle related requests. Ticket details and error logs help us reproduce problems, assess their impact and report our findings. If we need more information to investigate, we will tell you what to provide rather than ask for your entire source code repository.
Security.Necessary access and connection logs help us detect suspicious sign-ins, abuse and unauthorized access, and protect our service and other users. Only personnel who need these records to deliver the service, handle billing, provide support or maintain security may access them, and only within the scope of their duties.
We do not sell your personal information or use code and build artifacts on your machine for ad targeting or model training. If a service provider processes necessary information on our behalf, we limit processing to the relevant purpose. Where disclosure is legally required, we provide only the information required.
4. Data on your machine
Source code, assets, signing certificates, provisioning profiles, archives, IPAs, test results and other artifacts that you upload to or create on your cloud Mac belong to you or their respective rights holders. We do not proactively read this content, collect it for service analytics or gain rights to use it by providing the machine.
You are responsible for managing access to data on your machine, including Keychain, SSH keys and automation credentials. Apply least-privilege access to signing assets and avoid committing private keys to shared repositories. If you need support, share redacted error excerpts where possible. If troubleshooting requires your authorization, we will first clarify the scope of the work and the materials needed.
When your rental ends and the machine enters the recovery process, its disk is securely erased and the system is reinstalled before the machine is assigned to another customer. Deleting your account is separate from machine recovery. Before requesting account deletion, check for active rentals, outstanding order obligations and files you need to export.
Before your rental ends, export any code, artifacts and configuration you want to keep to a location you manage. Do not treat the only copy of a file on the node as a backup. Erased data cannot be retained as recoverable material, and renting again later does not mean your original files will still be there.
5. Retention and deletion
We set retention periods according to the purpose of each type of data, rather than applying one period to everything. Account details are retained while we provide account services. Order, billing and payment-status records are retained as needed to fulfil transactions, reconcile payments and meet applicable legal requirements. Access logs and support materials are kept only as long as needed to troubleshoot issues, investigate security matters or resolve related requests.
When a processing purpose is fulfilled and there is no legal requirement or unresolved matter requiring further retention, we delete the relevant information or de-identify it so it can no longer be linked to you. Records may need to be kept longer to resolve billing disputes, investigate security issues or meet legal requirements. This does not change how data on your machine is erased during recovery.
To request deletion, submit a ticket from your verified account or email support@osxbuild.com from your account email. Specify the data categories and relevant order numbers. We will verify your relationship to the account and explain what can be deleted, any steps required first and the types of records that cannot be deleted immediately. Do not send passwords or private keys by email.
6. Cookies and analytics
Your account and the console may use cookies or similar local storage to maintain sign-in sessions, perform security checks and remember necessary interface settings. These technologies do not store files on your machine. Clearing session data in your browser may sign you out or require you to verify your identity again.
Our website uses Matomo analytics loaded from the same domain to understand page visits and button interactions, and to check whether navigation, content and ordering links work as intended. Analytics are limited to website visits and interactions. They do not collect source code, certificate private keys or build artifacts from your machine. Do not enter this information in website query parameters or support requests.
You can use your browser settings to restrict cookies, clear site storage or enable the browser's tracking protection features. Restricting essential session data may affect sign-in and console functions. To ask how records related to your account are handled or make a privacy request about analytics, use the contact options in Section 8.
7. Your data rights
Access and correction.You can view the account, order and billing information shown in the console. If your email, order ownership or another record is incorrect, tell us exactly where the record appears and what needs to be corrected. Changes involving account ownership or payment verification require identity checks first.
Deletion and restriction.You can request deletion of information that is no longer needed or ask us to restrict certain processing. We will assess what we can do based on your current service status, outstanding invoices, disputes and applicable law. If we must retain certain records, we will explain why; deleting your account does not mean all transaction records are erased.
Export.You can request an export of account and order records associated with your account that we can provide. Export source code, certificates and build artifacts from your machine using your own connection method. Do so before your rental ends; do not wait until after recovery and erasure to request file recovery.
When making a request, specify whether you want access, correction, deletion or export, along with your account email and any relevant order number. To prevent information from being sent to the wrong person, we may ask you to confirm from a signed-in account or provide verification appropriate to your request. We will never ask for your account password, SSH private key or signing certificate private key.
8. Contact and policy updates
For privacy questions, data rights requests or security reports, contact us at support@osxbuild.com, orsign in to the console and submit a ticket. For an existing order, a ticket helps us verify the account and service records. If you cannot sign in, email us from your account email address.
For email, we recommend using “Privacy request” and the specific request type as the subject. Include the relevant order number, the data you want us to address and an email address where we can reply. Do not attach passwords, private keys or complete payment card details. After verifying your request, we will update you on its progress. If we need more time or information, we will let you know through the same contact channel.
We update this policy when our services, data practices or applicable requirements change, and show the current version and effective date on this page. We will notify you of significant changes to processing purposes, information categories or your rights through an appropriate channel, such as our website, console or your account email. Review any updates before continuing to use the service.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Please first try to resolve any dispute through the contact channels above. If legal proceedings are necessary, they will be handled by a court with jurisdiction in that same jurisdiction.