Privacy Policy

How email addresses, order fields and machine identifiers are stored, and to whom they are shown.

  1. Scope

    This policy sets out what ovncloud.com handles during registration, ordering, payment, delivery and console use. The purpose is limited to identifying an account, calculating the amount due, delivering a paid machine, and answering tickets from that account.

    Records are shown only to a signed-in session of the account they belong to, and never written into another account's console. Personal data is not sold, and email addresses, orders and access passwords are not passed to directories unrelated to the delivery at hand.

  2. Email address

    The email address identifies the account. It is used to tell whether an address already has an account, to send verification codes, and to send notices tied to an order. One address corresponds to one account.

    Verification codes are separated by purpose: sign-in, registration, password reset. The message body holds the code alone, with no clickable link and no account password. When the lookup on an address fails, that failure is not treated as a new user and no account is created.

    Once signed in, the top bar shows nothing but that address. Its menu holds the console entrance and the sign-out action. After signing out, the console no longer presents orders or passwords under that address.

  3. Order contents

    An order stores the memory tier, the number of added disks, the bandwidth step, the count of extra IPv4 addresses, the system, the Windows language where Windows was chosen, the billing term and the payment state. These fields calculate the monthly rent and the amount due, and after payment they produce the machine record in the console.

    The machine list accepts paid master orders only. A list title is written as model plus memory tier, for example AMD EPYC 7543P ยท 128GB. Added disks, bandwidth, extra addresses and the system stay in the order detail rather than the title.

    Unpaid orders and subordinate orders do not enter the machine list, so the console never shows an unpaid configuration as a connectable machine.

  4. Machine identifiers

    Identifiers tied to a machine include the order number, expiry date, facility, addresses and access password. The facility is recorded as Tokyo, Japan. There may be more than one address; addresses are split apart and de-duplicated on storage, and their number stays within the total of the included address and the extra IPv4 ceiling for that order.

    While the status is not connectable yet, the detail view keeps only the short title, status, order number, facility and expiry date. Address, SSH, RDP and password are all withheld.

    Once connectable, those fields appear only to the signed-in account that owns them. SSH or RDP uses the first address in the list. The password is masked with dots by default, and revealing or copying it happens inside that account's session. Addresses copy one line at a time, or every line at once when there is more than one.

  5. Tickets

    A ticket stores its subject, description, replies and closed state. The content serves only the power, system or address matter raised by that same account, and is not written into another account's console.

    Replies and later notes are appended to the original ticket. Filing and reading the ticket list both require a signed-in account. Ticket text does not change the memory, disks, bandwidth, addresses, system or term recorded in an order.

  6. Payment records

    At checkout the payment method is chosen from the gateways the interface returns at that moment, and the chosen gateway handles the money. What this site stores is the invoice number, term, amount and payment date, which list the paid records in the console and link back to the matching machine.

    Unpaid invoices are not listed in the console, the console stores no payment-method choice, and no payment starts from the invoice page. Payment details collected by the payment institution on its own pages are not written into machine details here.

  7. Visit statistics

    Matomo records page visits and on-site actions such as opening the configurator, filing a ticket or following an article's configuration link. The statistics describe how pages are used; they do not replace account records and are not used to sell personal data.

    Events carry page and action names. Email addresses, order numbers and access passwords are not written into event names. Page visits are not written into orders, and without a signed-in session a visit is not attached to any address's orders.

  8. Access and correction

    Once signed in, an account can read its own paid machines, paid invoices and tickets in the console. Addresses and passwords appear only after a machine is connectable, and can be copied on that page.

    Changing the email address runs through the sign-in flow again rather than rewriting the address on an order record. Changes to specification or term are made through a new order, while the original keeps the configuration it was paid on, so invoices and machines still match.

    Questions about the scope of these records go to support@ovncloud.com with the account email stated. Such messages are used only to check the orders and tickets under that one account.