iTGTrackerCookies & Local Data

Document content version: 2026-10-17-v2. Website language edition: 2026-10-22. These translations do not change accepted orders or their agreed contractual language. This website now uses fixed translations and no longer loads Google Translate. References in the original policy describe its publication context.

Cookie and Local Data Notice

Document version: 2026-10-17-v2. English translation. Operator: TYRENX TECHNOLOGIES, 202603272412 (AS0523259-D). Address and privacy contact are in the Privacy Policy; email itgtrackercs@gmail.com.

1. Scope and distinctions

This notice covers the website, Backend, BO, Windows Tracker and local scoring components. Cookies, localStorage, session storage, configurations, credentials, logs and manual downloads are different objects; calling everything a cookie must not conceal the scope.

2. Necessary and preference browser storage

Reviewed Backend pages use a localStorage access token, tgtrack_access_token, for authorised requests and tgtrack_ui_language and tgtrack_notice_language for language choices. Reading records link to server-side account/version records. Different products/versions may use their own sessions; no universal cookie name or lifetime is asserted.

Necessary login storage supports authentication, permissions, security and operation. Preferences support language and experience. localStorage may persist until cleared/removed; the server still determines token validity, regardless of whether a string remains.

A complete site-wide cookie/analytics scan has not been performed: this is not a “zero cookies” claim, a denial of all third-party scripts or a claim that an optional-analytics consent button already exists. Disclose new non-essential marketing/analytics purposes and offer legally required choice first. This notice does not authorise default loading.

3. Local Tracker and scoring programs

Approved computers may retain device credentials, connection settings, model names/files, logs, temporary processing information and exports. Local QA receives server tasks/conversations, processes them in the local model and submits results. “Local model” does not mean information never leaves Telegram or is never stored locally.

Some device keys use Windows protection; this does not encrypt every setting, log, cache, model or export. Privileged users, malware or compromised devices remain risks. Enterprises must manage Windows accounts, disks, permissions, uninstall and handover procedures.

With installation and authorisation, components may register background/startup or Windows-sign-in execution. Closing a page, closing an Ollama window, stopping its service, exiting the worker, revoking a device and uninstalling are different. GPU power control requires supported hardware, installation and approval, may affect other GPU applications, and follows the actual package's compatibility/recovery instructions.

4. Local and third-party authority

Manage browser login, Tracker credentials, Telegram sessions, Google Drive OAuth and scoring-device authority separately. Revoking one does not automatically revoke all. Approved connections permit relevant reads/writes within scope; closing a browser does not establish that background work stopped.

5. Clearing and controls

Browser site-data controls can clear storage/cookies, potentially signing out and resetting preferences, without deleting server content. Use actual product/support channels to revoke relevant devices, accounts and integrations. Google/Telegram sessions may also require their own account controls.

Before device handover/disposal, revoke access and clear local information under enterprise procedures. Uninstalling does not guarantee removal of downloads, logs, backups or third-party copies. Do not delete unknown system directories; support can identify the relevant installed version's scope.

Customers separately protect CSV, HTML, PDF and other exports and Drive copies. Sign-out cannot retract copies, screenshots or sharing. Server access, correction and deletion requests go to itgtrackercs@gmail.com under the Privacy Policy.