1. Scope
This policy applies to the public pages, configuration pages, DGX Spark order page and console on tcpnode.com. It covers information handled when browsing, using an account, placing and paying for an order, and submitting support tickets.
It covers two categories of information: account, order, billing and communications records used to provide the service; and code, model weights, logs and other files stored on a rented machine by the customer. Their respective purposes and management responsibilities are explained below.
This policy is governed by the laws of the jurisdiction in which the platform operator is established. Any dispute relating to this policy will be handled by a court with jurisdiction in that jurisdiction.
2. Information collected
Account information includes the email address used to register and sign in. It is used to identify the account, send verification codes and notify the account holder about order delivery. The address should remain valid and be managed by the account holder.
Transaction information includes the product and configuration selected for an order, the rental term, the amount due and billing records. These records link payment outcomes to specific orders and display related services and completed payments in the console.
Support ticket information includes the issue description, relevant order number and any error output or attachments provided. Before submission, remove personal information unrelated to troubleshooting, passwords, private keys and other sensitive credentials.
3. How information is used
TcpNode uses account and order information to provision and deliver machines, send delivery emails and associate each service with the relevant account. After delivery, connection details and login credentials are available in the machine details section of the console.
Order and billing records are used to verify configurations, amounts and payment outcomes, and to support related billing and renewal processes. Billing terms vary by product; orders from the two product lines are handled separately.
Support ticket contents are used to investigate reported issues, identify the machine and actions involved, and keep a record of how the issue was handled. Issue descriptions should focus on the problem and exclude data copies unrelated to resolving it.
4. Payment information
Orders are settled in USD. Available payment methods are those shown on the configuration page.
TcpNode does not store complete payment card details. The site uses payment outcomes and billing records associated with an order to confirm whether it has been paid. Billing records in the console are not complete payment credentials.
Do not resubmit payment information through a support ticket or email. If the payment outcome does not match the order status, provide the order number and a description of the issue through a console support ticket for review.
5. Machine data and DGX Spark expiry
Customers are responsible for managing and backing up code, model weights, datasets and logs stored on a rented DGX Spark machine. TcpNode does not access this content. Service delivery and support ticket records are not backups of data stored on the machine.
Data is erased when a DGX Spark rental expires. Files, experiment results and environment configurations that need to be retained should be transferred before expiry. A rented machine should not be the sole storage location for data.
Hard reboots and operating system reinstalls for DGX Spark are handled through console support tickets. Before requesting a reinstall, confirm that all required data has been transferred. Reinstallation does not replace data migration or backup.
6. Cookies and login status
Cookies and local storage used for login and language preferences serve only those functions: keeping the account signed in and remembering the selected page language. Language preferences do not change order configurations or the billing currency.
Clearing the relevant browser data may require signing in again or selecting a language again. On a shared device, sign out when finished to prevent subsequent users from accessing order and support ticket information in the console.
7. Sharing information
TcpNode does not share account, order, billing or support ticket information with third parties except as needed to fulfil orders or meet legal requirements. Information is handled only to the extent necessary to provide the relevant service.
Payments are processed using the methods listed on the configuration page. The processing involved is separate from the order and billing records stored by the site. Complete payment card details are not stored by the site.
Information is handled in response to legal requirements in accordance with the laws and requirements of the jurisdiction in which the platform operator is established. This policy makes no commitments about data storage locations or fixed retention periods beyond the actual service processes.
8. Access and corrections
Requests to access, correct or delete account information can be submitted as a support ticket through the signed-in TcpNode console. Include the type of request, the information concerned and any relevant order number so the request can be matched to the account and service records.
Deleting an account is separate from managing files on a machine. An account deletion request does not replace transferring data before expiry or change the billing records for completed transactions. The handling of relevant records remains subject to order fulfilment and legal requirements.
If console access is unavailable, contact support@tcpnode.com about the account access issue. Do not include passwords, private keys or complete payment card details in the email.
9. AMD dedicated server data
AMD dedicated server orders also rely on account email addresses, order configurations, billing records and support ticket contents to provide the service. The monthly, quarterly, semi-annual and annual billing periods, as well as additional drives, bandwidth, extra IPv4 addresses and operating system options, are recorded as part of the product line's order configuration.
Customers manage applications, files, accounts and backups on systems such as Windows Server or Proxmox VE. TcpNode does not access data stored on the machine. Dedicated server NVMe storage is directly attached and has no hardware RAID. Software RAID, ZFS mirroring and off-site backups must be arranged separately; data redundancy is not a substitute for backups.
Hardware and network issues for dedicated servers are handled through console support tickets. The pricing catalogue and configuration page are available at the TcpNode AMD rental catalogue and the TcpNode dedicated server configuration page. These pages do not change the information-handling purposes set out in this policy.