Privacy Policy

Data controller

Otgonbayar Lkhagva · TradeChrono · Mongolia

Controller and current scope

The TradeChrono operator identified below is the data controller. The privacy contact is provided in the shared operator disclosure. This policy describes only the current pre-launch website and software foundation.

The current website uses the first-party tc_locale cookie solely to remember EN or MN. It does not use optional analytics, advertising pixels, session replay, or marketing tracking.

Current and planned data

Current: the locale preference value may be stored on your device for up to one year. Normal hosting infrastructure may necessarily process request data such as IP address and security logs, depending on the verified deployment provider; no provider is named until actually enabled.

If you choose to email a published contact address, the operator receives your email address and the message contents through Google Workspace to respond to your inquiry. No message is collected merely by viewing a mailto link. Do not send broker credentials, payment-card details or unnecessary personal information.

Planned but not currently collected through website commerce/licensing: account ID, license ID, provider order ID, country, device/license metadata and optional analytics data. The policy will be updated before these systems collect data.

Data we do not collect

TradeChrono does not collect or store payment card numbers, CVV/CVC, broker or MT5 passwords, unnecessary identity documents, trading strategies, backtest trades, PnL, session files, or imported historical datasets through the current website foundation.

Purpose, retention, and choices

Functional preference data is used only to deliver the selected language and expires according to the cookie settings. Future data will receive a documented purpose, basis, retention period, and deletion path before collection.

Optional analytics and marketing remain OFF. Refusing future non-essential processing will not block basic website use.

Processors, transfers, and security

No payment or analytics provider currently processes data for this website. Lemon Squeezy and QPay are future architecture boundaries only. If enabled, relevant processors and cross-border handling will be disclosed before collection.

Reasonable data minimization, access control, secret separation, redacted logging, and lifecycle controls are required for future systems.

Requests and incidents

Use the Privacy requests channel below for access, correction, or deletion requests where applicable. Use the Security / vulnerability reports channel for security incidents. The named operator is responsible for these channels; incident notification procedures remain a launch requirement.