Cookies | Evolostok

01 What cookies are

Cookies are small pieces of data a site stores in your browser. They help recognise a session, secure sign-in and (when connected) measure anonymised statistics.

Similar technologies (local storage, session storage) may be used for the same interface purposes. In this Policy, “cookies” also covers such means when they store identifiers on the device.

This document supplements thePrivacy Policyand covers only cookies / tracking on the site and in cabinets.

02 Who uses cookies

Cookies are set when you visit evolostok.ru and CRM sections (/login, /cabinet, /app, /admin) under the Evolostok brand.

Questions: info@evolostok.ru
Form: /en/contact/

03 Cookie types

NecessaryRequired for sign-in, session security and basic cabinet operation. Without them protected sections do not work.

AnalyticsCount visits and events (clicks, form submits). Connected only if Google Analytics / Google Tag Manager IDs are configured on the site.

MarketingAd pixels and retargeting are not intentionally used on the site now. If that changes — we will update this section.

FunctionalInterface preferences (e.g. service flags). Not used for advertising.

04 Necessary cookies

For CRM operation and security we use, in particular:

auth session cookies (cabinet sign-in);
session security / CSRF parameters in combination with NextAuth;
technical markers without which an authenticated state cannot be kept.

These cookies are strictly necessary for the service you request (cabinet access). Disabling them in the browser will sign you out and break protected sections.

05 Analytics and events

The site has an internal event bus (evolostokTrack / dataLayer): CTA clicks, language switch, industry and service views, form submits, downloads. The bus itself does not set third-party cookies.

If PUBLIC_GA_ID and/or PUBLIC_GTM_ID are set in the site build, Google scripts (Analytics / Tag Manager) are loaded. The browser may then receive cookies and similar identifiers from Google for statistics. Where applicable, GA is configured with IP anonymisation (anonymize_ip).

While analytics IDs are not set in the build, third-party Google analytics cookies are not intentionally set. After providers are enabled, we will update this section with the current list.

06 Retention

session — deleted when the browser closes or the server session expires;
persistent (if used by an analytics provider) — until the provider’s term or until you clear them in browser settings;
necessary auth cookies — while the session is active / “remember me” under the authentication provider’s policy.

07 How to manage cookies

You can:

delete stored cookies in browser settings;
block or limit cookies for specific sites;
use incognito / private browsing (some cookies will not persist after the window closes);
for Google — additional ad and analytics settings on Google’s side (if analytics is connected).

Restricting necessary cookies makes stable CRM sign-in impossible. Restricting analytics cookies does not prevent browsing public pages.

08 Third parties and cross-border transfer

With Google analytics enabled, visit data may be processed by Google LLC / affiliates, including infrastructure outside Russia. That is cross-border transfer of technical / analytics data in the volume set by the counter configuration.

Site and CRM hosting, email and infrastructure services may log technical requests (IP, User-Agent) at the server level — this is not a “site cookie”, but relates to security and reliability. More on PD processing — in the Privacy Policy.

09 Updates

We update this Policy when providers, purposes or legal requirements change. Current version:/en/cookies/. Date and version number — in the page header.