Skip to content

Legal

Cookie notice

Last updated: 4 October 2026

Chronika sets three kinds of cookie, all of them to make the app work. This page lists each one by name.

The short version

Chronika sets only the cookies it needs to work: one to keep you signed in, and two to remember a choice you made. There are no advertising cookies, no analytics cookies and no third-party trackers on the pages we serve.

Because these cookies are needed for something you asked for (signing in, or keeping a setting), they do not usually need consent under cookie rules. If we ever add a cookie that is not strictly needed, we will ask for your consent first.

The cookies we set

Signing in

Sign-in is handled by Auth.js. When you sign in it sets a session cookie, chronika.session-token (on a secure connection its name starts with __Secure-). It holds your signed session so we know who you are, and it lasts up to seven days. Signing in also uses short-lived helper cookies (authjs.csrf-token and authjs.callback-url, and for sign-in with an external provider, authjs.state, authjs.pkce.code_verifier and authjs.nonce) that protect the sign-in itself against forgery.

Light preference

chr_light remembers whether you chose Safelight (the dark bench) or Lights on (warm paper, the default). It is set when you switch, holds the value safe or on, and lasts one year.

Workspace selection

chr_ws remembers which workspace you were looking at, so the app opens where you left it. It holds a workspace identifier and lasts one year.

What we do not set

We do not use advertising cookies, analytics or tracking pixels, and we do not load third-party scripts for them. The Chrome and Windows recorders do not use these cookies: they connect with a personal token instead.

Your control

You can delete or block cookies in your browser settings. If you block the session cookie you cannot stay signed in, and without the other two the app forgets your light and your workspace each visit. Signing out ends your session.

More about how we treat personal data is in the privacy policy.

Questions about this page? Use the contact page.