Last updated10 September 2026
Cookies
Citerra sets cookies for two purposes: keeping you signed in, and remembering the language and time zone you chose. It runs no analytics, no advertising and no cross-site tracking. This page names every cookie set, says what is not set, explains why there is no consent banner, and says how to control them. A final section names the governing language.
§ 1
What Citerra sets
The first three cookies maintain your sign-in session. Blocking them signs you out and prevents sign-in. Clerk sets them and stores no personally identifiable information in them by default. The last two are set by Citerra and hold a language code and a time zone name, nothing else.
Reading citerra.de sets no cookie until you open it in a language other than your browser's, by the menu or by a link; the marketing site neither reads nor mints a session. The application sets the same language cookie when you sign in, and a time zone cookie so dates render in your zone.
| Cookie | What it does | How long |
|---|---|---|
| __client | The client token. A signed token on clerk.citerra.de holding a client id and a rotating anti-fixation token, from which each host mints its own session. HttpOnly, and never readable by the page. | 7 days, the session lifetime Clerk applies |
| __session | The session token for one host. A short-lived signed token carrying your user id, refreshed from the client token as you browse. | Under a minute, then refreshed |
| __client_uat | Says whether a session probably exists, so a page can decide whether to attempt a handshake before it renders. Carries a timestamp and nothing else. | Until you sign out |
| NEXT_LOCALE | The interface language you chose, on citerra.de and in the application, so both open in it. Holds a two-letter language code. | 1 year |
| tz | The time zone your browser reports, so the application renders dates in it. Set on app.citerra.de only. | 1 year |
§ 2
What Citerra does not set
No analytics cookies, no advertising cookies, and no cross-site tracking. This website loads no tag manager and no third-party script.
Session replay is switched off on the editor, because a replay of the writing surface would record an unpublished paper keystroke by keystroke. Error reports carry a stack trace with personal data removed.
The application remembers interface choices such as the theme and panel sizes in your browser's local storage. After a failed save, it also keeps the unsaved manuscript draft for up to 30 days, separated by user and organization and cleared on sign-out. This data never leaves your device and is not a cookie.
§ 3
Why there is no banner
Consent is required for cookies that are not strictly necessary (§ 25 (1) TDDDG). The cookies listed here are strictly necessary to provide the sign-in, the language and the time zone you asked for. § 25 (2) no. 2 TDDDG exempts them from consent, so no consent banner appears.
If Citerra ever adds an analytics or marketing cookie, this page gains a group for it and a preferences dialog appears. The decision is stored and can be revoked. That change would be announced before it takes effect.
§ 5
Governing language
This page is published in English and in German, and both versions describe the same cookies.
The English version governs until counsel has reviewed both texts. Where the two differ before that review, the English wording applies.