Cookie notice
This site sets no cookies, and the only thing it stores is your answer to the question of whether it may. The details are worth stating plainly — including what the product does inside your own cluster, which is a different question with a different answer.
Last updated 27 August 2026
On this website
No cookies are set by these pages: no analytics cookie, no advertising identifier, no session cookie. One thing is written to your browser's local storage, and only after you have answered the bar described below: the answer itself. No third-party script runs that could write anything on our behalf.
Everything the pages need — fonts, images, stylesheets, the small script that opens the mobile menu — is served from this domain. There is no CDN in the path, so no third party learns that you visited.
The choice bar
On your first visit a bar appears at the bottom of the page with two buttons: accept and reject. They are the same size, in the same row, one click each. There is no "manage my preferences" maze behind the reject, because a reject that is harder to press than an accept is not a choice.
Answering it changes nothing today, and we would rather say so than imply otherwise: there is currently nothing on these pages to accept or reject. What the answer does is settle the question in advance, so that the day something non-essential is added it is already governed by an answer you gave, rather than loading first and asking afterwards.
The answer is kept in your browser's local storage under
attestkeep:cookie-consent, with the date you gave it. It never leaves your
browser and it is not a cookie, so it is never attached to a request and we cannot read
it. Storing it is what saves you from being asked again on every page.
The English and Turkish versions of each page live at their own addresses, so even a language preference does not need to be remembered.
If that ever changes
If we ever add something that stores data on your device — an analytics tool, an embedded video, a support widget — it will not load until the answer above allows it, and this page will list what was added and why before that happens. Until then, this page stays short and the answer governs nothing but itself.
Change your answer
Bring the bar back and answer it again. Clearing your browser's data for this site does the same thing, and then you will be asked once more on the next visit.
Inside the product
The console you install in your own cluster is a different matter. It sets one session
cookie so that signing in works, marked HttpOnly and SameSite,
and marked Secure automatically when the installation is served over TLS.
That cookie is strictly necessary for authentication, it lives on your own domain, and it
never reaches us.
The console stores your view preferences — table or card layout, page size — in your browser's local storage, on the same origin. Nothing in it is shared, and clearing your browser data resets it.