Home / Legal / Cookies
Right now this site stores one thing: the colour palette you chose, in your browser's own memory. No cookies, no analytics, no trackers. Below is the full account of that.
last updated: draft
The text describes the site as it stands today. When analytics or session management comes in, this page and the consent flow will be updated together. This notice is drafted under the law of the Republic of Türkiye — read together with KVKK (Turkish Personal Data Protection Law No. 6698) — and the English version is a convenience translation; where the two differ, the Turkish text governs.
A cookie is a small text file that a website saves to your browser and can read back on later visits. Similar technologies include localStorage and sessionStorage, which hold data in browser memory, as well as tracking tools such as pixels and tags. In this text the word "cookie" is used broadly enough to cover those similar technologies.
The marketing site is static: there is no build step, no server-side session and no user account. This site writes no cookies. The only value stored is the preference set by the palette picker in the bottom right, and it stays in your browser's localStorage — it is not sent to the server and not shared with third parties.
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
| kaldera-palette | localStorage | Remembers the colour palette you chose, so the theme does not shift when you change page. | Until you delete it |
That single row is the whole site. No other storage key, cookie or tracker is used.
No analytics are in use today. There is no page view counter, no heatmap, no session recording and no ad pixel. If product analytics are introduced later, a self-hosted tool will be preferred and this section will be filled in with the tool's name, the fields stored and their lifetimes.
Not used, and not planned. No data is transferred to third-party ad networks.
The product console is a separate application and currently runs only on a local development address. When the console goes live, a necessary session cookie will be used to keep the session; the plan is for that cookie to be HttpOnly and SameSite=Lax, running on our own identity database. Sign-in is not possible without the session cookie, so it rests on delivering the service rather than on consent. When the console goes live, this section will be updated with the real cookie names and lifetimes.
Storage that is necessary or functional does not require separate consent; it is required for the site to work and does not serve to identify a person. When analytics or any similar optional technology is added, a consent banner will offer an explicit choice on page load, no optional technology will run until that choice is made, and consent will always be withdrawable. We do not show such a banner today, because we do not run anything that requires consent.
The page pulls its typefaces from a font distribution service. That request passes your browser's IP address to the service; it writes no cookie. Serving the fonts from our own server is under consideration, and this page will say so when that change is made.
To the extent the technologies described here lead to the processing of personal data, the purposes, legal grounds, retention periods and data subject rights are set out in the Privacy and KVKK Disclosure Notice.
This text is updated whenever storage behaviour on the site or in the console changes. The update date appears at the top of the page; today's state is marked "draft".
Legal
The less we store, the less we have to explain. The day we add analytics, we will do it by announcing it and asking for consent.
Draft text; not in force.