1. Scope
This policy applies to the cloud Mac rental service provided through the xcodenode.com website and its console. It covers the processing of personal information when you browse the site, create an account, configure an order, make a payment, manage a physical node or submit a support ticket. “We” refers to the platform operator; “you” means a visitor, account holder or authorized team member using the service.
Each rental order is assigned a dedicated physical machine, not a virtual machine. Your platform account and the work environment on your node are separate data scopes: your email, order details and payment references are used to manage the platform service. Projects, build artifacts and other files you create in macOS are node data. See Section 4 for how we handle them and Section 6 for erasure at the end of the rental term.
This policy does not replace your team’s internal access-control rules. Before granting team members access to a node, confirm the scope of their access and manage keys and work files yourself. If this policy changes materially, we’ll publish an update on the website or in the console. We’ll provide separate notice of any new processing purposes or matters requiring consent under applicable law. This policy is governed by the laws of the jurisdiction where the platform operator is based. Disputes will be heard by a court with jurisdiction in that jurisdiction.
2. Information We Collect
Account and support information. We process the account email you provide and the information needed for sign-in verification, service notifications and support tickets. If you contact us by email or through the console, the message, order number and issue description may also become part of your support record. Please share only what’s needed to resolve your issue. Never send passwords, private keys or complete signing materials by email or in a support ticket.
Order and payment records. We record the selected machine, node, rental term, add-ons, order amount, payment status, renewals and delivery details. Payment references, such as a Stripe transaction ID or USDT-TRC20 transaction hash, help us match payments to orders, verify transaction outcomes and resolve billing issues. Services are billed in USD. We accept USDT-TRC20 and Visa / Mastercard / Amex, processed by Stripe. Available payment gateways are confirmed by the checkout interface.
Access and security logs. When the website and console are in use, we may log IP addresses, request times, paths accessed, response statuses, technical information provided by your browser or device, and sign-in and account activity. We use this information to troubleshoot failed requests, detect unusual access and protect service security. These logs do not mean we read project files on your node. You don’t need to provide personal information unrelated to the service to rent a node.
3. How We Use Information
Node delivery and management. We use your account email to verify account ownership and send essential service notifications. Order details tell us which machine, node, rental term and add-ons to provide. The console links your order to its node so you can check service status, manage your rental or submit a support ticket. We process only what’s needed for these tasks; providing extra personal information is not a condition of delivery.
Billing and reconciliation. We use order amounts, payment references and payment status to confirm payments, prepare billing records, reconcile renewals and resolve payment disputes. For USDT-TRC20 payments, we verify on-chain records using the transaction hash. For card payments, we check the results returned by the payment processor. When reporting a payment issue, your order number and transaction reference usually help us identify it more accurately than a full payment screenshot.
Security reviews and service communications. We use access logs and account activity to detect unusual sign-ins, troubleshoot API errors and investigate incidents that may affect account security. Email and support ticket records help us respond to questions and notify you about your account or orders. We process this information as needed to provide the service, comply with applicable law and protect account and platform security. We’ll explain separately when consent is required. We do not use service communications to sell personal information.
4. What We Don’t Collect
We don’t access files or project data on rented physical nodes, and we don’t collect source code, build artifacts, model files, project documents or signing materials as personal information for the platform. Order management and billing require account and service records, not the contents of your working directories. Platform access logs do not mean we collect the contents of node files.
When troubleshooting, share redacted error messages, relevant command output and steps to reproduce the issue. Don’t send an entire repository, configuration files containing keys or data unrelated to the problem. If you choose to attach project snippets or logs to an email or support ticket, they become part of that support record. Before sending, check for tokens, personal information or anything your team prohibits sharing.
A dedicated machine means one machine is assigned to one tenant; it does not mean your work files receive additional backups. You’re responsible for managing node account permissions, SSH keys, application dependencies and backups. Before your rental ends, export any projects and artifacts you need and verify that your backups work. Don’t rely on recovering data after the rental ends as a backup plan.
5. Third-Party Processors
Visa / Mastercard / Amex card payments are processed by Stripe. Card details required to complete a transaction are submitted during payment processing; we don’t store full card numbers. We use the transaction reference, payment result and reconciliation details returned to us to manage your order, rather than storing complete card details in your account or support ticket.
USDT-TRC20 payments are verified against on-chain records using the transaction hash. On-chain transactions are publicly verifiable, and deleting your platform account cannot remove an existing on-chain transaction. To help us verify a payment, provide your order number and transaction hash. Never share your wallet’s private key or other credentials that could give someone direct control of your funds.
We don’t sell personal information. We share only the information payment processors need to process and reconcile transactions. We limit disclosures when required by applicable law or when legally necessary to investigate an incident affecting service security. For questions about third-party processing or data transfers, contact us using the details in Section 8. We’ll explain how they relate to your account and order.
6. Data Retention
We keep account information for as long as needed to provide the service and manage your account. We retain order and billing records for the periods required by applicable law to reconcile transactions, meet accounting obligations and handle disputes. Deleting your account does not necessarily delete all order or payment records immediately. We limit the use of records we’re legally required to retain and don’t use them for purposes unrelated to their retention.
We keep access logs, security incident records and support records for as long as needed to troubleshoot operations, investigate security issues and resolve requests. We don’t treat every data category as something that must be kept indefinitely. Retention requirements may vary depending on service status, unresolved disputes or legal obligations. You can ask which records relate to you and why they’re retained. We’ll handle information that can be deleted and is no longer needed in line with applicable rules.
When a rental ends, node data is handled through a recovery process that erases the disk and reinstalls the system before the machine is assigned to the next tenant. This applies to work data on the node, not order and billing records we retain as required by law. Export your data before your rental ends. This policy doesn’t promise a fixed data-retention period or that erased data can be recovered. Account closure, node recovery and payment record retention are handled separately.
7. Cookies & Language Preferences
The website and console may use cookies or browser storage to maintain sign-in sessions, perform security checks and remember your language preference. Session information lets the console recognize your signed-in account. Language preferences help keep the interface in your chosen language on future visits. Language prompts shouldn’t force you to leave the page you’re viewing for a version in another language; you can choose which language to read.
Website analytics and technical logs help us understand page visits, diagnose errors and improve the experience. They don’t read files on rented nodes. Browser preference records are not project backups and don’t include working directories stored on nodes. To see what a website has stored in your browser, check its cookies and local storage in your browser’s site data settings.
You can clear site data, restrict cookies or use a separate browsing session in your browser settings. If you clear your language preference, the website may not remember your previous choice. If you clear your sign-in session, you’ll need to sign in to the console again. Blocking essential session storage may affect account features. Before leaving a shared device, sign out and clear its website data if needed.
8. Your Rights & Contact
Where applicable law allows, you can request access to personal information relating to you, correction of inaccurate information or deletion of information that’s no longer needed. You can also ask about the purposes of processing, recipient categories and the basis for retention. Where applicable, you may also request that we restrict processing, object to processing or withdraw your consent. Withdrawing consent doesn’t affect processing carried out lawfully before withdrawal. Records we’re legally required to retain may not be deleted immediately.
Email us at support@xcodenode.com, or sign in to the console to submit a ticket. We recommend contacting us from your account email. Include the request type, relevant order number and the category of information you want corrected or deleted. Suggested subject lines: “Privacy request: access,” “Privacy request: correction” or “Privacy request: deletion.” Don’t include passwords, private keys or full card details in your request.
To help prevent us from sharing account information with someone who isn’t authorized, we may need to verify that you own the account or are authorized by your team. We’ll request only what’s necessary to process your request. Once verified, we’ll respond within the timeframe required by applicable law and explain the outcome. If some records can’t be deleted, we’ll explain why we retain them and how they’re handled. We’ll communicate about progress, additional information and the outcome through the same email address or console ticket.