What cookies are
Cookies are small text files your browser stores on behalf of a site and sends back with every request. We use them only to remember the things without which the application would not work: that you are signed in, that a request really comes from you, which language you want the interface in, and what you chose about cookies themselves.
Every cookie listed here is first-party. There is no third-party cookie on any page of the platform.
The category model
Cookies fall into three categories. Only two of them have a switch, because only two of them leave room for a choice.
- Essential — always on, no switch. The sign-in session, CSRF protection, language, the secure link between sign-in and your subdomain, and the consent cookie itself. Without them sign-in and security do not work, so there is nothing to accept or refuse.
- Analytics — switch, off by default. These would measure how the site is used. Currently unused: we set no cookie in this category, even if you allow it. Your choice is stored for the future.
- Marketing — switch, off by default. These would measure campaigns. Currently unused: zero pixels, zero ad networks, zero third-party cookies.
- No non-essential script is allowed to load without passing the consent gate. This is not an editorial promise: it is a technical boundary in the site's own code.
The full inventory
This is the complete list of cookies BuildMetrica sets today. If we ever add another, this list is updated BEFORE it is set.
- buildmetrica-session — holds your sign-in session. Essential. Server-only (HttpOnly), SameSite=Lax, expires after 120 minutes of inactivity.
- XSRF-TOKEN — proves that every write action really comes from our site (CSRF protection). Essential, readable by the site's script, same lifetime as the session.
- locale — remembers the chosen language, sq or en. Essential for the interface, server-only and encrypted, one-year lifetime.
- bm_consent — stores your choice for this site: the policy version you accepted, the categories allowed and the moment of the choice. Essential (without it we could not remember your refusal), readable by the site's script, SameSite=Lax, 12-month lifetime. It contains no account identifier and does not travel to company subdomains.
- bm_handoff_state — links sign-in on the main site to your company's subdomain and prevents anyone else from placing you into an account that is not yours. Essential, server-only (HttpOnly), one-minute lifetime.
- remember_web_… and remember_platform_… — set ONLY if you tick the "Remember me" box at sign-in, so you do not sign in every time. Essential at your request: leave it unticked and they are never set. Lifetime up to 400 days.
Local storage in the browser
Besides cookies, we keep a few preferences in your browser itself. These are never sent to the server and do not identify you.
- The collapsed or expanded state of the sidebar inside the application.
- The progressive web app (PWA) cache for static files, so pages open fast and work offline.
Consent: how it is taken, stored and changed
On the first visit a bar appears at the bottom of the page with three actions: accept all, essential only, or open settings. The bar does not block reading and takes up no space in the page — refusing is exactly as easy as accepting, with the same number of clicks and the same visual weight.
Your choice is stored in your browser only, in the bm_consent cookie, together with the version of this policy and the moment of the choice. We do not store it in the database and do not tie it to your account.
VERSIONING: the version number of this policy is shown at the top of the page and stored inside the cookie. If we change what you are agreeing to — the categories or their use — the version increases, the previous consent ceases to be valid and the question is asked afresh. Expiry after 12 months has the same effect.
CHANGING YOUR CHOICE: the footer of every public page carries a "Cookie settings" link that reopens the preference centre at any time. The new choice replaces the old one immediately.
No tracking and no third parties
We use no Google Analytics, no advertising pixels, no ad networks, no external fonts, no embedded maps and no other third-party resource on the public surface. We do not follow you across other sites and we do not sell usage data.
The "currently unused" label on the two optional categories is a statement of fact, not a cautious formula: no such script exists in the code today. If one is ever added, it will pass through the consent gate and this page will be updated first.
Managing them from the browser itself
Every browser lets you view and delete cookies from its settings. Bear in mind that deleting or blocking essential cookies means you will not be able to sign in: the session and CSRF protection depend on them.
Deleting the bm_consent cookie brings the consent bar back on your next visit — the same state as a new visitor.
Changes
Any change to this inventory is reflected here, together with the new effective date and the new version number at the top of the page.