This document explains TradeStat rules and practices. Its contents identify the document type and any action that applies; informational notices do not themselves constitute user consent.
About this document
This policy explains which cookies and similar technologies the TradeStat site uses, why they are needed, how long they remain, and how to control them. Cookies are small browser records; similar technologies here means localStorage and sessionStorage.
We separate technologies into necessary and analytics categories. Necessary technologies preserve the selected language and privacy setting and, after successful sign-in, maintain a protected session. Analytics is off by default and appears only after explicit permission.
Necessary TradeStat technologies
These records are created by TradeStat and are not used for advertising. The language cookie is written after a user selects a language or supplies a valid lang parameter; until then, the browser language can be used without saving a cookie.
| Name | Storage | Purpose | Retention |
|---|---|---|---|
| tradestat_lang | Cookie | Selected language: ru or en | Up to 1 year |
| tradestat_analytics_consent | Cookie | Whether analytics is allowed or rejected | Up to 1 year |
| tradestat_session_replay_consent | Cookie | Separate choice for Session Replay and click maps | Up to 1 year |
| tradestat_consent_version | Cookie | Version of the cookie notice shown; a material new edition requires a new choice | Up to 1 year |
| __Host-tradestat_session | HttpOnly cookie | Random opaque session identifier containing no email, password, or AuthServer token | Up to 30 minutes or until sign-out |
| __Host-tradestat_preview_access | HttpOnly cookie | Temporary proof that this browser may use test accounts; it is not a user session and does not contain the original private-link capability | No later than the limited preview-access expiry |
| tradestat_analytics_consent_sync | localStorage | One-time signal used to synchronize the choice across tabs | Removed immediately after the signal is sent |
| tradestat_restore_language_focus | sessionStorage | One-time marker used to restore keyboard focus after a language switch | Removed after navigation; no longer than the browser session |
Yandex Metrica — only after consent
Allowing analytics loads Yandex Metrica tag 110885371. Session Replay and click maps are enabled only when that separate category is allowed. The provider may set first-party cookies on the TradeStat domain, cookies on Yandex domains, and localStorage or sessionStorage records. These help distinguish browsers, count visits, determine traffic sources, diagnose issues, limit requests, and—when separately allowed—record interactions.
According to Yandex’s official register, possible technologies include _ym_metrika_enabled, _ym_isad, _ym_uid, _ym_d, _ym_visorc_*, _ym_hostIndex, is_gdpr, yabs-sid, yandexuid, and ymex, plus _ym-prefixed web-storage records. Yandex controls this set and its retention and may change them; the provider’s current register prevails.
| Provider | Examples | Purpose | Provider-listed retention |
|---|---|---|---|
| Yandex Metrica / TradeStat domain | _ym_metrika_enabled, _ym_isad, _ym_uid, _ym_visorc_* | Traffic, browser identifier, Session Replay, diagnostics | 30 minutes to 1 year |
| Yandex Metrica / Yandex domains | is_gdpr, is_gdpr_b, yabs-sid, i, yandexuid, yuidss, ymex, usst | Technical service operation and browser distinction | Session or up to 2 years; longer in some countries for individual items |
| Yandex Metrica / web storage | _ym<id>_lastHit, _ym<id>_lsid, _ym_retryReqs, _ym_debugger_state | Request sequence, retries, identifier, and diagnostics | Set by the provider and browser session |
Data analytics may receive
After permission, Yandex may receive technical browser and device information, an IP address, referrer, the path of an opened page, and interface interactions. TradeStat manually sends only the pathname, without query parameters, hashes, or page titles.
We do not configure intentional transmission of names, email addresses, account or API identifiers, search text, input contents, or trading values to Metrica. Authentication callbacks are excluded; dashboard and admin surfaces use content masking and disabled click maps. Masking reduces recording risk but does not replace data minimization and tag-configuration review.
Managing and withdrawing your choice
Analytics, Session Replay, and click maps are off on the first visit. “Accept all” enables both optional categories, “Reject optional” leaves only necessary technologies, and “Customize” lets the user select ordinary analytics separately from Session Replay. Refusal does not restrict access to the public site.
The choice can be changed at any time. After withdrawal, TradeStat disables and destroys the accessible tag instance, removes its script, and attempts to delete accessible first-party Metrica cookies, localStorage, and sessionStorage. The site cannot itself delete records on Yandex domains; those can be removed in browser settings. Data already lawfully collected is not always erased automatically with cookies.
Updates and contact
When a new optional purpose or provider is added, the notice version changes, the saved permission is no longer treated as current, and analytics remains off until a new choice is made. Minor editorial changes may not require another prompt.
A public operator contact for privacy questions will be published before real user data is processed. Until then, treat this site as a demonstration environment and do not submit personal data or exchange keys through it.