1. Scope
This policy applies to the xcodenet.com website, the XcodeNet console, and data processing related to ordering, provisioning, renewing and billing for Cloud Mac services, as well as support. Whether you are browsing plans or renting a dedicated physical node, this policy explains how your information is handled.
We distinguish between two types of data: account, order and security records needed to operate our services, and projects, tools, build artifacts and other files you store on your Cloud Mac. Renting a dedicated physical server does not give us ownership of the files on it, nor does it automatically make them part of a platform backup.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Any dispute requiring judicial resolution will be handled by a court with jurisdiction in that jurisdiction. We will update this page when the policy changes. We will notify you through the website or console of material changes affecting data use or your rights.
2. Information We Collect
When you create and manage an account, we process your account email and the verification, login and security records needed to operate it. When you place an order, we process the selected model, node region, rental term, add-ons, amount, payment status and renewal records to identify your service, provision the node and reconcile billing. If you contact us by ticket or email, your description of the issue and any attachments you choose to provide become part of our support records.
We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all payments settled in USD. Stripe processes card details; we do not store full card numbers. For USDT-TRC20, we record only the on-chain transaction hash to match the payment to your order and verify its status. Do not send card security codes, private keys or seed phrases by support email or ticket.
To detect unusual access and troubleshoot connection issues, the service may record request times, source IP addresses, browser or client details, and operation results. We process these records only as needed for the relevant function. For general presales questions, we do not ask you to provide project source code, a full disk image or identity documents unrelated to your request.
3. Data on Your Cloud Mac
Projects, documents and build artifacts on your dedicated physical server belong to you, or are used by you under the relevant licence. You choose which development tools to install, which files to store and how to manage team access. Grant access only to collaborators who need it, and manage your own SSH keys, system passwords and software credentials.
Our operations staff do not proactively browse your projects or business files. If troubleshooting requires access to the system or files, we will work only within the scope of a ticket you have authorised. Your authorisation should specify the target node, permitted actions and data that may be accessed. You can ask us to explain the troubleshooting steps before deciding whether to grant access.
Before sending diagnostic materials, remove unrelated personal information, access tokens and signing keys. If a screenshot or log already contains sensitive content, point it out in the same ticket and ask us to address it. Support assistance does not replace your own backup plan, and platform provisioning records are not backups of files on your node.
4. How We Use Data
Provisioning and renewals: We match payment status to your order, assign the selected physical node, provide connection credentials in the console, and manage the rental term and renewals. Billing: We record charges, verify payment results, and provide relevant order and billing records. These functions may not be possible without the necessary account or order information.
Security and troubleshooting: We check for unusual logins, detect abuse, protect account access and investigate issues using the time and node details you provide. Service notifications verify your account, report order changes, remind you when a rental is nearing expiry and share important updates directly related to the services you use.
We do not use project files on your node as advertising material, and we do not require you to publish source code to get support. We process and share information only as needed to complete payment, operate the infrastructure, provide support you have authorised or meet applicable legal requirements. Do not include personal information unrelated to the service in tickets or diagnostic attachments.
5. Storage and Location
Choose from six node locations: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, the US East Coast and the US West Coast. Files stored on your Cloud Mac's local disk or selected external expansion drive are located in the region of that physical node. When ordering, choose a node based on your data location requirements, not just the remote access experience.
The location of your node is not necessarily the location where platform administration records are processed. Account, order, payment status, security and support records are handled by the website, console and related services. Choosing a node does not mean all these administrative records are restricted to that node's region.
Moving to a node in another region involves a new destination. You may also create additional data flows by syncing files to team storage, downloading them locally or uploading attachments in a support ticket. If your project has specific requirements for processing locations, access or cross-region transfers, check with us by email or console ticket before uploading restricted data.
6. Expiry and Deletion
Export your source code, build artifacts, configuration files and other important data before your rental ends. Check the console information for your order or get written confirmation through a ticket for any retention period, applicable deletion date and recovery conditions. This policy does not set a standard number of days without confirmation, and data recovery after expiry is not included by default.
After a node is deprovisioned, the process includes revoking the original access permissions, wiping the disk or resetting the system, and checking the environment before it is used for another service. The actual scope depends on the node and any additional storage. If you use an external expansion drive, mention it in your deletion request so it is not overlooked when checking the system disk.
Deleting node files and deleting account records are separate actions. We may need to retain certain records for billing reconciliation, security investigations or applicable legal requirements. You can ask why information is retained and check its processing status. If we cannot delete some information yet, we will explain why and what is affected. Before requesting deletion, save any billing or support records you still need.
7. Cookies and Analytics
Essential cookies or similar local storage keep your session active, verify requests and save necessary interface preferences, such as your language choice. They support account security and normal site operation; they are not visit analytics. You can clear or restrict them in your browser, but clearing your session will usually require you to sign in again.
Anonymous analytics help us understand overall page visits and feature usage, such as whether a guide was read or the booking flow was used. Analytics and login verification serve different purposes. Analytics should not include system passwords, connection credentials, sensitive payment information or files stored on your node; aggregated visit data is not used to identify individual users publicly.
You can manage cookies, website data and related permissions in your browser settings. To check your current analytics settings or make a request about analytics data, contact our support email. Restricting analytics is not a reason to withhold general information, but disabling essential session storage may affect console sign-in and order management.
8. Your Rights and Contact
You can ask to access information we process about you, correct inaccurate records, delete data that is no longer needed, or learn the purpose and scope of specific processing. If processing is based on your consent or ticket authorisation, you can also ask to withdraw or limit that authorisation. We will assess completed processing and records that still need to be retained separately.
If you have an account, sign in to theconsole and submit a ticket. If you cannot sign in or do not have an account, email us at support@xcodenet.com. State the type of request, your account email, the relevant order or node, and the data you want us to address. Do not include passwords, keys or full card details.
To avoid disclosing data to someone without access rights, we may ask you to verify your identity through your account email or the console. Before acting, we will check the scope of your request, any active services and applicable retention obligations. If we cannot carry out your request directly, we will explain why and suggest next steps. You can follow up on your existing email or ticket for updates; there is no need to resubmit sensitive materials publicly.