Cookies
Last updated 30 September 2026
Chime Bee only uses cookies that are strictly necessary for it to work: to keep you signed in, to keep a guest connected to their stay, to protect forms, and to remember a language choice. There are no advertising, analytics or tracking cookies, and none from other companies, so there is nothing to accept or reject.
| Cookie | What it's for | How long |
|---|---|---|
| authjs.session-token (or __Secure-authjs.session-token) | Keeps a team member signed in. | Up to 30 days |
| authjs.csrf-token, authjs.callback-url | Protect the sign-in form against forged requests. | The browser session |
| ow_login_challenge | Remembers, for a few minutes, that the password was right while you enter your two-step code. | 5 minutes |
| oneweb_guest_session | Keeps a guest connected to their stay, so they can send requests. | Until checkout |
| oneweb_lang | Remembers the language a guest chose. | 1 year |
If you block these cookies in your browser, signing in and guest services won't work.
Counting visitors, without cookies
On Chime Bee's own public pages (the home page, prices, demo, sign-up and help) we count visits without any cookie or outside tracker: the page, the website that sent you, your country, and a code made from your IP address and browser that changes every day, so we can tell how many different people visited but can't follow anyone from one day to the next. Nothing is counted inside a workspace or on guest pages. Counts are kept for about 13 months.
Chime Bee · chimebee.hq@gmail.com