Cookie policy

This page explains the cookies and similar storage Kalsenti uses in your browser, why we use them, and how you can control them.

Last updated 6 November 2026 · Version 1

Contents

Who we are

This site is run by Kalsenti Limited. In this policy, “we” and “us” mean Kalsenti Limited.

Kalsenti Limited is a company registered in England and Wales, company number 17555690. Registered office: 82a James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE.

Cookies and similar storage

Cookies are small files a website asks your browser to keep. Websites can also keep information in your browser in other ways, such as local storage, session storage and IndexedDB. The same rules apply to all of them, so this policy covers them all.

What we use

We only use storage that the site needs to work, or that remembers a choice you’ve made. We don’t use analytics or advertising cookies, and no other company sets cookies or storage on our pages.

Strictly necessary · Strictly necessary storage doesn’t need your consent, but we still have to tell you about it.

Preferences · Your theme, language and layout choices are only kept between visits if you allow it. If you don’t, the choices you make are kept in session storage until you close the tab, so the site can do what you asked.

  • kalsenti.session_token
    Type
    Cookie
    Set by
    Kalsenti
    Purpose
    Keeps you signed in, so each page knows it’s you.
    Category
    Strictly necessary
    How long it lasts
    7 days, renewed while you use the site. Deleted when you sign out.
  • kalsenti.state
    Type
    Cookie
    Set by
    Kalsenti
    Purpose
    Protects signing in with GitHub or Google against forged requests. Only set when you choose one of them.
    Category
    Strictly necessary
    How long it lasts
    5 minutes
  • kalsenti.two_factor
    Type
    Cookie
    Set by
    Kalsenti
    Purpose
    Remembers that your password was accepted while we ask for your two-factor code. Only set if you use two-factor authentication.
    Category
    Strictly necessary
    How long it lasts
    10 minutes
  • kalsenti-consent
    Type
    Cookie
    Set by
    Kalsenti
    Purpose
    Remembers your cookie choices, so we don’t ask on every page.
    Category
    Strictly necessary
    How long it lasts
    6 months
  • kalsenti-tour
    Type
    Session storage
    Set by
    Kalsenti
    Purpose
    Lets a tutorial you’ve started carry on after you come back from adding credit.
    Category
    Strictly necessary
    How long it lasts
    Until you finish the tutorial or close the tab
  • kalsenti-chat
    Type
    IndexedDB
    Set by
    Kalsenti
    Purpose
    Used by private chats. Keeps your chat key on this device if you ask it to remember it, and details your browser uses to check your private chats.
    Category
    Strictly necessary
    How long it lasts
    Until you choose to forget this device, start over, or clear your browser’s site data
  • kalsenti-themekalsenti-languagekalsenti-models-view
    Type
    Local storage or session storage
    Set by
    Kalsenti
    Purpose
    Remember the theme, language and model list layout you choose. Only set when you make one of these choices.
    Category
    Preferences
    How long it lasts
    With your consent, until you change it or withdraw consent. Without it, until you close the tab.

On our live site, the names of the sign-in cookies start with __Secure-, which tells browsers to send them only over secure connections.

Changing your choice

You can change or withdraw your consent at any time. Open Cookie settings from the bottom of any page, or from Settings in your dashboard. If you withdraw consent, we delete preferences storage from your browser straight away, and your current choices only last until you close the tab.

Your browser also lets you see, delete and block cookies and other site storage. If you block strictly necessary cookies, you won’t be able to sign in.

Other companies

Some things you do take you to another company’s site, which uses its own cookies under its own policy. We don’t control those cookies.

  • Stripe, when you add credit. You pay on Stripe’s own checkout page, and we don’t load Stripe on our pages.
  • GitHub or Google, if you choose to sign in with one of them.

Changes to this policy

We’ll update this page if the storage we use changes. If a change needs your consent, we’ll ask you again.

Contact us

If you have a question about this policy, email us: [email protected]