Cookie Policy

Version: 1.3
Effective date: 10 August 2026

1. General

This Policy describes cookies and similar technologies on patchdna.ai, ru.patchdna.ai and global.patchdna.ai and supplements the Privacy Policy. The apex patchdna.ai router does not set a PatchDNA session or preference cookie. Each regional service uses its own host-only technologies required for authentication, security and preferences. With the visitor's separate affirmative choice, it also uses Yandex Metrica for optional Website analytics. Session Replay and marketing or advertising technologies are not active.

2. What cookies are

A cookie is a small value stored by a browser and returned with later requests to the same service. It may maintain an authenticated session, remember a setting or, where a separate provider is installed, measure Website use.

3. Similar technologies

Similar technologies include localStorage, sessionStorage, pixels, SDKs and server-side identifiers. Yandex Metrica may use cookies and browser storage only after analytics consent. PatchDNA does not load an advertising pixel or marketing SDK in the current Website build.

4. Strictly necessary cookies

Necessary technologies support authentication, a protected Account session, same-origin request protection, rate limiting and checkout integrity. Account and purchase features cannot operate securely without them. PatchDNA omits the cookie Domain attribute: a cookie issued by ru.patchdna.ai is not sent to global.patchdna.ai and vice versa. Necessary technologies are disclosed here but are not placed behind an optional-consent switch where applicable law recognises the necessity exemption.

5. Functional cookies

A host-only first-party cookie remembers the selected RU or EN Website version on the regional service that issued it. It is not used for advertising, cross-site tracking or transfer of a session between regional services.

6. Analytics cookies

Yandex Metrica tag 111201464 may measure page visits, technical browser and Device characteristics, link interactions and clicks on non-sensitive public pages. It is used to understand performance and improve the Website, not to issue or enforce a Product License. The Yandex library and counter start only after the visitor separately accepts analytics. The integration sends the current page as origin plus pathname and the referrer as origin only; it intentionally excludes URL credentials, query parameters, fragments, email, Account identifier and License key. Session Replay (Webvisor) is disabled. The counter is not started on designated Account, authentication, checkout and License-claim routes.

7. Marketing cookies

PatchDNA does not currently use marketing cookies, advertising pixels or cross-site behavioural profiles.

8. Third-party services

When analytics is accepted, Yandex acts as the provider of Yandex Metrica and may receive the analytics data described above under its own privacy terms. When you actively leave PatchDNA for a Payment Provider or another external service, that provider may set cookies under its own policy. PatchDNA does not silently embed a third-party payment session before your action.

9. Duration

The Account session cookie lasts no more than 30 days and may end sooner after logout, password reset or session revocation. Preference cookies may last up to one year. Yandex Metrica durations vary by identifier, from the browser session or 30 minutes up to two years. Exact known values and the provider register are listed below.

10. Legal basis and consent

Necessary cookies support the service you request, performance of the agreement and the legitimate interest in security. Optional analytics is based on a separate consent, is off by default and is not preselected. Accepting the Terms, acknowledging the Privacy Policy or requesting immediate digital delivery does not count as analytics consent. Marketing technology is not active.

11. Managing preferences

On the first visit, the Website offers equally available choices to reject optional analytics or accept it. “Cookie settings” in the footer opens the preference control. A visitor may change or withdraw analytics consent at any time; withdrawal stops Yandex Metrica and removes accessible Yandex Metrica identifiers from this Website where technically possible. Rejecting or withdrawing consent means the Yandex library and counter are not loaded again unless the visitor later accepts analytics.

12. Browser controls

Your browser can display, delete and block cookies. Instructions are available in its privacy settings. Deleting the Account session cookie logs you out.

13. Effect of disabling cookies

Public pages remain readable when cookies are blocked, but authentication, checkout, downloads and License management may be unavailable. Rejecting any future optional analytics must not disable core Product functions.

14. Changes

Before a new cookie provider or technology is enabled, PatchDNA will update the version, categories, purposes, duration, recipients and consent behaviour in this Policy. Material changes receive a new effective date.

15. Contact

Cookie questions may be sent to support@patchdna.ai. Controller: Individual Entrepreneur Igor Grigoryevich Molka, INN 772377040614, OGRNIP 321774600446241.

16. Factual cookie register

Technology	Provider	Purpose	Category	Duration	JavaScript access
epc_session	PatchDNA	Authentication, role and protected Account session	Strictly necessary	up to 30 days	No, HttpOnly
patchdna-locale	PatchDNA	Selected Website language on the issuing regional host	Functional	up to 1 year	No, HttpOnly
patchdna_cookie_preferences	PatchDNA	Records the policy version and the visitor's analytics choice	Functional	up to 1 year	Yes
_ym_metrika_enabled	Yandex Metrica	Checks whether analytics cookies work correctly	Analytics	60 minutes	Yes
_ym_isad	Yandex Metrica	Determines whether an ad blocker is present	Analytics	20 hours	Yes
_ym_uid, _ym_d, _ym_fa	Yandex Metrica	Distinguishes Website users and records the first-session date	Analytics	generally up to 1 year	Yes
gdpr, is_gdpr, is_gdpr_b	Yandex Metrica	Records GDPR-jurisdiction handling	Technical / analytics	up to 2 years	Yes
_ym<tag ID>_* and other _ym* browser-storage values	Yandex Metrica	Request sequencing, bounce measurement, retry handling and visitor identification	Analytics	varies by purpose	Yes

epc_session and patchdna-locale attributes on the live regional services include Secure, SameSite=Lax, Path=/ and no Domain attribute. The patchdna_cookie_preferences cookie is likewise host-only but is readable by JavaScript so the page can apply the recorded choice. The apex router does not set these cookies. Email-verification and password-reset tokens are stored server-side, not in a browser cookie. Yandex maintains the current provider register at https://yandex.com/support/metrica/en/general/cookie-usage. The exact analytics set may vary by browser and enabled Yandex Metrica functions. Before analytics consent, PatchDNA does not load the Yandex library or counter. Session Replay remains disabled after consent.

Current Policy: https://global.patchdna.ai/en/cookies