Where your data comes from, how we use it, and when we delete it

This notice applies to visits to mangovm.com, browsing products and pricing, preparing inquiry emails through the contact page, communicating via support@mangovm.com, and personal data created when you order, manage services, or submit tickets in the console.

When a website button takes you to the console, page visits, account authentication, order linking, and support may form one continuous process. We use necessary identifiers to confirm the relevant account or order, but a normal page visit does not automatically read project files, source code, or work products on a dedicated physical node.

Data you create, import, or process on a dedicated physical node is generally under your control. The platform processes it only as necessary to provide the service, respond to authorized support requests, handle security incidents, or meet applicable legal requirements.

1. Provide and manage services Link accounts, process orders, show service status, deliver connection details, manage rental terms and add-ons, and record necessary billing results.
2. Verify access and authorization Identify login attempts and verify that requests come from the account holder or an authorized user, reducing the risk of unauthorized account use.
3. Process order-linking requests Use the order identifier to verify the model, term, region, payment result, and service status, preventing one account’s information from being disclosed to another.
4. Protect website and service security Detect abnormal requests, abuse, malicious-code distribution, and unauthorized access, while retaining enough technical records to investigate incidents and restore service.
5. Respond to support and improve processes Reproduce issues, record completed steps, coordinate node and billing investigations, and improve documentation and product workflows based on recurring faults.
6. Meet legal obligations Retain necessary transaction and compliance records, respond to legally authorized requests, and handle claims related to the service relationship.

If we plan to use existing information for a purpose materially different from the original context, we first assess compatibility, necessity, and impact. Where separate consent is required, we provide a clear choice rather than bundling consent with non-essential features.

How required and optional fields differ

Required fields support account verification, order linking, billing checks, security controls, or support diagnosis. Optional fields usually add workload context, preferences, or reproduction details. Labels, descriptions, or workflow placement indicate the difference; you may submit the minimum first and let support confirm what else is needed.

Withdrawing consent, declining optional analytics, or leaving optional fields blank does not change a confirmed order’s configuration or rental term. Requests involving account ownership or order records still require enough information for identity verification.

Processors must handle information according to agreed purposes, confidentiality requirements, and security measures, and may not use it independently for unrelated purposes. We assess access controls, incident response, and data-return or deletion arrangements based on the processing, risk, and available information.

If our business structure changes, relevant information is transferred only as necessary for transaction evaluation, service continuity, and legal obligations. Recipients must continue to meet applicable data-protection duties.

MangoVM offers nodes in Singapore, Tokyo, Japan, Seoul, South Korea, and Hong Kong. Your selected node region determines where the dedicated physical node is provided, but does not mean account data, orders, email, tickets, or security logs remain permanently in that region.

To provide website, authentication, order management, communications, security monitoring, and support, information may move between regions or be accessed by processors in the relevant regions. We use measures such as contractual safeguards, access restrictions, transfer protections, log audits, and vendor assessments as required.

If you require regional handling for specific information, email support@mangovm.com before ordering with the data category, business restriction, and target region. The team will confirm what is feasible; node availability is not a permanent regional commitment for all related information.

Once the retention purpose ends, information is deleted, de-identified, or placed in access-restricted archives until any mandatory retention period ends. Deletion may need to cover active systems and rotating backups; before backups are overwritten, the data is not returned to routine business use.

Before service expiry, migrate project files, logs, build artifacts, and other data you need to keep from the dedicated physical node. Deleting account records does not replace node-data migration or automatically cancel incomplete orders, disputes, or legal obligations.

1. 1

   Define the request scope

   State the right you wish to exercise, related account email, order identifier, information category, and approximate timeframe. Do not send passwords, private keys, or signing certificates by email.

2. 2

   Complete identity verification

   To prevent others from obtaining or deleting your information, we use login status, control of the email address, order links, and request risk for necessary verification. We do not ask for unrelated information.

3. 3

   Assess scope and exceptions

   We confirm whether the request can be fulfilled, whether it affects others’ rights, and whether retention is required for transaction records, security investigations, disputes, or applicable law.

4. 4

   Receive the outcome

   The result is sent to the account-linked email or console ticket. If the request cannot be fully fulfilled, we explain the affected categories, reason for restriction, and available next steps.

You can submit a request by emailing support@mangovm.comor by logging in to theconsole and submitting a ticket. If the request concerns an active service, we recommend using a ticket first so the order and handling records can be linked securely.

Where applicable rules permit, you may object to specific processing based on legitimate interests, withdraw consent, request data in a portable format, or contact an authorized supervisory authority. The applicable scope depends on the request and the rules where you are located.

Server technical logs

Even if your browser rejects optional Cookies, servers may record request time, IP address, request path, response status, browser type, and security decisions to deliver pages, detect faults, and block attacks. These logs are processed as necessary for security and operation and are not optional analytics preferences.

You can delete Cookies, block non-essential storage, or adjust site permissions in your browser. Deleting necessary session identifiers usually signs you out and requires access verification again. Browser settings do not automatically delete existing orders, tickets, or security-incident records.

This version takes effect on August 24, 2026. The version number and effective date at the top of the page identify the rules you are reading.

If processing purposes, information categories, recipients, retention principles, or rights procedures materially change, we will update this page and, based on impact, notify you through the website, account-linked email, or console. New processing requiring consent will not treat continued browsing alone as consent.

You can request historical versions at support@mangovm.com. Put “Historical privacy notice” in the subject and state the approximate period you want. If an update affects existing orders, we will also explain its effective date and transition arrangements.