1. Scope
This policy applies to the public pages of cloududp.com,configuration pagesandthe consoleand explains what personal data CloudUDP handles, and why, when processing account registrations, dedicated server orders, order management, billing records, and support tickets.
The information involved varies by activity. Account processes involve the registration email address and account details; ordering and payment involve selected configurations, orders, and payment status; support tickets involve submitted problem descriptions and related communications. See Sections 2 and 3 for details.
This policy distinguishes platform business records from data on rented servers. Accounts, orders, and support tickets in the console are part of the platform service. Customers manage the operating systems, applications, and business data installed on their servers; see Section 7 for details.
2. Information Collected
Registration email and account details.When an account is registered, accessed, or managed, the platform processes the registration email address and submitted account details to identify the account, verify identity, and associate services with it. Submitted details should reflect actual account use.
Order and billing records.Records created during configuration and purchase include the selected server model, memory tier, additional drives, bandwidth, IPv4, operating system, billing period, and the corresponding order, invoice, and payment status. These records confirm what was purchased, support billing checks, and help manage subscribed services.
Support ticket content and console login records.The platform processes problem descriptions, server identifiers, necessary error details, and replies submitted through support tickets. Console login records are also processed to help investigate account security issues. Tickets should focus on the specific issue and exclude unrelated personal information, complete business datasets, or login passwords.
3. How Information Is Used
Provisioning and managing servers.Account information links orders to the relevant account. The configuration in each order is used to provide dedicated server services and display server status and service details in the console. Related records also help verify subsequent configuration or service requests.
Billing, invoices, and support tickets.Order and billing records are used to calculate and verify service charges, record payment status, and provide invoice details. Support ticket content helps clarify issues, verify related orders, resolve technical or billing matters, and retain the context of communications about the same issue.
Protecting account security.Registration email addresses, identity verification information, and console login records are used to verify logins and identify and investigate account access issues. For requests to view or correct account details, the platform verifies the request's connection to the relevant account to avoid disclosing account records to unrelated parties.
4. Payment Information
All orders are billed in US dollars (USD). Available payment methods are shown on the configuration page before payment is confirmed. Payment is processed using the selected method; no payment channel is specified in advance on public pages.
During payment, the site records only the order and payment status. This information links payment results to the relevant order, supports invoice checks, and helps progress service delivery. The order configuration and payment result together verify what was purchased; opening a payment page alone does not confirm that payment is complete.
For payment status or invoice queries, submit the relevant order ID and a description of the issue through a console support ticket. Do not include payment passwords or payment details unrelated to the request.
5. Cookies & Local Storage
Cookies are small pieces of data saved by a browser and used with relevant requests. Local storage lets a browser save site settings on the current device. The site uses these technologies to maintain login status and remember the selected page language.
Login status supports account identification and uninterrupted activity in the console. Language preferences preserve the selected language for future visits. Language settings are not account details and do not change a server's configuration or operating system language.
Browser settings generally allow these items to be viewed, cleared, or restricted. Clearing login-related data may require signing in again to access the console; clearing language preferences may require selecting a page language again. On shared devices, sign out after completing account activity.
6. Information Sharing
CloudUDP does not sell personal information. Information relevant to a specific matter is shared only as needed to complete payment, provide services, or meet legal requirements. A service operation does not constitute blanket authorization to disclose all account details.
For payment, relevant information links orders to payment results. To provide services, relevant information is used to verify orders, handle service matters, or resolve support tickets. The information provided is limited to what is relevant to the specific purpose, rather than all records in an account.
Requests to provide information under legal requirements are handled in accordance with the laws of the jurisdiction where the platform operator is based. Any dispute related to this policy will be handled by a court with jurisdiction in that jurisdiction.
7. Data on Servers
During the rental period, customers manage the operating systems, applications, business accounts, and data on their servers. Platform order, payment status, and support ticket records do not back up data on servers. Customers are also responsible for operating system configuration and updates, as well as application security.
The standard configuration includes two directly attached 1TB NVMe drives, with no hardware RAID. The drives are separate; this does not mean mirroring or other redundancy is in place. For disk redundancy, configure software RAID or a ZFS mirror according to business requirements, and arrange off-site backups separately.
Before reinstalling an operating system, changing storage, or taking any other action that could affect data, confirm that backups are complete and recoverable. When requesting troubleshooting through a support ticket, provide only the necessary server identifiers and exact error messages. Avoid submitting entire databases, keys, or business user records.
8. Access, Corrections & Policy Updates
To access account-related information, verify order records, or correct account details, sign in to the console and submit a support ticket. Specify the type of information, the relevant record, and the requested action. For order-related requests, include the order ID to help locate the record.
To protect account information, the platform verifies that access or correction requests are linked to the relevant account. If console access is unavailable, email support@cloududp.com to describe the account access issue. Do not include account passwords, server passwords, or verification codes in the email.
Updates to this policy will be published on this page with the update date. Changes to the scope or process of information handling will be explained in the revised policy. Questions about access, corrections, or the policy can be submitted through a console support ticket.