Cookie policy
Chronik.io uses no tracking cookies and no analytics cookies, and shows no cookie banner. This page is short because there is little to say, and it exists so that the absence is stated rather than merely implied.
The only cookies there are
None of them is read by anyone but this site, and none of them follows you to another one.
Set on every visit, because the site cannot work without them
| Cookie | What it does | How long |
|---|---|---|
| Session cookie | Keeps you signed in between requests | Until you sign out or the session expires |
| CSRF token | Protects forms against cross-site request forgery | For the session |
Set only after you do something that asks for it
| Cookie | What it does | How long |
|---|---|---|
| Remembered sign-in | Only if you asked to stay signed in | Until it expires or you sign out |
| Sign-in duration | Only if you changed how long you stay signed in. It carries that choice per device, because the session's clock is set before we know who you are | Five years, or until you set it back to the default |
| Language choice | Only if you picked a language yourself. Keeps the site in that language on your next visit instead of guessing again from your browser | One year, or until you choose another |
| Shared changelog access | Only if you entered the passphrase for a changelog somebody shared with you. One cookie per changelog, so unlocking one never unlocks another | Thirty days |
And one that is not a cookie
| Entry | What for | How long |
|---|---|---|
wirekit-theme in localStorage |
Only if you picked light or dark yourself. Keeps that choice for your next visit instead of following your operating system again | Until you pick "follow the system" again — then the entry is deleted |
⚠️ It is listed because § 25 TDDDG does not speak of cookies but of storage on your device — and
a localStorage entry is covered just the same. Leaving it out because it is technically not a
cookie would have made this page enumerate by technology rather than by subject.
It is created only when you use the switch. Somebody who never touches it gets nothing written: the default, "follow the system", is the absence of the entry rather than a value stored in it.
The four in the second group do not exist until you act, so a first visit sets only the two above them. The language and duration cookies hold a plain short value — a two-letter language code, a number of minutes — and both are checked against a fixed list of allowed values when written and again when read. The changelog cookie is encrypted and bound to this installation, so it cannot be read or moved to another one.
Everything listed — the cookies and the localStorage entry — is strictly necessary to provide
a service you asked for, so § 25 (2) TDDDG applies and no consent is required. Refusing them means the service cannot sign you in, cannot
keep the language or the sign-in duration you chose, and cannot remember that you already
entered a changelog passphrase.
Why there is nothing else
Page views are measured server-side, on our own Matomo instance, from the request that already happened. No analytics script runs in your browser, and the measurement stores nothing on your device — no cookie, no entry, nothing that recognizes you again. What does land on your device is listed in full in the three tables above. The privacy policy explains that in context, along with everything else Chronik.io does with personal data.