Cookie Policy
SafeLaw. Cookie Policy
Effective Date: November 2, 2026 · Last Updated: November 1, 2026 · Version: 1.4
Translation of the Russian original. The Russian version prevails in case of discrepancies.
This Cookie Policy (the "Policy") explains how SELLAI LLC ("SafeLaw," "we," "us" or "our") uses cookies and similar technologies on the safelaw.ai website and related applications (together, the "Service"). This Policy is part of our Privacy Policy (safelaw.ai/privacy) and should be read together with it.
1. What Are Cookies
Cookies are small text files stored on your device (computer, smartphone, tablet) when you visit a website. They allow the site to remember your actions and preferences (for example, language, font size, authentication) over a period of time, so that you do not have to set them again on every visit. In addition to cookies, we use browser local storage (localStorage) and session storage (sessionStorage). These are not cookies: they are described separately in section 5.
2. Cookies We Use
Below are all the cookies set on the safelaw.ai website. The Service does not set any other cookies. In addition, once you have given consent, the connected analytics and marketing services may set cookies on the providers' own domains (clarity.ms, bing.com, Yandex domains) — such cookies are marked in the table with the domain. The durations of third-party service cookies are given according to their providers' documentation and may be changed by them.
| Name | Purpose | Duration | Type | Can you opt out |
|---|---|---|---|---|
| auth_token | Authentication: confirms that you are logged in to your account. Not accessible to page scripts (HttpOnly) | Up to 30 days; deleted when you log out | Strictly necessary | No — logging in to your account is impossible without it |
| refresh_token | Extends the session without re-entering your password. Not accessible to page scripts (HttpOnly) | Up to 30 days; deleted when you log out | Strictly necessary | No — logging in to your account is impossible without it |
| _ga | Google Analytics 4: distinguishes visitors for site-traffic statistics | Up to 2 years | Analytics | Yes — set only after your consent |
| _ga_<id> | Google Analytics 4: stores the state of the visit session | Up to 2 years | Analytics | Yes — set only after your consent |
| _clck | Microsoft Clarity: stores the visitor identifier and Clarity settings for our site | 1 year | Analytics | Yes — set only after your consent |
| _clsk | Microsoft Clarity: combines the page views of one visit into a single session recording | 1 day | Analytics | Yes — set only after your consent |
| CLID | Microsoft Clarity: records when Clarity first saw this browser on sites that use Clarity. Set on the clarity.ms domain | 1 year | Analytics | Yes — set only after your consent |
| MUID | Microsoft: browser identifier used on Microsoft sites and services. Set on Microsoft domains (clarity.ms, bing.com) | 1 year | Analytics | Yes — set only after your consent |
| _ym_uid | Yandex Metrica: distinguishes visitors | 1 year | Analytics | Yes — set only after your consent |
| _ym_d | Yandex Metrica: stores the date of the first visit to the site | 1 year | Analytics | Yes — set only after your consent |
| _ym_isad | Yandex Metrica: detects whether an ad blocker is used | 20 hours | Analytics | Yes — set only after your consent |
| _ym_visorc | Yandex Metrica: enables Session Replay (Webvisor) | 30 minutes | Analytics | Yes — set only after your consent |
| _ym_metrika_enabled | Yandex Metrica: checks whether the other Metrica cookies are set correctly | 60 minutes | Analytics | Yes — set only after your consent |
| Other Metrica service cookies (_ym_fa, _ym_ucs, _ym_hostIndex, etc.) | Yandex Metrica: service data for identifying the visitor and limiting the number of requests | From 1 day to 1 year | Analytics | Yes — set only after your consent |
| yandexuid, yuidss, i, yabs-sid, ymex, usst | Yandex Metrica: distinguish users, store the visit identifier and auxiliary data for identifier synchronisation. Set on Yandex domains, not on safelaw.ai | yabs-sid — until the browser is closed; others — 1 year | Analytics | Yes — set only after your consent |
| ph_<project_key>_posthog | PostHog: stores the visitor and current session identifiers for product analytics and session recordings | 1 year | Analytics | Yes — set only after your consent |
| _fbp | Meta Pixel: browser identifier for measuring advertising effectiveness | Up to 90 days | Marketing | Yes — set only after your consent |
| _fbc | Meta Pixel: information about arriving at the site from a Meta ad (the fbclid parameter). Set by the Meta Pixel or by our code | 90 days | Marketing | Yes — set only after your consent |
2.1 Strictly Necessary Cookies
These are the auth_token and refresh_token cookies. They are required to log in to and use your account and cannot be disabled. If you do not log in to an account, they are not set.
2.2 Functional Settings
We do not set separate functional cookies. Your language, theme and interface settings are stored in the browser local storage (section 5). The "Functional" category in the consent banner is passed to Google Analytics as a consent signal and does not include any other cookies.
2.3 Analytics Cookies
These cookies help us understand how users interact with the Service so that we can identify problems and improve it. Through them we collect the visitor identifier assigned by the analytics tool, technical data about your device and browser, and information about your actions on the site. We use Google Analytics 4 (provider: Google LLC) to collect site-traffic statistics and improve the Service. The related cookies (e.g. _ga, _ga_<id>) are set only after you consent to analytics cookies and are not used before then. You can withdraw your consent by deleting the cookies and site data for safelaw.ai in your browser settings: the consent banner will then appear again and you will be able to make your choice anew (section 4).
The analytics category also includes the following services, which are activated only after you consent to analytics cookies:
- Microsoft Clarity (provider: Microsoft Corporation, USA) — statistics of on-page behaviour, heatmaps and session recordings. Cookies:
_clck,_clsk; on Microsoft domains —CLID,MUID. - Yandex Metrica with Session Replay (Webvisor) and click map (provider: Yandex LLC, Russia) — site-traffic statistics, click map and session recordings (Webvisor). Cookies:
_ym_uid,_ym_d,_ym_isad,_ym_visorcand other Metrica service cookies; on Yandex domains —yandexuid,i,yabs-sid, etc. - PostHog (provider: PostHog Inc.; data is stored and processed in the PostHog EU cloud — Frankfurt, Germany) — product analytics (which sections and features of the Service are used) and session recordings. Cookie:
ph_<project_key>_posthog; PostHog keeps part of its data in browser storage (section 5).
A session recording is a replayable record of how the page looked and how you interacted with it: navigation, scrolling, pointer movements and clicks. Session recordings in Microsoft Clarity, Yandex Metrica Webvisor and PostHog are configured with masking: the text you type into the chat field, as well as the texts of your questions and of the Service's answers on the page, are not recorded and are not sent to the providers of these services — masked placeholders appear in the recording instead.
2.4 Marketing Cookies
We use the Meta Pixel (provider: Meta Platforms, Inc.) to measure marketing and advertising effectiveness. The relevant cookies (_fbp, _fbc) are set only after you consent to marketing cookies and are not used before then. To match advertising conversions (sign-up, first question, payment), in addition to information about your actions on the site we pass your email address, phone number, name and account identifier to Meta — only in hashed form (irreversible SHA-256 transformation; the original values cannot be recovered from it), including from our server (Meta Conversions API). The contents of your documents and requests in the Service are not passed to advertising or analytics tools. Sign-up and payment information is passed to Meta from our server in hashed form even if you have not consented to marketing cookies — on the basis of the consent given at registration or payment (Privacy Policy, section 6.4). You can withdraw your consent by deleting the cookies and site data for safelaw.ai in your browser settings: the consent banner will then appear again and you will be able to make your choice anew (section 4).
3. Third-Party Cookies
When you use the Service, third-party services may set their own cookies on your device. We do not control these cookies. The third-party services that may set cookies are listed below:
3.1 Payment Providers
When you pay by Uzcard or Humo card via FreedomPay, or via Click or Payme, you go to the payment page of the relevant provider. The provider may set its own cookies on its page for transaction processing and payment security. These cookies are not set on the safelaw.ai website and are governed by the privacy policy of the relevant payment provider (FreedomPay, Click or Payme).
3.2 Hosting
Our hosting provider (Netcup GmbH) may use technical means for security and protection against attacks; if technical cookies are set for this, they serve only these purposes. These cookies are strictly technical and are not used for user tracking.
3.3 Analytics and Marketing Services
Once you have consented to the relevant cookie category, Microsoft Clarity and Yandex Metrica may set cookies on the providers' own domains (clarity.ms, bing.com, Yandex domains). These cookies are listed in the table in section 2 with the domain indicated; their use is also governed by the providers' privacy policies.
4. How to Manage Cookies
4.1 Via Our Consent Banner
On your first visit to SafeLaw, you will see a banner with information about cookies. You can:
-
Accept all cookies — all categories will be activated
-
Reject — only strictly necessary cookies will be activated
-
Open the settings (the gear icon) — enable only the categories you wish to allow and save your choice; by default only strictly necessary cookies are enabled.
Your saved choice remains in effect until you delete the cookies and site data for safelaw.ai in your browser settings. Once they are deleted, the banner will appear again and you will be able to make your choice anew. You can delete or block cookies at any time using your browser — see section 4.2.
4.2 Via Browser Settings
You can also manage cookies through your browser settings. Most browsers allow you to:
-
View the cookies that have been set
-
Delete all or individual cookies
-
Block cookies from specific sites
-
Block all cookies
-
Receive a notification when a cookie is set.
Instructions for the main browsers:
-
Google Chrome: Settings → Privacy and Security → Cookies
-
Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data
-
Safari: Preferences → Privacy → Manage Website Data
-
Microsoft Edge: Settings → Cookies and Site Permissions.
Please note: Blocking strictly necessary cookies may prevent some Service features from working (for example, logging in to your account).
4.3 On Mobile Devices
On smartphones and tablets, cookie management is done through the mobile browser settings. The path to the settings depends on the browser and the operating system used (Android or iOS).
5. Local Storage (localStorage / sessionStorage)
Browser local storage and session storage are not cookies: the data is stored only on your device and is not sent to the server with every request. SafeLaw uses them for the following:
| What is stored | Example keys | Duration | Type |
|---|---|---|---|
| Your cookie choice and the date of the choice | cookie_consent, cookie_consent_categories, cookie_consent_date, cookie_consent_epoch | Until the site data is cleared in the browser | Strictly necessary |
| A technical browser identifier — a random value created on your device. It is sent to our server together with your cookie choice (consent log) and with information about the source of your visit to the site | visitor_id | Until the site data is cleared in the browser | Strictly necessary |
| Language and theme | legalai-lang, legalai-theme, legalai-dark-theme | Until the site data is cleared in the browser | Functional |
| Selected jurisdiction and country | legalai-jurisdiction, legalai-country | Until the site data is cleared in the browser | Functional |
| AI response and voice input settings | legalai-ai-tone, legalai-ai-style, legalai-ai-clarify, legalai-voice | Until the site data is cleared in the browser | Functional |
| Interface state: sidebar, completed onboarding tour, dismissed notices | safelaw-sidebar-open, safelaw_tour_v1_done, safelaw_maint_closed_… | Until the site data is cleared in the browser | Functional |
| A local copy of the open chat and drafts, so that text is not lost when the page is refreshed | legalai-chat-…, legalai-session-id | Until the site data is cleared in the browser | Functional |
| A record of your consent to the terms of working with AI | ai_consent | Until the site data is cleared in the browser | Strictly necessary |
| The Meta ad click identifier from the page address (sessionStorage). Used only after consent to marketing cookies | safelaw_fbclid | Until the tab is closed | Marketing |
| PostHog state: visitor identifier, current session details and session recording. Used only after consent to analytics cookies | ph_<project_key>_posthog and PostHog service keys | Until the site data is cleared in the browser; session data — until the tab is closed | Analytics |
| Yandex Metrica service data: visitor identifier, bounce tracking, queue of unsent requests. Used only after consent to analytics cookies | _ym_uid, _ym<counter_number>_lsid, _ym<counter_number>_lastHit, _ym<counter_number>_reqNum, _ym_retryReqs | Until the site data is cleared in the browser | Analytics |
Apart from visitor_id, local storage data is not automatically sent to our servers. PostHog and Yandex Metrica data in browser storage is used by the scripts of these services and is sent to their providers (section 6) only after you consent to analytics cookies; Microsoft Clarity may also keep service data of their scripts in browser storage. You can clear local and session storage through your browser settings (usually together with deleting cookies); your language, theme and cookie choice will then be reset.
6. How Cookie Data Is Processed
Data collected through cookies is processed in accordance with our Privacy Policy (safelaw.ai/privacy) and the Law of the Republic of Uzbekistan "On Personal Data" (ZRU-547).
What we do not do:
-
We do not sell your personal data
-
We do not use cookies to access the contents of your documents or your conversations in the Service
-
We do not display third-party advertising on the site
What does happen with the data. Analytics and marketing cookies send information about your actions on the site to the providers of those tools:
- Google LLC, USA (Google Analytics 4);
- Meta Platforms, Inc., USA (Meta Pixel);
- Microsoft Corporation, USA (Microsoft Clarity);
- Yandex LLC, Russia (Yandex Metrica with Webvisor and click map);
- PostHog Inc. — data is stored and processed in the EU (Frankfurt, Germany) (PostHog).
We use this to understand how the Service is used, to find errors and inconvenient parts of the interface, and to measure the effectiveness of our own advertising and conversion, that is, to understand what share of the people who come to the site take the action we want. The text typed into the chat field and the texts of questions and answers are masked in session recordings and are not sent to the providers (section 2.3). Google, Meta, Microsoft and Yandex are, among other things, advertising platforms: they also process the data they receive from us in accordance with their own policies, and we do not control that processing of theirs. Such cookies are set only after you have given your consent (sections 2.3 and 2.4).
7. Changes to This Policy
We may update this Policy from time to time — for example, if we add new cookies or connect new third-party services. If we make material changes, we will notify you via an updated cookie consent banner and/or a site notification at least 15 days before the changes take effect. The "Last Updated" date at the top of this Policy indicates when it was last revised.
8. Contact Us
If you have any questions about this Policy or about the use of cookies on SafeLaw, contact us: SELLAI LLC, 91/7 A. S. Pushkin St., Nukus, Republic of Karakalpakstan, Republic of Uzbekistan. TIN (STIR): 312530703. Cookies and personal data: privacy@safelaw.ai. General enquiries: info@safelaw.ai Phone: +998 90 590 59 00
By using SafeLaw, you confirm that you have read and understood this Cookie Policy.