Legal

Privacy Policy: How Data Is Used to Provide Services

This policy explains how account, order, billing and support ticket information is used to provide services, and clarifies the distinction between account records and data stored on servers.

Accounts & orders Billing & support

Contents

  1. 1. Scope
  2. 2. Information collected
  3. 3. How information is used
  4. 4. Payment information
  5. 5. Cookies & local storage
  6. 6. Sharing & disclosure
  7. 7. Server data
  8. 8. Access, correction & deletion
Open account portal

1. Scope

This policy applies to the public pages on cloudsfp.com, dedicated server configuration pages and the account portal. It covers information handled through existing processes such as browsing service details, registering and signing in, placing orders, viewing bills and submitting support tickets.

This policy distinguishes platform service records from data stored on a rented server. Account, configuration, billing and support ticket records are used to deliver and manage services. The customer is responsible for the operating system, applications, business files and backups stored on the server; see Section 7 for details.

Any legal matters relating to this policy are governed by the laws of the jurisdiction in which the platform operator is established. Disputes will be handled by the competent courts in that jurisdiction.

2. Information collected

Account information includes the registration email address, account details, and information needed for sign-in and verification. The registration email is used to identify and verify the account and to send notices about subscribed services. Requests to update account details can be submitted through a support ticket in the account portal.

Order and billing information includes the selected server, memory tier, storage options, bandwidth, IPv4, operating system, billing period, amount due, order status and payment records. These records are used to identify the relevant order, reconcile payments and manage subscribed services.

Support ticket information includes the issue description, associated server ID, error details, and any attachments or logs voluntarily provided. Submitted materials should be limited to what is needed to investigate the issue. Passwords, private keys, verification codes, complete payment details and unrelated business data should not be included in support tickets.

3. How information is used

Account and order information is used to provision and deliver servers, associate the selected configuration with the relevant account, and display order and server details in the account portal. Delivery notices are sent to the account email address. Connection details and credentials are available in the account portal after delivery.

Order amounts, billing periods and payment records are used for billing, reconciliation and billing notices. Support ticket content is used to confirm service requests, investigate hardware or network issues, record how they are handled and continue communication about the same request.

Information is used to verify accounts, deliver services, process billing and provide support. If a support ticket does not include enough detail to identify an issue, additional information directly related to the issue may be requested, such as a server ID, error message or description of the steps taken.

4. Payment information

All orders are settled in US dollars. Available payment methods are listed on the configuration page before payment is confirmed. Payment information is handled by the payment service selected for the transaction. The site does not store full card numbers, and no specific payment method is named on public pages in advance.

Payment results and billing records associated with an order are used to reconcile its settlement status. For details about information collected directly by a payment service during a transaction, refer to that service’s own documentation.

Payment reconciliation requests should be submitted through a support ticket in the account portal, with the relevant order and a description of the issue. Full card numbers, payment verification codes and other credentials that could be used to make a payment should not be included in tickets or emails.

5. Cookies and local storage

Cookies or browser local storage are used to support sign-in state and language preferences. Sign-in data helps identify the current account on restricted pages; language preferences retain the selected page language.

Browser settings can be used to clear cookies and local storage. After sign-in data is cleared, signing in again may be required to access the account portal. Clearing language preferences may remove the previously selected language.

Accounts should be signed out of shared devices after use. Browser session data and server connection credentials serve different purposes; clearing browser data does not change server passwords or keys.

6. Sharing and disclosure

Personal data is not sold. Information is shared with relevant service providers only when necessary to deliver dedicated server rental services, process payments or meet legal requirements, and only to the extent needed for the specific purpose.

Sharing is limited to the matter at hand. For example, payment processing requires information associated with order settlement, while investigating a service fault requires information related to the server and fault. Unrelated account or business information is not shared to handle a particular request.

Information requests made under applicable law are handled in accordance with the relevant requirements, with disclosure limited to what is necessary. Questions about the use or disclosure of information can be raised through a support ticket in the account portal or by emailing the address listed in Section 8.

7. Data stored on servers

The customer is responsible for the operating system and applications installed on a rented server, as well as the data stored there. The site does not read that content. The site is responsible for the server hardware and network; the customer is responsible for system configuration, accounts and keys, business access permissions, data redundancy and backups.

The two included 1TB NVMe drives are each directly attached, with no hardware RAID. Dedicated hardware does not replace data protection; disk redundancy and independent backups must be arranged separately. A request to delete account details does not include backing up or migrating server data.

Customers should review logs before submitting them for troubleshooting. Logs, screenshots and attachments should be cleared of unrelated personal information, business content and authentication credentials. Materials submitted voluntarily become part of the relevant support ticket and are handled for support purposes.

8. Access, correction and deletion

Requests to access, correct or close an account should be submitted through a support ticket in the account portal. The request should identify the information involved, the action requested and the associated account. Account verification may be required to prevent unauthorised changes.

Deletion and account closure requests are handled in light of outstanding orders, billing reconciliation and applicable legal requirements. Any records that must be retained, along with the status of the request, will be discussed through the support ticket. This policy does not set a uniform deletion period or equate account closure with the immediate removal of all service records.

If account access is unavailable or there are questions about this policy, email support@cloudsfp.com. Emails should briefly identify the account email address and request, without including passwords, private keys or verification codes. Requests to change account details still require the necessary verification.

Submit a data request