1. Scope
This policy applies to the public pages at amdmetal.com, dedicated server configuration pages, the DGX Spark order page and the console. It explains how AmdMetal handles information in connection with account use, order processing, server service management and support requests.
Public product information and service records within an account serve different purposes. Browsing a product page does not place an order. Account details, payment records and support requests are generated during their respective processes. This policy describes each information source separately and distinguishes console records from business data stored on servers.
This policy and the Terms of Service together describe the respective responsibilities involved in using the services. Questions about information handling may be raised through the contact channels on this page. Requirements for using rented services and billing terms are set out in the relevant order and Terms of Service.
2. Information collected
Account information includes the registered email address and details submitted during account processes. The email address is used to identify the account, verify sign-ins and send service notifications. Account details should be reviewed and updated in the console when they change, to help ensure delivery messages and billing notices reach the intended recipient.
Transaction records include the selected service and configuration, order amount, billing cycle, billing records and payment status. These records link a payment to the relevant service and support later queries and billing checks.
Support request information includes the issue description, any relevant order number or server identifier, and any screenshots, logs or other materials attached voluntarily. Before submitting a request, unrelated personal information, business data, passwords and keys should be redacted. Only the information needed to investigate the issue should be included.
3. Payment information
Payments are processed using the methods listed on the configuration page before payment is confirmed, and are settled in US dollars. Available options are those shown on the page at the time of payment. This policy does not specify any particular payment channel.
AmdMetal retains the order amount and payment status to determine whether an order has been paid, display billing records and handle payment-related support requests. Payment details should be submitted through the selected payment method's process. Complete payment credentials should not be sent through a standard support request or email.
For questions about payment status, the relevant order number and the message displayed on the page may be submitted through the console. Screenshots used for verification should have unrelated sensitive fields redacted, and should not include payment details alongside service-related issues.
4. How information is used
AmdMetal uses account and order records to provision and manage server services, linking confirmed orders to the relevant account, server and service status. Configuration and billing information is used to verify the services ordered; temporary descriptions in support requests do not replace order records.
The registered email address is used to send service delivery messages and billing notices. Delivery information directs account holders to the console to view server details. Sign-in credentials are not displayed on public product pages.
Support request details are used to understand reported issues, check service records and communicate outcomes. Server-related requests should include the server identifier and error details. Billing questions should include the order number so that the information provided can be matched to the matter being reviewed.
5. Data on servers
Customers are responsible for managing business files, databases, application configuration and backups stored on their servers. AmdMetal does not read customer business data. AmdMetal is responsible for the hardware and network; customers are responsible for system configuration, applications and data backups.
Each NVMe drive in a dedicated server is directly attached. Hardware RAID is not provided, and servers are not delivered with a preconfigured RAID-1 array. Data redundancy should be configured to suit business requirements using software RAID, ZFS mirroring or another solution, alongside off-site backups. Disk mirroring is not a substitute for independent backups.
Before requesting a reinstallation or an operation that may affect storage, backup completeness and recoverability should be verified. For troubleshooting, redacted logs and relevant error details may be provided. Complete business data and access keys should not be attached to routine support requests.
6. DGX Spark data
Data stored on a DGX Spark is erased when the service expires and must be exported beforehand. Service terms are described in the AmdMetal DGX Spark overview.
7. Cookies and logs
Cookies maintain sign-in status so the console can recognise an active session across consecutive actions. Account holders should manage signed-in browsers carefully and sign out after using a shared device.
Logs generated during service processes support security audits and troubleshooting, such as checking account actions and the execution of related requests. Logs and support request details help investigate service issues; they do not replace the management and backup of business data stored on servers.
Cookies can be managed or cleared in the browser. Clearing sign-in data may end the current session and require another sign-in. Questions about sign-in status may be raised through a console support request or by email using the address on this page.
8. Contact and updates
Privacy questions should preferably be submitted through an AmdMetal console support request, so the request can be associated with the relevant account and order. If account access is unavailable, email support@amdmetal.com with the account email address, the scope of the issue and the records to be reviewed.
Requests to review or correct account details should include enough information to identify the relevant records. Passwords, verification codes and private keys should not be sent by email. Exports and backups of business data must be handled within the server service and should not be sent through public pages.
Policy updates are published on this page. The relevant sections should be reviewed before using an account or placing an order. This page does not promise a fixed data retention period or a standard number of days before deletion.
This policy is governed by the laws of the jurisdiction in which the platform operator is based. Any disputes will be handled by the courts with jurisdiction in that jurisdiction.