What is the crisp-client/session/ cookie?
The crisp-client/session/ cookie belongs to the family of cookies set by Crisp, a live chat and messaging service used by websites for customer support and sales conversations. The full cookie name includes, after this prefix, a unique website ID assigned by Crisp to the specific site.
The cookie is created by the Crisp script (crisp.chat) in the visitor's browser, typically the first time the chat widget loads on a page, whether or not the visitor actually opens the chat window.
What data it stores
The cookie stores a session identifier that Crisp uses to link the visitor to a conversation and to chat interface preferences, such as whether the chat window was open or minimized. The exact value format is not publicly documented and may vary; it should not be manually interpreted.
Data is sent to Crisp's servers (crisp.chat / relay.crisp.chat), which may process additional information such as conversation history, the current page, and technical browser data, depending on the site's Crisp account configuration.
What it is used for
For the website — it keeps a chat conversation active as the visitor moves between pages, so they don't lose the conversation history or need to restart the chat from scratch.
For Crisp — it ensures messaging session continuity, links messages from the same visitor across return visits, and supports features like notifications, operator routing, and automated chatbots.
Does it require consent?
CookieFix classifies crisp-client/session/ as preferences (functional). It is not generally considered strictly necessary under ePrivacy, since the site's core functionality does not depend on the chat widget.
- Under Romania's Law 506/2004 (transposing the ePrivacy Directive) and the GDPR, setting this cookie requires the visitor's prior consent, obtained through the cookie banner.
- Site owners must disclose the cookie in their cookie policy and ensure the Crisp widget does not load before consent if the visitor hasn't accepted the relevant category.
- If a site wants the chat bubble visible before consent without setting the session cookie, it should confirm with Crisp whether the widget can run in a cookie-less mode.
How to block or delete crisp-client/session/
A visitor can delete or block this cookie through browser settings (e.g., clearing cookies for the site's domain or blocking third-party cookies), though this may interrupt the Crisp chat widget for that session.
At the site level, administrators should not let the Crisp script run automatically on page load. A consent management platform like CookieFix can automatically block the Crisp script until the visitor consents to the preferences category, preventing the cookie from being set without agreement.
Frequently asked questions
It's a cookie set by the Crisp live chat widget to maintain a chat conversation as the visitor browses the site.
No, it's not a harmful cookie; it's a functional cookie that supports live chat, but it must still be set in compliance with consent rules.
Yes, prior consent is generally required since it's classified as preferences/functional rather than strictly necessary.
Its typical duration is 6 months, after which the browser removes it automatically unless renewed by a new visit or chat interaction.