1. Scope
This policy applies to the public pages on amdssh.com, the configuration page and the console. It explains what information is involved in account registration, configuration orders, payment records and support ticket handling, and how that information is used. Browsing service information and signing in to an account are separate processes. Questions about an account, order or server should be checked against the relevant account records.
This policy distinguishes platform service records from business data stored on a dedicated server. Account details, configuration selections, orders, billing records and support tickets are used to provide the service. Customers manage the operating systems, applications, files and databases on their servers. This policy's explanation of account management does not constitute a backup commitment for data stored on a server.
2. Information collected
When an account is registered or used, the information involved includes the email address and account details provided. The email address is used to identify the account, support verification processes and enable account-related communication. Account details should be kept accurate, especially the email address used to sign in and receive account notifications. To access or correct account details, a support ticket can be submitted through the console.
Configuration and order records include the selected server model, memory tier, drives, bandwidth, IPv4 address, operating system and billing period, along with the status of the relevant order. Billing records link orders with payment results, so the servers, orders and completed payments shown in the account can be checked against one another.
Support tickets may include a description of the issue, the related server or order, and any error details provided. For troubleshooting, relevant connection details, the steps that led to the issue and error text may be included. Before submitting a ticket, unrelated personal information, full passwords, keys and business data should be removed.
3. How information is used
Account details and order configurations are used to identify the service, confirm the selected configuration, provision and deliver servers, and show the corresponding service records in the console. Order and billing records are used to calculate amounts due, verify payment results and issue bills. A support ticket description does not replace the actual order configuration.
Support ticket information is used to understand an issue, check the related service and handle technical or billing matters. Providing the server, order and error details directly related to an issue can reduce follow-up questions. Issues involving different orders should identify each relevant order to avoid mixing records for other servers into the same request.
Account verification and session information are used to maintain sign-in status, identify account activity and protect account security. Requests to access or correct account details require verification of the request's connection to the account. Service descriptions on public pages alone cannot confirm account ownership.
4. Payment information
Payments are made using the methods listed on the configuration page before payment is confirmed, and are settled in US dollars (USD). Available payment methods are those shown on the configuration page. Any information required during payment depends on the requirements presented by the selected method at the time of payment.
AMDSSH retains service-related order and billing records to link configurations, verify payment results and handle billing questions. To ask about a payment, the relevant order and issue should be identified in a support ticket in the console. Sensitive payment credentials should not be pasted into public areas or unrelated tickets.
The server configuration, billing period and amount due should be checked before payment. After payment, account-specific records and questions can be handled through the account's orders, billing records and support tickets. Public pages do not display account-specific payment records.
5. Data on servers
Customers install, configure and manage the operating systems, applications, databases, logs and other business data on their dedicated servers. System account permissions, access controls, password changes and business data handling should be planned for the actual workload. Account management in the console is separate from system administration on a server.
The two included NVMe drives are each directly connected, with no hardware RAID. Customers are responsible for data redundancy and backups. Software RAID, ZFS mirroring and off-site backups are part of system and data planning; the presence of two drives does not mean that mirroring or backups are already in place.
When submitting a support ticket, provide the error text and context needed to locate the issue rather than uploading a full database, business files or connection keys. If an issue involves data on a server, the troubleshooting scope should be made clear, and information unrelated to the purpose of the request should be excluded.
6. Cookies and sessions
The console uses session cookies to maintain sign-in status and associate subsequent account activity with the signed-in account. Sessions provide access to the servers, orders, billing records and support tickets associated with an account. Session information should not be copied to give another person access to an account.
Browser restrictions or cookie clearing may affect sign-in status. After accessing the console on a shared device, the account should be signed out and any saved sign-in details in the browser should be handled appropriately. Session information, passwords and verification codes should not be included in support tickets or emails as ordinary issue details.
7. Sharing and disclosure
AMDSSH does not sell account information. Only information directly relevant to the applicable purpose is provided when required by law or needed to complete a payment. Full account details, support tickets and business data stored on servers are not provided as part of payment information.
Information is handled in accordance with the laws of the jurisdiction where the platform operator is based when required by law. Disputes related to this policy are handled by the competent courts in that jurisdiction. Account and order facts should still be checked against the relevant records.
Before submitting a support ticket or sending an email, check for account details belonging to other people, unrelated order information or sensitive business data. Include only the context needed to explain the issue rather than attaching complete data files in place of a specific description.
8. Access, corrections and policy updates
Requests to access or correct account information can be made through a support ticket after signing in to the console. The request should identify the information to be checked and the requested correction. If an order or bill is involved, the relevant record should be identified. Information can be processed only when account ownership and the relevant records can be verified.
Questions about this policy can also be sent to support@amdssh.com. Email is suitable for general policy questions. For requests involving account-specific records, the preferred channel is a support ticket in the console. Passwords, verification codes and keys should not be included in emails or support tickets.
Updates to this policy will be published on this page as a new version. When reviewing it, check the version label and the full text, especially the information about account, order, payment and support ticket processes. Questions about specific records can be submitted through a support ticket in the console; summaries on other pages do not replace the full explanation in this policy.