Cookie Use
This is a translation provided for convenience. The Russian version of the document is the main one: if the texts diverge, it prevails.
1. What cookies are
A cookie is a small file that a website saves in your browser. On your next request the browser sends the file back, and the site knows it is dealing with the same visitor. Without this mechanism you could not, for example, stay signed in while moving between pages. Cookies come in two kinds: session cookies, which disappear as soon as you close the browser, and persistent ones, which stay until their term runs out or until you delete them. This page describes which of these files the brickworld.biz website (the "Site") uses, what they are for and how to refuse them. Information that reaches us by other means is covered by the Privacy Policy. Revised 12 August 2026.
2. Why we use them
Only to run the Site: to keep you signed in to your account, to protect the sign-in procedure and to remember the language you chose. We do not use cookies for advertising, we do not follow you across other sites with them and we do not build a profile of you.
3. Which cookies the Site sets
Every file below is set by the Site itself. In the usual wording of such documents they are strictly necessary and functional: we have no analytics, advertising or tracking categories at all, which is why there is no section listing them.
| File | Term | Category | What it does |
|---|---|---|---|
| brick_session | 30 days | Strictly necessary | Holds the key to your session: it is how the Site recognises you as you move between pages. The term runs from the moment you sign in. Deleted when you sign out. Without it there is no way into your account. |
| brick_oauth | 10 minutes | Strictly necessary | Protects the sign-in procedure from substitution. Appears when you go to authorise through Telegram and is deleted as soon as you come back to the Site. |
| NEXT_LOCALE | Until the browser closes | Functional | Holds the language code of the version of the Site you opened. Appears on the very first request to any page, before you have chosen anything. |
brick_session
Term: 30 days
Category: Strictly necessary
What it does: Holds the key to your session: it is how the Site recognises you as you move between pages. The term runs from the moment you sign in. Deleted when you sign out. Without it there is no way into your account.
brick_oauth
Term: 10 minutes
Category: Strictly necessary
What it does: Protects the sign-in procedure from substitution. Appears when you go to authorise through Telegram and is deleted as soon as you come back to the Site.
NEXT_LOCALE
Term: Until the browser closes
Category: Functional
What it does: Holds the language code of the version of the Site you opened. Appears on the very first request to any page, before you have chosen anything.
The first two files are closed to page scripts and travel only over a secure connection. The language file is not protected at all, because there is nothing in it to protect: it holds two letters of a language code.
4. What we keep in the browser besides cookies
Your answer to the cookie question is remembered not by a cookie but by the browser storage built into your browser.
| Record | Storage | Term | What it does |
|---|---|---|---|
| brick-cookies-accepted | localStorage | Until site data is cleared | Appears if you pressed Accept. While the record is there, the question is no longer shown. |
| brick-cookies-declined | sessionStorage | Until the tab is closed | Appears if you pressed Decline. We stop asking for this visit and ask again on the next one. |
brick-cookies-accepted
Storage: localStorage
Term: Until site data is cleared
What it does: Appears if you pressed Accept. While the record is there, the question is no longer shown.
brick-cookies-declined
Storage: sessionStorage
Term: Until the tab is closed
What it does: Appears if you pressed Decline. We stop asking for this visit and ask again on the next one.
These records never leave for the server and are needed only by your browser. You can delete them together with the site data in your browser settings.
5. Third party cookies
There are no third party cookies on the Site. We have connected neither advertising networks nor social network widgets, so there is nowhere for their files to come from. Fonts, images and video are served by our own server, not from someone else’s storage. We count visits to the Site ourselves. That count uses no cookies, saves nothing in your browser and passes nothing to third parties. Nor are the technologies that usually accompany cookies present: pixels, web beacons, tracking of opened email. The Site sends no mailings at all. When you follow our links outwards, to Telegram for instance, you come under the rules of that service. It has files of its own, and this page does not cover them.
6. How to refuse cookies
Any browser lets you inspect, block and delete cookies. In Chrome, Safari, Firefox, Edge and Opera this lives in the settings section called Privacy and security or Site settings; the same place lets you block files for a single address without touching the rest. If your browser sends Do Not Track or Global Privacy Control signals, they change nothing on our Site, and the reason is simple: there is nothing to change. We have no optional files, so such a signal has nothing to switch off. Do keep in mind: if you block cookies for this Site, signing in to your account will not work, because the Site will have no way of recognising you. The rest of the sections (work, careers, legal pages) stay available as usual.
7. Changes
If the set of files changes, if third party cookies appear for example, we will update this list before connecting them and put a new revision date on it. You can follow the changes on this page.
8. Questions
If something here is unclear, write to us on Telegram: or by email: hello@brickagency.email. Everything else we know about you is covered by the Privacy Policy.