Citerra · on writingCookies
Citerra markCiterra
productpricingupdates
FAQssecurity
contact
EnglishDeutsch
sign injoin the waitlist
productpricingupdatescontact
sign in
resources
FAQssecurity
Language
EnglishDeutsch

Last updated8 September 2026

Cookies

Citerra sets cookies for one purpose, which is keeping you signed in. 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.

On this page

  1. § 1What Citerra sets
  2. § 2What Citerra does not set
  3. § 3Why there is no banner
  4. § 4Controlling cookies
  5. § 5Governing language

Questions about cookiescontact@citerra.de

§ 1

What Citerra sets

These 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.

Nothing is stored on your device until you sign in to the app. Reading citerra.de sets no cookie at all, signed in or not: the marketing site neither reads nor mints a session.

CookieWhat it doesHow long
__clientThe 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
__sessionThe 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_uatSays 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
__clerk_db_jwtDevelopment only. Keeps a session in step between localhost and the Clerk development domain. It is never set on citerra.de.Development sessions only

§ 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 the panel sizes in your browser's local storage. That 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. The cookies listed here are strictly necessary, 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.

§ 4

Controlling cookies

Every browser can block or delete cookies for a site, and signing out clears the session cookies. Blocking them prevents sign-in entirely.

Deleting the organization removes everything stored alongside it, as described in the privacy policy.

§ 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.

Citerra markCiterra
Everything the paper needs.
resourcesproductpricingupdatesFAQs
companycontactsecuritystatus
toolsCiterra for web
legalimpressumtermsprivacysubprocessorscookiesdata processingopen source
communityXLinkedInInstagramDiscord
  • GDPR
  • EU hosted
  • No model training
  • Export anytime
  • English
  • Deutsch
© 2026 Citerra · made for academic writing