{
    "status": "ok",
    "document": {
        "doc": "cookies",
        "label": "Cookies & Tracking Notice / Уведомление о cookie и трекинге",
        "requested_language": "en",
        "source_language": "en",
        "source_file": "cookies_tracking_notice_v4.php",
        "version": "4",
        "effective_date": "2026-09-04",
        "html_url": "https://voscom.online/legal/en/cookies_tracking_notice_v4.php",
        "text_url": "https://voscom.online/legal_text.php?lang=en&doc=cookies",
        "json_url": "https://voscom.online/legal_text.php?lang=en&doc=cookies&format=json",
        "sha256_text": "83c11f7a4d7931b532c265b7b430356546679c71c454f83583cc95493820346d",
        "sha256_source_file": "2f258162de9cb5699c3ea625e8b39693df148862cdc55d0374c530df0325bfcf",
        "last_modified": "2026-09-04T11:10:21+00:00",
        "text": "VOSCOM.ONLINEAll documentsVersion historyMy consents\n\n# Cookies and Tracking\n\nVersion: 4\nEffective date: 2026-09-04\n\nEnglish translation. The Russian edition is authoritative in the event of a discrepancy to the extent permitted by applicable law.\n\nTXT · JSON\n\n## 1. Operator and purpose\n\nVOSCOM-ONLINE LLC (ООО «ВОСКОМ-ОНЛАЙН»), OGRN 1217700640189, INN 9719021912, KPP 771901001. Address: 105484, Russia, Moscow, Vostochnoye Izmaylovo municipal district, Sirenevyy Boulevard, building 50, apartment 72.\n\nThis notice covers cookies, local storage and optional analytics on VOSCOM.ONLINE and supplements the Privacy Policy. The service is available in Russia and subject to Russian law and mandatory user rights. Visiting the site, silence or accepting general Terms is not analytics consent.\n\n## 2. Necessary technologies\n\nPHPSESSID identifies the login session, form security and operation state. It is a session cookie with HttpOnly, SameSite=Lax and Secure over HTTPS; it does not contain your password. Necessary processing supports requested functions and security on an applicable basis under Article 6 of Russian Federal Law No. 152-FZ. Declining analytics does not disable these functions.\n\nvoscom_cookie_consent stores necessary-only (essential) or edition-4 analytics permission (analytics_v4) for up to 180 days. voscom_cookie_receipt links permission to its audit record, has HttpOnly and the same maximum lifetime, and is removed on refusal. These host-scoped cookies use Path=/, SameSite=Lax and Secure over HTTPS.\n\nvoscom-public-theme in localStorage stores the theme. IDE, sound and AI conversation identifiers may also be stored locally for requested functions. localStorage has no automatic expiry and persists until changed or cleared. These preferences are not analytics permission.\n\n## 3. Separate analytics choice\n\nClicking “Accept analytics” gives the Operator separate consent to automated processing of the data below to measure visits and improve usability: collection, recording, organisation, accumulation, storage, use, event correlation, anonymisation, restriction and deletion; where Yandex Metrica is enabled, relevant data is also transmitted to its provider. Permission lasts until withdrawal or 180-day expiry. It does not authorise advertising mail, public disclosure of personal data or analytics processing of private message contents.\n\nBefore permission, the site tracker neither creates an analytics identifier nor sends events, and Metrica is not loaded. A failed permission save does not enable analytics. The old analytics value without a current edition is not treated as new consent; the site requests a fresh choice.\n\n## 4. Site analytics\n\nvoscom_marketing_visitor is a random localStorage identifier. The server keeps its hash and a session-identifier hash; for signed-in users visits may be linked to their account ID. Data includes IP address, browser User-Agent, language, page address and title, IDE tab, referrer, timing, duration and visibility, viewport size and interface events.\n\nThe browser tracker removes query parameters and # fragments from page and referrer addresses. This does not erase ordinary server access logs or previously collected data. Usernames, chat contents, passwords and API keys are not intended as arbitrary analytics event parameters.\n\n## 5. Yandex Metrica\n\nWhere the Operator has configured a counter, permission enables Yandex Metrica (Yandex LLC). The browser sends technical visit, device, page-address and interaction data. Visit measurement, click and link maps are enabled; Session Replay is disabled in the site's integration code. This does not authorise advertising mail.\n\nMetrica may use _ym_uid to distinguish visitors and _ym_d for first-visit date (up to a year), _ym_isad for ad-blocker checks (20 hours) and _ym_metrika_enabled for cookie checks (60 minutes). Actual storage depends on the browser and provider; Yandex-domain cookies may have other lifetimes. See the current Metrica inventory and Yandex policy. Provider terms do not remove the Operator's duties.\n\n## 6. Changing and withdrawing\n\nUse “Cookie settings” at the bottom of public pages, or “My consents and public name” in your account and its cookie section. Direct cookie settings do not require login.\n\n“Necessary only” stops new site analytics, removes its local identifier, stops the loaded Metrica counter and clears accessible local Metrica data and _ym_ cookies. Other open same-domain tabs receive the change; suspended tabs recheck on return. An already transmitted request cannot be recalled.\n\nRefusal applies locally even if its server audit is temporarily unavailable; the interface reports an unconfirmed audit separately. Third-party-domain, protected or inaccessible-path cookies may require browser cleanup. Withdrawal does not automatically erase all previously lawful records or backups; contact admin@voscom.online for erasure requests.\n\n## 7. Evidence of choice\n\nThe server journal records choice or withdrawal, timestamp, document edition and hash, IP address and account ID where available. A random receipt links permission to the browser; only its hash is journalled, not passwords, authentication-cookie contents or private keys. This evidence supports consent verification and requests, not advertising profiles.\n\n## 8. Retention\n\nPreference-cookie expiry is not the retention period for every server record. Analytics and consent evidence are retained only as necessary for their purposes and lawful obligations. Contact the Operator for specific retention grounds and periods. This notice does not claim an implemented automatic deletion deadline for every record. Refusal removes the local analytics identifier; other local preferences can be cleared in the browser.\n\n## 9. Other browsers and external resources\n\nChoices apply to the current browser and domain. Another browser or cleared storage requires another choice. Do Not Track does not replace the site's controls. Blocking necessary cookies may break login or form protection.\n\nFonts, CDNs and external embeds may receive connection data independently of analytics. Cookie permission does not authorise arbitrary transfers to any provider. The primary service database is in Russia; this is not a claim that all providers and all copies are exclusively in Russia. Personal data remains subject to the Privacy Policy and applicable Russian requirements, including transfer rules.\n\n## 10. Editions and contact\n\nThis edition supersedes edition 3 of 2026-09-03 for new analytics choices. Previous documents remain in history. Material purpose or processing changes require a fresh choice, not assumed permission.\n\nCookie, withdrawal, access and erasure requests: admin@voscom.online. Support: support@voscom.online. Operator: VOSCOM-ONLINE LLC, at the address in section 1."
    }
}