Cookie consent for live chat: Crisp, tawk.to, Tidio

Live chat, one by one

What matters for consent with Live chat

What our tests found on Live chat

• Set before the choice · Cookie RocksCookie Rocks holds Crisp until the visitor accepts, with no reload

  The loader waits for Accept, then starts on the same page. Nothing is requested after Refuse.

  Seen in our tests, 6 November 2026, Cookie Rocks.

  Full detail

  Cookie Rocks 2.10.0 holds the Crisp 0.49 loader client.crisp.chat/l.js and its inline script before any choice. After Accept, l.js loads and the Crisp API is ready without a page reload. After Refuse, nothing is requested from Crisp. Tested with a placeholder website ID, so the chat window itself was not opened.

• Set before the choice · Crisp - Live Chat and ChatbotThe Crisp plugin loads its chat on every page and shares user details

  For logged-in users it sends their e-mail and name to Crisp, and with WooCommerce the customer's phone, name and addresses. It has no consent setting and sets no cookie itself.

  What to do: Hold both the inline script and l.js until consent.

  Read in its code, 5 November 2026, Crisp - Live Chat and Chatbot 0.49.

  Full detail

  The Crisp plugin enqueues client.crisp.chat/l.js with the WordPress handle crisp (async, footer, version = the current date) on every page, after an inline script that sets CRISP_WEBSITE_ID. For logged-in users that inline script pushes their email and name to Crisp, and with WooCommerce the customer's phone, name and addresses from the session. The plugin has no consent setting, no filter, no WP Consent API and sets no cookie itself; the handle is crisp.

• Good to know · Crisp, Tidio, tawk.toCrisp, Tidio and tawk.to chat scripts are held until consent

  The chat scripts added by the Crisp, Tidio (asynchronous loading) and tawk.to plugins (client.crisp.chat/l.js, code.tidio.co, embed.tawk.to) are held by Cookie Rocks until consent and load after Accept all.

  Seen in our tests, 17 October 2026, Crisp, Tidio, tawk.to 0.48, 8.0.1, 0.9.3.

• Set before the choice · tawk.to Live Chattawk.to loads its chat on every page and passes logged-in users' e-mail

  With visitor recognition on (default), a logged-in user's name and e-mail address go to tawk.to when the chat loads. No consent setting, no filter and no WP Consent API support.

  Read in its code, 16 October 2026, tawk.to Live Chat 0.9.3.

  Full detail

  The tawk.to plugin prints an inline footer script (id tawk-script) that creates the async embed.tawk.to script itself, on every page by default. With visitor recognition on, which is the default, Tawk_API.visitor carries a logged-in user's name and e-mail address in the HTML, sent to tawk.to when the widget loads. The plugin has no consent setting, no filter of its own and no WP Consent API support.

• Depends on a setting · tawk.to Live Chattawk.to Secure Mode sets a PHP session cookie from the server

  setting “Secure Mode JavaScript API key” · by default: empty

  With visitor recognition on (default) and a Secure Mode key saved, the plugin starts a PHP session on every request. No consent banner can hold this cookie.

  Read in its code, 16 October 2026, tawk.to Live Chat 0.9.3.

  Full detail

  When visitor recognition is on (the default) and a JavaScript API key is saved for Secure Mode, the tawk.to plugin calls session_start() on init for every request, closing it at once for visitors who are not logged in. This sets a PHP session cookie from the server, which no consent banner can hold.

• Set before the choice · TidioTidio opens a connection to its server before any choice, even when held

  setting “tidio-async-load” · by default: on

  • A preconnect link to code.tidio.co is on every page, with no setting to remove it.
  • Its script waits for the page load event, so when released after consent it never ran.
  • Cookie Rocks 2.5.0 runs it at once; the chat starts after Accept all without a reload.
  • The chat keeps the visitor ID and its state in local storage (tidio_state_*).

  Read in its code, 16 October 2026, Tidio 8.0.1.

  Full detail

  The Tidio plugin adds a preconnect link to code.tidio.co in the head of every page once connected, with no setting or filter to remove it, so the browser opens a connection to Tidio before any choice even when the chat is held. In asynchronous mode (on by default) its inline footer script waits for the page load event to create code.tidio.co/<key>.js, so a script released after consent never ran. Cookie Rocks 2.5.0 runs such a wait at once when the page has loaded, and the chat starts after Accept all without a reload. The chat keeps the visitor ID and its state in local storage keys tidio_state_*.

Chat and messaging

Other plugins of the same kind.

Every plugin and theme we test →