1. Service Scope
XcNode provides dedicated Apple Silicon Cloud Mac servers. Each delivered node is assigned to one tenant for the rental period. It is not a virtual machine: the CPU, GPU and unified memory of the same machine are not shared with other tenants through a shared host. The macOS graphical interface and command line may be used for development, builds, testing and other activities permitted under these terms.
The current catalog offers two configurations: Node Core M4, with an M4, 16 GB of memory and a 256 GB SSD; and Node Pro M4, with an M4 Pro, 64 GB of memory and a 2 TB SSD. Both are available in Singapore, Tokyo, Seoul and Hong Kong. Available configurations, add-ons and current capacity are determined by the live information returned in the console and confirmed at checkout.
An order includes access to the selected physical node and the connection details provided in the console order or instance view. Renting a node does not transfer ownership of the device or include separate licenses for third-party software. After delivery, verify the model, memory, storage, location and rental period. If anything differs from your order, keep the order number and open a console support ticket.
2. Billing and Rental Periods
Service is prepaid by the day, week, month or quarter, and all prices and charges are in US dollars (USD). The base rental fee and any add-ons, such as storage expansion or Thunderbolt 5 clustering, are listed separately on the order. Current catalog pricing is shown on thePlanspage. Confirm the amount due, selected billing period and rental start and end dates before checkout.
Billing starts at the rental start time specified in the order. If delivery is still in progress after payment, check the order status; do not assume that payment completion means the node is ready to use. Billing is not automatically paused if you do not sign in, pause tasks, have no builds queued or leave the machine idle. Pausing development work and ending a subscription are different actions. Check the order expiry date and renewal status to see whether service will continue.
Renewals use the period confirmed in the order and the price displayed at the time of renewal. Before changing the model, adding or removing add-ons, or adding a node, confirm how the change will be made, any price difference and the data migration plan. Configuration changes not confirmed in the console or a support ticket are not considered active. If your team rents multiple machines, check each order separately; renewing one node does not renew all of them.
3. Payment Methods
We accept USDT-TRC20 and Visa, Mastercard or Amex card payments processed by Stripe. All orders are charged in US dollars. Available payment gateways are determined by the response from the backend. Use the payment details generated at checkout; do not use an address from an older order or guess payment details for a new one.
For USDT-TRC20 payments, verify the network, receiving address, amount due and payment instructions for that order, and keep the transaction hash. A transaction submitted on-chain and payment confirmed on the order are separate statuses; check the payment status in the console. For card payments, complete any verification required on the payment page. If it shows a failure or the result is unclear, check the billing status before trying again to avoid duplicate charges.
For payment issues, provide your order number, payment method, payment time and transaction ID. Contact us through a console support ticket or at support@xcodenode.com . Do not send your full card number, card security code, account password or private key. Stripe processes card details; the platform does not store card numbers. See ourPrivacy Policyfor details on data processing.
4. Renewals, Expiry and Data Retention
To keep using a node, renew before it expires and confirm in the console that the new rental period is active. Starting a payment, sending a renewal email or opening a support ticket does not by itself complete a renewal. Plan your work around the expiry time shown in the order, and do not rely on a single reminder to decide whether to renew.
Nodes that are not renewed by expiry will be taken out of service; running tasks and remote connections may be interrupted. Data retention after expiry is governed by the period shown for that order or confirmed in a support ticket. These terms do not promise a fixed retention period. If no retention period has been agreed, do not treat an expired node as storage you can continue to access.
After the retention period ends, the disk is erased and the system is reinstalled before the node is assigned to another tenant. The platform cannot be relied on to recover projects, build artifacts, certificates or caches after erasure. Export any data you need before expiry and verify that your backups can be restored. Make a separate backup before renewing or migrating configurations, too. Before requesting recovery, confirm whether the node can still be renewed, whether the data remains available and what new order arrangements apply.
5. Refunds
As a general rule, fees for a billing period that has started are non-refundable. This applies to requests resulting from project cancellations, reduced workloads, idle nodes or unused time. Stopping tasks early does not automatically trigger a refund or cancel a confirmed billing period.
This general rule does not apply to delivery failures. If a node cannot be delivered as ordered, its delivered configuration differs from the confirmed order, or it cannot be used after delivery and requires action from the platform, open a support ticket promptly. We will review the order, delivery records and reported issue, then work with you to determine whether to repair the issue, provide a replacement or issue a refund. You are not required to treat an undelivered service as properly provided.
Refund requests should include the order number, a description of the issue, when it was first noticed and any records that can verify it. The refund scope, amount and method depend on the outcome of our review. Check the payment provider’s processing status separately from the order status. Uptime credits for availability below the stated target are handled under Section 7. Keep all handling of the same incident in one support ticket to avoid duplicate or conflicting requests.
6. Acceptable Use
You must not use a node for mining, sending spam, attacking other systems, distributing unlawful content, or conducting unauthorized scans, intrusions, credential theft or malware distribution. Testing and security research must be limited to systems you are authorized to access and the expressly authorized scope. Renting a dedicated machine does not expand the systems you may test or your network access permissions.
You are responsible for securing your console account, SSH keys, connection credentials and project secrets. If your team shares a node under one tenant, you must manage member permissions and keys, and coordinate use of the graphical desktop and build tasks. Do not publicly share connection credentials. When a team member leaves a project, revoke their access promptly and review credentials used by automated tasks.
Report unusual account activity, suspected credential exposure or prohibited activity promptly through a console support ticket or the support email. If conduct may threaten other systems or platform security, or violate applicable law, the platform may impose necessary access restrictions or suspend service. Where security and applicable law permit, we will explain the reason and any required steps. You must cooperate with any investigation and may not continue restricted activity through a new order.
7. Uptime and Service Credits
Nodes operate 365 days a year. Service availability is measured against the monthly uptime target of 99.9% published on theSecuritypage. This figure is a service target and the basis for determining credits; it does not guarantee build times, the performance of any individual network route or the response speed of third-party services.
If verified monthly availability falls below 99.9%, the rental period will be extended in proportion to the downtime. Compensation is provided as service time, not an automatic cash refund. The assessment distinguishes physical node outages from issues with the user’s local network, inaccessibility caused by user changes to system or network settings, and third-party service disruptions. Downtime caused by force majeure or the user is not included in the platform’s responsibility.
To request a review, submit the order number, affected node, outage start and end times, and connection test results through the console. Include the time zone used for your records. We will compare node operating logs with the information you provide, confirm the affected period, and record any credit and adjusted expiry date in the support ticket or order. After the node is restored, check task and connection status so that application-level failures are not counted as continued node downtime.
8. Liability and Disclaimers
The platform is responsible for delivering the dedicated physical node specified in the order, addressing platform-side issues, and handling billing reviews, data disposition and applicable credits under these terms. You are responsible for project content, third-party software licenses, development credentials, access permissions, task configuration and independent backups. Dedicated resources do not guarantee that an application task will succeed; build results, model performance and third-party release reviews depend on their respective inputs and rules.
The responsible party bears the consequences of user-deleted files, incorrectly configured networks, exposed credentials, use of third-party systems beyond authorized scope, or failure to back up data before expiry. If force majeure or an external service issue beyond a party’s control affects use, both parties should take reasonable steps in light of the actual impact, preserve verifiable records and distinguish platform-side causes from external ones.
Nothing in these terms excludes liability that cannot be limited or waived under applicable law. Nor does the platform use the statement that “users are responsible for backups” to avoid responsibility for its own attributable conduct. Any dispute over losses will be assessed in light of the order, cause of the issue, direct impact and steps taken by both parties to mitigate the loss. No unspecified compensation multiplier or monetary cap is assumed.
9. Changes and Disputes
The platform may update these terms to reflect changes to the service, billing process or compliance requirements. We will publish an explanation of changes and their effective date on the public site or in the console. Reasonable notice will be given for changes that materially affect user rights or obligations. The terms applicable to a confirmed order will be determined with reference to the terms accepted when placing the order and any applicable notice. A silent update to a webpage will not retroactively change terms for services already provided.
If you have a concern about an order, bill, data disposition or interpretation of these terms, first contact us through aconsole support ticketor support@xcodenode.com and provide the order number, the matter in dispute, supporting records and your preferred resolution. Both parties should first try to resolve the issue through discussion and keep a record of the outcome. For contact details and guidance on what to submit, see ourContactpage.
These terms are governed by the laws of the jurisdiction in which the platform operator is established. Any dispute that cannot be resolved through discussion will be submitted to a court with jurisdiction in that jurisdiction. Any mandatory legal protections for users will apply. If any provision is found invalid, the remaining provisions will continue to apply to the extent permitted by law.