Cookies & storage
Optional tools start only after a separate choice. Saving privacy settings does not authorise analytics or advertising.
Before a choice and after refusal
No analytics library, pixel, preconnect or remote tracking request is loaded. Nothing is written to browser storage before a choice. Rejecting both purposes removes the website decision and does not save a new one. The notice may return on the next page.
Decision record
Allowing preferences or analytics saves elazai.privacy.v2 in localStorage: version, revision, selected purposes and timestamp. No unique visitor identifier is in this record. It is recognised for 180 days and is not sent to our server. Changing the counter or collection scope requires a new choice. The old v1 permission cannot enable analytics.
Metrica data
Only after analytics permission, Yandex Metrica may create browser identifiers and provider storage, including _ym_uid and _ym_d (up to one year), _ym_isad (20 hours), and localStorage names beginning with _ym. The provider list and periods can change; consult its official cookie documentation. Unlike the decision record, these identifiers are used for statistics and sent to Yandex.
Withdrawing
Open Privacy settings in the footer, uncheck analytics and apply, or reject both purposes. The counter is stopped; accessible first-party _ym cookies and storage are removed. The page reloads to remove the already-loaded SDK. This cannot undo previous transmissions, delete reports at Yandex, remove HttpOnly cookies or erase data on another domain; use the provider contact channels and browser controls for those.
Advertising and new providers
Advertising services are not connected and cannot be enabled by this choice. A new provider needs its own integration, purpose and recipient disclosure, revised permission and tests that it makes no requests before that permission.