Version dated 19 September 2026.
This Policy explains how ИП Ефремова Софья Николаевна uses cookies and similar technologies on https://app.cleverapp.pro and in your account, what each one is for, how long it lives and how to refuse it. It forms part of our Privacy Policy, which describes everything else we do with personal data.
A cookie is a small text file that a website asks your browser to store on your device and sends back on your next visit. Cookies let a site remember that you signed in, which language you chose and which interface hints you have already dismissed.
We also use technologies that work like cookies: local storage in the browser, where your account keeps interface preferences, and pixels — tiny images whose loading tells an analytics service that a page was opened. Everything said here about cookies applies to those technologies too.
A first-party cookie is set by our site. A third-party cookie is set by another company whose code runs on the page.
Optional cookies are not a condition of using the service: refusing them withholds no feature, hides no content and changes no price.
These are always set, because the site cannot work without them.
lang — the language you selected, so that the site opens in it next time. First party. Lifetime: 1 year.__Host-wb_sid, __Host-wb_rt (formerly wb_sid, wb_rt) — your signed-in session in the account: a short-lived access token and the refresh token that keeps you signed in. These are HttpOnly (unreadable by scripts), Secure and SameSite=Lax; the __Host- prefix means the cookie is bound to this site only and cannot be replaced from another subdomain. First party. Lifetime: the refresh period of the session, after which you sign in again. Set only after you sign in, never for a visitor who is not logged in.aat — marks a support agent working in your account at your request. First party. Lasts until that session ends.Signing out deletes the session cookies.
A few cookies remember your choices in the interface so that the account does not show you the same thing twice: bannerId — an announcement you closed (30 days), mtcm — a maintenance notice you closed (1 day), mr_ab_vl — the collapsed help panel in the conversations section (1 year).
They hold only the number of an announcement or a "hidden" flag. They contain no profile of you, are not read by any third party and are not used for advertising.
If you arrive by a campaign link that carries UTM parameters, we store those parameters — utm_source, utm_medium, utm_campaign, utm_term, utm_content — in first-party cookies so that a registration completed later can be attributed to the campaign that brought you.
If you open a registration link from one of our partners, the partner's identifier is stored the same way in a first-party cookie called ref_id, so that the partner receives credit for your registration under our affiliate programme.
These cookies are set only when you actually follow such a link. They hold a campaign or partner label, not a profile of you; they are not read by any third party, are not used for advertising to you elsewhere and are not combined with data from other sites.
They belong to the marketing category. For visitors from countries where the law requires consent to be asked in advance — the European Economic Area, the United Kingdom and Switzerland — we do not set them at all: the parameters stay in the page you are looking at and are discarded when you close it.
They are deleted as soon as you register, because their only purpose is over at that point. If you never register, they expire on their own — ref_id after a year, the UTM cookies after five. You can delete them at any time in your browser settings, and blocking them has no effect on how the site works for you.
If you sign in with the Google, Yandex or VK button, the sign-in page loads that service's code, and it sets its own third-party cookies to recognise you in your account with them. Those cookies belong to that company and are processed under its terms; we do not read them. If you sign in with an email address or a phone number, that code is not loaded.
Every browser lets you see the cookies stored for a site, delete them, block third-party cookies or block all cookies. The settings are usually under Privacy or Site settings:
Blocking the strictly necessary cookies will break sign-in. Private or incognito windows delete cookies when you close them, so your language and dismissed hints are forgotten each time.
Inside your account we keep a few preferences in the browser's local storage rather than in cookies, because they never need to reach our servers: the light or dark theme, the collapsed menu, the blocks you recently used in the flow editor and the contents of the editor clipboard.
That data stays on your device, is not sent to us and is not read by anyone else. Clearing the site data in your browser removes it.
Where one of our users runs an online school on their own domain, or publishes a shop front, a site or a widget, the cookies set there serve that user's service. For those cookies the user is the controller: their own cookie notice applies, and requests about them go to them.
We provide the technical means and do not use those cookies for our own purposes.
The mini apps our users build in the editor do not open on this site or in your account: they open on a separate domain that we operate for mini apps. The platform itself sets no cookies there. To make the app work, it keeps the following in the browser's local storage on that domain:
So that a mini app can be installed on your home screen and opened without a connection, your browser registers a service worker for it and keeps a cache of the app's files: the page, scripts, styles and images. The server's responses to what you do in the app are not stored in that cache. Clearing the site data in your browser removes the service worker and the cache.
A mini app may also run code added by its owner, our user: their own scripts, HTML code and external scripts such as analytics counters or third-party widgets. That code can set its own cookies, use the browser's storage and send data directly to third parties without passing through us. We do not review that code and do not use those cookies or that data for our own purposes. It is for the owner of the app to tell visitors about those cookies and to obtain their consent where the law requires it: the owner's own cookie notice applies, and requests about them go to the owner.
When the set of cookies changes, we update this Policy and the version date at the top of the page.
The current version is always available at https://app.cleverapp.pro/cookies.
ИП Ефремова Софья Николаевна, 663020, Красноярский край, Емельяновский район, п.г.т. Емельяново, ул. Ромашковая, д. 2..
Questions about cookies and privacy: info@cleverapp.pro.
Your rights as a data subject and how to exercise them are described in the Privacy Policy.