VERILYZE COOKIE AND SIMILAR TECHNOLOGIES POLICY
Version dated September 11, 2026
1. General Provisions
1.1. This Cookie and Similar Technologies Policy (the “Cookie Policy”) defines the procedure for using cookies, browser local storage, and other similar technologies when using the websites, applications, and services of Verilyze, including:
https://verilyze.ru;https://demo.verilyze.ru;https://app.verilyze.ru;- other subdomains of
verilyze.ru; - related web applications and other Verilyze components
(collectively, the “Service” or “Verilyze”).
1.2. The Operator is:
Individual Entrepreneur Denis Anatolyevich Denisov
Taxpayer Identification Number (INN): 525813258650
Primary State Registration Number of Individual Entrepreneur (OGRNIP): 325527500044492
Region of state registration: Russian Federation, Nizhny Novgorod Region
Email for personal data matters: [email protected]
hereinafter referred to as the “Operator”.
1.3. This Policy supplements the Verilyze Personal Data Processing Policy and applies together with it.
2. What Cookies Are
2.1. Cookies are small pieces of data that a website may store on a user’s device through the browser.
2.2. Cookies may be used to:
- enable website functionality;
- maintain a user session;
- ensure security;
- save user preferences;
- remember the selected language;
- remember the selected interface theme;
- analyze use of the website;
- prevent abuse;
- enable third-party authentication services.
2.3. In addition to cookies, Verilyze may use similar technologies, including:
localStorage;sessionStorage;- server-side session identifiers;
- technical identifiers;
- other browser mechanisms necessary for operation of the Service.
2.4. In this Policy, the term “cookies” may be used broadly to include the similar technologies listed above unless the context indicates otherwise.
3. Categories of Cookies Used by Verilyze
Verilyze divides the technologies it uses into the following categories:
- strictly necessary;
- functional;
- analytical;
- marketing.
4. Strictly Necessary Cookies
4.1. Strictly necessary cookies support the basic operation and security of the Service.
4.2. They may be used for:
- maintaining a user session;
- authentication;
- account protection;
- storing security state;
- protection against CSRF attacks;
- preventing repeated or suspicious requests;
- rate limiting;
- load balancing;
- proper request routing;
- storing the user’s cookie preferences;
- enabling forms;
- preventing automated abuse;
- enabling payment processing;
- performing other functions without which the Service requested by the user cannot operate correctly.
4.3. Strictly necessary cookies are used regardless of whether the user consents to analytical or marketing technologies, because certain Verilyze functions may not operate without them.
4.4. Users may block cookies through their browser settings; however, certain Verilyze functions, including account login, may stop working correctly.
5. Authentication and Session Cookies
5.1. When Verilyze’s own authentication mechanism is used, Verilyze may store cookies or other technical identifiers necessary for:
- logging into an account;
- maintaining an authenticated session;
- refreshing a session;
- logging out;
- protection against request forgery;
- protection against unauthorized access.
5.2. Depending on the technical implementation, Verilyze may use:
- temporary session cookies;
- secure HTTP-only cookies;
- refresh/session identifiers;
- server-side identifiers;
- other secure session management mechanisms.
5.3. Verilyze seeks not to store sensitive authentication data in JavaScript-accessible browser storage unless required by the selected architecture and appropriate security measures are implemented.
6. Functional Cookies
6.1. Functional cookies are used to remember user preferences and improve the usability of the Service.
6.2. They may store, for example:
- the selected interface language;
- light or dark theme;
- interface state;
- display preferences;
- selected time zone;
- other user preferences.
6.3. Depending on the relevant preference, functional information may be stored:
- in cookies;
- in
localStorage; - in the user’s server-side account.
6.4. If a corresponding function can operate without identifying the user and the law of the relevant jurisdiction requires consent for such storage, it will be enabled in accordance with the user’s cookie preferences.
7. Analytical Technologies
7.1. Analytical technologies help the Operator understand:
- how many users visit the Service;
- which pages are most frequently used;
- which functions are used;
- where users come from;
- whether technical problems occur;
- how quickly pages load;
- how the structure and interface of the Service can be improved.
7.2. Analytical data should not be used to read the contents of user files, private messages, or other materials unrelated to analyzing use of the website.
7.3. The Operator seeks to prevent general-purpose web analytics systems from receiving:
- full names;
- email addresses;
- telephone numbers;
- form contents;
- user files;
- contents of analytical tasks;
- other information not required for traffic statistics.
8. Yandex Metrica
8.1. Yandex Metrica may be used to analyze the use of Verilyze by users from the Russian Federation.
8.2. Yandex Metrica may use cookies, browser storage, and technical identifiers to generate statistical information about website visits.
8.3. Yandex Metrica may process, in particular:
- information about pages visited;
- date and time of visit;
- session duration;
- referral source;
- technical information about the device and browser;
- approximate regional information;
- user actions on pages to the extent permitted by analytics settings;
- technical browser identifiers.
8.4. The Operator should not intentionally transmit the contents of fields containing personal data to Yandex Metrica unless such transfer is provided by a specific service function and has an appropriate lawful basis.
8.5. Certain advanced analytics functions may be disabled or restricted where their use creates an unjustified risk of processing confidential information.
8.6. Yandex Metrica is used taking into account applicable law and the user’s consent settings.
9. Google Analytics
9.1. Google Analytics may be used for Verilyze users outside the Russian Federation.
9.2. Google Analytics may use cookies and other technologies to analyze website usage.
9.3. Google Analytics may process:
- page visit data;
- session information;
- referral source;
- technical information about the browser and device;
- approximate geographic location;
- interaction events within the interface;
- technical identifiers.
9.4. For users from the European Economic Area, the United Kingdom, and other jurisdictions where prior consent is required for the relevant analytical technologies, Google Analytics is activated only in accordance with the user’s choice.
9.5. By default, before the required consent is obtained, storage of analytical cookies for which such consent is mandatory must remain disabled.
9.6. The Operator may use technical consent management mechanisms, including Google-supported Consent Mode or comparable solutions.
10. Cloudflare Web Analytics
10.1. Cloudflare Web Analytics may be used to obtain general statistics concerning the performance and use of Verilyze websites.
10.2. This service may be used as a statistics and performance measurement technology without creating traditional identifying analytical cookies.
10.3. Cloudflare Web Analytics may use technical data to measure:
- page loading;
- performance;
- number of page views;
- Core Web Vitals;
- other aggregated technical characteristics of website operation.
10.4. Use of Cloudflare Web Analytics does not eliminate Cloudflare’s processing of certain technical data in connection with other Cloudflare services, including CDN, network protection, DNS, WAF, and abuse prevention.
11. Cloudflare and Cloudflare Turnstile
11.1. Verilyze uses or may use infrastructure services provided by Cloudflare.
11.2. Cloudflare may provide:
- content delivery;
- DNS;
- network infrastructure protection;
- filtering of malicious traffic;
- DDoS protection;
- protection against automated requests;
- analysis of technical security events.
11.3. Verilyze may also use Cloudflare Turnstile to verify that a request is made by a human user or an allowed client application rather than a malicious automated system.
11.4. To perform such verification, Cloudflare may receive technical information about the request, browser, and device.
11.5. Technologies strictly necessary to protect forms, accounts, and infrastructure are classified as security technologies.
12. Third-Party Authentication
12.1. In addition to its own login mechanism, Verilyze may allow authentication through third-party providers.
12.2. The Russian version of the Service may use:
- Telegram;
- Yandex ID;
- VK ID / VK OAuth;
- other authentication services.
12.3. The international version may use:
- Telegram;
- Google;
- Meta/Facebook, if such functionality is enabled;
- X, if such functionality is enabled;
- other authentication providers.
12.4. When selecting a third-party login method, the user also interacts with the relevant authentication provider.
12.5. Such provider may use its own:
- cookies;
- session identifiers;
- security mechanisms;
- local storage;
- other technologies
in accordance with its own privacy policy and terms of use.
12.6. Verilyze does not determine the composition or retention periods of cookies created directly on the domains of third-party providers.
12.7. A third-party authentication flow is initiated by the user by selecting the relevant login button.
12.8. If displaying a login button requires loading third-party JavaScript or an iframe that may use optional cookies before the user actively selects that authentication method, the integration should be configured in accordance with applicable consent requirements.
13. Payment Services
13.1. When paying for Verilyze products or services, the user may be redirected to the payment provider’s website or interact with an embedded payment form provided by the payment provider.
13.2. The primary planned payment provider is YooKassa.
13.3. Other payment organizations may be connected in the future.
13.4. A payment provider may use its own cookies and other technical mechanisms necessary for:
- processing payments;
- ensuring security;
- preventing fraud;
- confirming transactions;
- complying with legal requirements.
13.5. Verilyze does not receive or store users’ full bank card details.
14. Marketing Cookies
14.1. Marketing cookies may be used for:
- measuring advertising campaign effectiveness;
- attribution;
- audience creation;
- displaying relevant advertising;
- retargeting;
- measuring advertising conversions.
14.2. At the time of adoption of this version, Verilyze does not need to use marketing cookies for the operation of its core Service functions.
14.3. If such technologies are introduced, they must be assigned to the separate “Marketing” category.
14.4. Where applicable law requires prior consent, marketing technologies are not activated before such consent is obtained.
14.5. Refusal of marketing cookies must not prevent use of Verilyze’s core functionality.
15. Consent Management
15.1. When first visiting the website, the user may be shown a cookie notice or cookie management interface.
15.2. Depending on applicable law, the user may be offered the following options:
- Accept All;
- Necessary Only;
- Customize.
15.3. The settings may include the following categories:
Necessary — always active to the extent required for operation of the Service;
Functional — used in accordance with user preferences;
Analytics — used where an appropriate lawful basis exists;
Marketing — used only where an appropriate lawful basis exists and, where required, with consent.
15.4. Optional categories must not be enabled merely because the user continued using the website where applicable law requires separate affirmative consent.
15.5. Where consent is required, failure to make a choice or closing the notice does not constitute consent to optional technologies.
15.6. Consent must be provided through an affirmative action by the user.
16. Default Settings
16.1. In jurisdictions where prior consent is mandatory, the following approach applies before the user makes a choice:
Strictly Necessary: enabled;
Functional technologies requiring consent: disabled;
Analytics: disabled;
Marketing: disabled.
16.2. After the user makes a choice, only categories permitted by the user are activated.
16.3. A user who refuses optional cookies must retain the ability to use the core functionality of the Service.
17. Geographic Differences
17.1. Verilyze may use different sets of services depending on the user’s region.
17.2. For example:
For the Russian Federation
The following may be used:
- Yandex Metrica;
- Verilyze’s own authentication;
- Telegram;
- Yandex ID;
- VK ID;
- Cloudflare;
- Cloudflare Turnstile;
- YooKassa.
For Users Outside the Russian Federation
The following may be used:
- Google Analytics;
- Cloudflare Web Analytics;
- Verilyze’s own authentication;
- Telegram;
- Google;
- Meta/Facebook;
- X;
- other regionally available services.
17.3. The inclusion of a particular provider in this list does not mean that it is used during every visit to the Service.
17.4. The specific set of technologies depends on:
- the user’s region;
- the version of the Service being used;
- selected settings;
- actions taken by the user;
- availability of the relevant provider;
- the current Verilyze configuration.
18. Determining the User’s Region
18.1. To select the appropriate website version, analytics systems, and legal regime, Verilyze may approximately determine the user’s region based on:
- IP address;
- selected language or region;
- domain or Service version;
- account settings;
- other technical indicators.
18.2. IP-based geolocation is approximate and may be inaccurate, for example when using a VPN, proxy, or corporate network.
18.3. Where technically and legally permitted, a region or Service version selected manually by the user may take precedence over the automatically determined region.
19. Storing the User’s Cookie Choice
19.1. To avoid asking the user to make the same choice on every visit, Verilyze may store the user’s decision.
19.2. A strictly necessary cookie or similar technical storage mechanism may be used for this purpose.
19.3. Such storage may contain:
- selected categories;
- date of consent;
- Cookie Policy version;
- consent interface version;
- technical identifier of the choice.
19.4. The Operator may retain a server-side record of consent where necessary to demonstrate that such consent was obtained.
19.5. The user may be asked to make the choice again if:
- the composition of cookies changes materially;
- processing purposes change;
- applicable law changes;
- the applicable consent period expires;
- the user deletes cookies;
- the user accesses the Service from a new device or browser.
20. Changing Settings and Withdrawing Consent
20.1. The user may change their decision regarding optional cookies.
20.2. Verilyze websites may provide a permanent link labeled:
“Cookie Settings”
or a similar interface element.
20.3. Through this interface, the user may be able to:
- review the current selection;
- allow cookie categories;
- disable cookie categories;
- withdraw previously provided consent.
20.4. Withdrawal of consent does not affect the lawfulness of processing carried out before the withdrawal.
20.5. After withdrawal, optional technologies based solely on such consent cease to be used for subsequent user activity to the extent technically possible.
21. Managing Cookies Through Browser Settings
21.1. Most browsers allow users to:
- view cookies;
- delete cookies;
- block cookies;
- block third-party cookies;
- clear website data;
- manage local storage.
21.2. Such settings are available directly in the user’s browser.
21.3. Disabling all cookies may cause incorrect operation of:
- authentication;
- sessions;
- interface preferences;
- forms;
- security systems;
- other Verilyze functions.
22. Cookie Retention Periods
22.1. Cookies may be:
Session Cookies
Deleted after the session ends or the browser is closed, unless the browser is configured otherwise.
Persistent Cookies
Stored for a specified period or until deleted by the user.
22.2. The retention period depends on the purpose of the relevant technology.
22.3. Verilyze seeks to set retention periods for its own cookies no longer than necessary for the relevant purpose.
22.4. Retention periods for cookies used by third-party providers are determined by those providers and may change independently of Verilyze.
23. Indicative List of Technologies
Depending on the Service configuration, the following categories of technologies may be used:
| Service | Purpose | Category |
|---|---|---|
| Verilyze | Authentication and session | Necessary |
| Verilyze | Security | Necessary |
| Verilyze | Storing cookie preferences | Necessary |
| Verilyze | Interface language | Functional |
| Verilyze | Light/dark theme | Functional |
| Cloudflare | CDN and network functions | Necessary / Infrastructure |
| Cloudflare Turnstile | Anti-bot protection | Necessary |
| Yandex Metrica | Usage statistics | Analytics |
| Google Analytics | Usage statistics | Analytics |
| Cloudflare Web Analytics | Performance statistics | Analytics / Technical |
| Telegram | Authentication | Necessary when this login method is selected |
| Yandex ID | Authentication | Necessary when this login method is selected |
| VK ID | Authentication | Necessary when this login method is selected |
| Authentication | Necessary when this login method is selected | |
| Meta/Facebook | Authentication | Necessary when this login method is selected |
| X | Authentication | Necessary when this login method is selected |
| YooKassa | Payment processing | Necessary when a payment is made |
23.1. This table is provided for informational purposes.
23.2. Specific cookie names, retention periods, and technical parameters may change when Verilyze or the relevant third-party service is updated.
23.3. The actual current set of cookies may additionally be displayed in the cookie management interface.
24. Data Transfers to Third-Party Providers
24.1. When a third-party technology is used, certain technical data may be transferred to the relevant provider.
24.2. Depending on the technology, such data may include:
- IP address;
- User-Agent;
- browser information;
- device information;
- date and time of request;
- URL;
- referrer;
- technical identifier;
- interaction event data.
24.3. Such processing is additionally governed by the Verilyze Personal Data Processing Policy and the documents of the relevant provider.
24.4. Where foreign providers are used, certain operations may constitute cross-border transfers of personal data.
24.5. Such transfers are carried out in compliance with applicable legal requirements.
25. Protection of Confidential Areas of Verilyze
25.1. The Operator seeks not to use general-purpose marketing or behavioral analytics systems in parts of the Service where users work with confidential analytical materials unless such use is necessary.
25.2. In particular, reasonable measures should be taken to prevent third-party analytics systems from receiving:
- contents of uploaded documents;
- texts of user queries;
- results of private analytical tasks;
- confidential reports;
- parameters of closed monitoring;
- identifying information concerning analyzed persons that is not necessary for operation of the analytics service.
25.3. To evaluate the operation of such areas, anonymized technical events or internal server-side statistics should preferably be used.
26. Do Not Track and Similar Signals
26.1. Browsers and operating systems may support various signals designed to limit tracking.
26.2. Verilyze may honor supported privacy signals where compliance with such signals is required by applicable law.
26.3. Support for particular signals may depend on the user’s region and the technical implementation of the Service.
27. Changes to this Policy
27.1. The Operator may amend this Cookie Policy due to:
- changes in legislation;
- addition or removal of third-party services;
- changes in analytics infrastructure;
- introduction of new Verilyze functions;
- changes in authentication mechanisms;
- changes in data storage methods.
27.2. The current version is published on the Verilyze website.
27.3. The effective version date is stated at the beginning of the document.
27.4. If changes materially affect processing for which consent is required, the Operator may request that the user make a new choice.
28. Contact Information
For questions regarding cookies, analytics, and personal data processing, please contact:
Individual Entrepreneur Denis Anatolyevich Denisov
Taxpayer Identification Number (INN): 525813258650
Primary State Registration Number of Individual Entrepreneur (OGRNIP): 325527500044492
Russian Federation, Nizhny Novgorod Region
[email protected]
Document: Verilyze Cookie and Similar Technologies Policy
Version: 1.0
Revision date: September 11, 2026
Operator: Individual Entrepreneur Denis Anatolyevich Denisov