1. Scope
This policy applies to cloud Mac rental services provided by XcodeRent Cloud Mac (brand short name: XCRent) on xcoderent.com and through its portal. It covers personal information generated when you browse public pages, create an account, purchase or renew a service, manage a dedicated physical node, or submit a support ticket. The portal and public website are part of the same service, and this policy governs how we handle account- and order-related data.
This policy distinguishes between two types of data: account, billing and support information that we process to provide the service; and source code, build artifacts and other files that you store on your dedicated physical node. Renting the service does not transfer ownership of node files. See Section 4 for details on how we handle them. If you use the service as part of a team, make sure you are authorized to provide team members’ information and upload the relevant files.
This policy explains our data handling practices and does not replace your order terms or the terms of service. The laws of the jurisdiction in which the platform operator is based govern this policy. Any dispute relating to this policy will be handled by a court with jurisdiction in that jurisdiction.
2. Information we collect
Account information mainly consists of the email address you provide and the records needed to sign in, verify your account and keep it secure. We use this information to identify your account, send verification and order-related notifications, and handle account recovery requests. Keep your email address accessible. Do not submit node passwords, SSH private keys or signing credentials as account information.
Billing records include the selected plan, node location, billing period, add-ons, amount in US dollars, payment status and renewal history. We use these records to provision services, reconcile billing, resolve payment issues and meet necessary financial record-keeping obligations. Buying a particular plan does not mean we will ask for team member details unrelated to providing the service.
Support ticket content may include a description of the issue, an order or instance ID, and any logs, screenshots or files you choose to attach. We use these materials to investigate the issue and respond. Before submitting, remove access tokens, certificate passwords, personal information and unnecessary business content from your source code. If an error snippet is enough to explain the issue, there is no need to upload the entire project.
Access logs may include IP addresses, request times, pages accessed, browser or client details, response results and security event records. We use them to secure sign-ins, troubleshoot page and API errors, identify unusual requests and understand service usage. Access logs are separate from node files; we do not access your build project to investigate website requests.
3. Payment data
Services are priced and settled in US dollars (USD). We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. The payment gateways actually available are determined by the response from the backend at checkout. Stripe processes card payments. We do not store full card numbers or card security codes; we retain the payment status, amount and payment reference needed to reconcile orders.
For USDT-TRC20 payments, we record only the transaction hash as on-chain payment evidence, to verify that funds have arrived for the relevant order. Never send support your wallet private key, recovery phrase or other secrets that could be used to control your assets. A transaction hash can be linked to public blockchain records, which cannot be removed by deleting your account on our website.
Payment providers process relevant payment information to complete transactions and carry out necessary security checks. Review the information shown at checkout before submitting payment details. Deleting your account does not reverse completed transactions or remove any obligation to retain necessary financial records under applicable law. See Section 6 for our retention and deletion practices.
4. Data on your node
Each rented instance is a dedicated physical Mac mini, not a virtual machine, and is assigned to a single tenant for the rental period. You own the source code, DerivedData, build artifacts, logs and other files you store on it. Dedicated means that you do not share the same physical machine with other tenants; it does not mean we automatically back up or archive your projects.
Information needed to provision and run a node includes the instance ID, node location, model, rental period and connection settings. We do not use your source code or build artifacts for marketing. If a technical issue requires us to inspect information on your node, we will first confirm the scope of the issue and the actions needed through a support ticket. Where redacted logs are sufficient, we will use them instead.
When your rental ends, we erase the disk on the returned node before provisioning it again. Before the rental ends, export any source code, certificates, caches and build artifacts you want to keep, and verify that your backups are readable. Disk erasure is not a backup service, and a node should not be treated as a way to recover files after your rental ends.
Reinstalling the operating system may also erase files on the node. Check your backups and data migration plans before starting a reinstall or confirming a related action. Changing your account email or deleting website cookies will not remove projects from a physical node. Node data, account information and billing records must be handled separately; do not assume one action applies to all of them.
5. Cookies and analytics
The website and portal may use cookies or local storage to maintain sign-in sessions, remember your language selection and retain necessary interface settings. Session data lets verified users continue accessing their accounts and helps prevent unauthorized actions. If you clear this data, you may need to sign in again, and some preferences may return to their default settings.
We use first-party analytics to record page views and key actions, such as viewing plans, starting checkout or opening support content. This helps us understand what is useful and which flows could be improved. Analytics should not contain node passwords, private keys, signing certificates or project source code. Support tickets and node files are not collected as page analytics.
You can manage or delete cookies and restrict local storage in your browser settings. Restricting essential session data may affect sign-in, checkout or account management. Clearing browser data affects that browser only; it does not delete server-side accounts, orders, support tickets or necessary security records already created.
6. Data retention and deletion requests
We set retention periods based on the purpose of each type of data rather than keeping every record indefinitely. Account information is retained while we provide account services. Billing records are kept for as long as needed to fulfil transaction, financial and dispute-handling obligations. Support materials and access logs are handled for as long as needed for support, security and troubleshooting. Once information is no longer needed for its purpose, we delete it or de-identify it.
You can submit a support ticket through the portal after signing in, or contact support@xcoderent.com from your account email to request access to, correction of or deletion of your personal information. Specify the type of request, the associated account and the data you want us to handle. We may ask you to verify account ownership so that someone else cannot close your account or affect a node you are still using by submitting a deletion request.
If we still need certain records to meet legal obligations, reconcile an unfinished transaction or handle an ongoing dispute, we will explain which data cannot be deleted immediately and why, and restrict its use to the relevant purpose. Make clear whether your request concerns account closure, deletion of support ticket attachments or the return of a node. If an instance is still running, confirm your data export and service termination plans first.
7. Cross-border transfers
The service offers six node locations: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East Coast and the US West Coast. The location you select determines where your project files are stored on a physical node. When you move a project between regions, source code, caches and build artifacts may be transferred from your location to the selected node location.
The location of a node is not the same as the locations where account, billing and support systems process data. Choosing a node does not mean all service records are processed only in that location. We process information only to the extent needed to provide the service, using account access controls and appropriate transfer protections to keep unnecessary project content out of billing and support workflows.
If your team has specific data residency, customer contract or cross-border transfer requirements, contact support@xcoderent.com before placing an order. Tell us the data categories involved, the node location you are considering and any restrictions, and confirm whether the service meets your requirements. Do not rely solely on the remote desktop experience to determine whether data residency is suitable. Before migrating, also review how your project dependencies and build scripts transfer data.
8. Contact and policy updates
For questions about this policy, data access, corrections, deletion or security, email us at support@xcoderent.com or sign in to the portal and submit a support ticket. If you have a rental, include your order or instance ID and the type of issue in your ticket. Do not include node passwords, SSH private keys or complete signing certificates in your email.
We may update this policy as our service processes or applicable requirements change, and will publish updates on this page. We will explain significant changes to the types of data we collect, the purposes for which we use it or how we process it through an appropriate on-site or account notification. Check this page before submitting new personal information or changing how you deploy projects; do not assume that previous practices will remain unchanged.
After submitting a request, make sure your contact email can receive our reply. To make it easier to track, continue in the same email thread or support ticket for the same issue, and include the actions you have already taken and any necessary redacted materials. We will confirm your identity and clarify the scope of your request before letting you know how we will handle it. If we need to retain some records, we will explain the relevant limits.