Last updated on: 15 July 2026

This policy describes how Crisp IM SAS ("Crisp", "we", "us") uses cookies and similar technologies on crisp.chat and how the Crisp chatbox uses cookies on websites operated by our customers.

For how we process personal data more broadly, see our Privacy Statement.

Cookies on crisp.chat

When you visit crisp.chat, our cookie banner lets you accept or refuse cookies by category (strictly necessary, functional, statistics, and marketing), in line with the table below.

You can reopen the banner at any time via Cookie settings in the website footer.

Cookie Name	Provider	Category	Purpose	Domain	Expiry	HttpOnly	Secure	SameSite
`crisp_cookie_consent`	Crisp	Strictly Necessary	Stores your cookie preferences so we can apply your choices and keep non-essential services disabled when refused	`crisp.chat`	180 days	No	No	Lax
`crisp-client-session-*`	Crisp	Strictly Necessary	Maintains the visitor's chat session identifier across the website	`*.crisp.chat`	6 months	No	No	—
`crisp-client-*`	Crisp	Strictly Necessary	Manages the WebSocket connection state for the live chat widget	`*.crisp.chat`	Session	No	No	Lax
`i18n_redirected`	Crisp	Strictly Necessary	Stores the user's language preference to avoid repeated redirects	`*.crisp.chat`	~1 year	No	No	Lax
`g_state`	Google (Auth)	Strictly Necessary	Tracks Google Sign-In state for authentication within the Crisp app	`*.crisp.chat`	Session	No	Yes	None
`shared_profile`	Crisp	Functional	Lets us prefill profile information for logged-in Crisp users when they interact with website forms or chat features	`*.crisp.chat`	Varies	No	Yes	Lax
`ph_phc_`	PostHog	Analytics	Tracks device ID and user behaviour for product analytics	`*.crisp.chat`	~1 year	No	Yes	Lax
`_gcl_au`	Google Ads	Marketing	Measures ad conversion efficiency by linking ad clicks to site actions	`*.crisp.chat`	3 months	No	No	—
`_fbc`	Meta	Marketing	Stores Facebook click identifier for ad attribution and retargeting	`*.crisp.chat`	90 days	No	Yes	Lax
`_fbp`	Meta	Marketing	Identifies browsers for Facebook advertising and analytics	`*.crisp.chat`	90 days	No	Yes	Lax
`li_fat_id`	LinkedIn	Marketing	LinkedIn first-party ad tracking identifier for conversion measurement	`*.crisp.chat`	30 days	No	Yes	—
`bcookie`	LinkedIn	Marketing	Browser identifier for LinkedIn advertising and analytics	`*.linkedin.com`	1 year	No	Yes	—
`lidc`	LinkedIn	Functional	Facilitates data centre selection for LinkedIn services	`*.linkedin.com`	1 day	No	Yes	—

Third-party video providers may also set cookies or use similar technologies after you accept functional cookies and load their players. YouTube and Vimeo cookie names, purposes, and retention periods are controlled by those providers and may change over time. Review their policies for more information:

YouTube / Google: Google Privacy Policy
Vimeo: Vimeo Privacy Policy

Cookie banner categories map to this policy as follows:

Strictly necessary — Crisp chat session cookies, locale preference (i18n_redirected), and Google Sign-In state (g_state).
Functional — preference and personalization features such as logged-in profile prefill (shared_profile) and third-party video players from YouTube or Vimeo (loaded only after consent).
Statistics — PostHog product analytics (ph_phc_) and Plausible analytics (loaded only after consent).
Marketing — Google Ads (_gcl_au), Meta (_fbc, _fbp), and LinkedIn (li_fat_id, bcookie, lidc) tags loaded via Google Tag Manager after consent.

You can review and change your preferences at any time via the cookie banner or Cookie settings in the footer. When you withdraw consent for a category, we stop loading the related services and clear related first-party cookies where technically possible. Some third-party cookies can only be cleared from your browser settings or by the third-party provider.

Affiliate referral (`track` URL parameter)

When you arrive via an affiliate link (?track=…), we store that identifier in session storage (not a cookie) for the current browser tab only if you accept marketing cookies, so we can forward it to our signup flow if you create an account. It is deleted when you close the tab or reject marketing cookies.

Under EU rules, affiliate attribution is generally not treated as “strictly necessary”; we avoid a persistent affiliate cookie on crisp.chat and only pass the referral at signup. If you do not want this, do not use affiliate links or close the tab before signing up.

Crisp chatbox cookies

The Crisp chatbox, running on the websites of our users, uses cookies solely as follows:

Cookies are necessary for chatbox functionalities; they restore the chat session and messages of a chatbox user when browsing between website pages and/or when returning to the website days later.
Cookies have a default expiration time of 6 months, which is renewed when the user returns to the website and loads the chatbox.
Cookies bind a user to a single session. If that session contains messages, it is permanent (unless deleted by a website agent); otherwise the session is temporary and is destroyed 30 minutes after the last website access.
Cookies are not used for tracking purposes. They bind a user to server-side session storage used for messaging when either the user or a website agent starts a conversation.
The user IP address is stored in the server-side session storage bound to the cookie. If the user leaves without using the chatbox messaging features, the session (and thus the IP address) is automatically removed from Crisp servers upon session expiration (30 minutes after last access).
The user IP address may be retained when the user started a chat session with a website on Crisp. We are legally required under French law to retain such logs for a minimum of one (1) year when required by authorities. We may retain IP addresses longer to protect our chatbox service against botnets and spam.

On customer websites, the chatbox sets cookies with the same naming pattern as in the table above (crisp-client-session-*, crisp-client-*), scoped to the website domain where the widget is embedded.

Managing cookies

On crisp.chat: use the cookie banner or your browser settings.
On a website using Crisp: you may withdraw chatbox cookies via your browser. End users should also review the privacy and cookie information published by the website operator.