What is the __tawkuuid cookie?
__tawkuuid is an HTTP cookie set by Tawk.to, a live chat widget provider used on many websites for real-time customer support. It appears in the visitor's browser as soon as the Tawk.to script loads on a page, whether or not the visitor starts a conversation.
The cookie is set by the Tawk.to service domain (the widget is embedded by the site owner via an embed script) and stays on the visitor's device for later recognition.
What data it stores
The cookie stores a unique identifier (UUID) generated for the visitor, used to recognize them when they return to the site or navigate between pages during the same chat session. The exact value differs for each visitor and typically does not contain directly identifiable data such as a name or email address.
The data linked to this identifier is sent to Tawk.to's infrastructure to associate messages sent by the visitor with the same conversation and history.
What it is used for
The main purpose is chat conversation continuity: if the visitor closes the widget, browses to other pages on the site, or returns later, __tawkuuid lets the widget recognize the same person and display the message history instead of starting a new conversation every time.
For the site owner, this cookie supports the correct functioning of the chat support tool, giving agents context about returning visitors.
Does it require consent?
Under CookieFix's classification, __tawkuuid falls into the preferences (functional) category. Under Romania's Law 506/2004 (transposing the ePrivacy Directive) and the GDPR, functional cookies that are not strictly necessary for the site's basic operation generally require the visitor's prior consent before being set.
Site owners should declare this cookie in their cookie policy, classify it correctly in the consent banner, and configure their CMP so the Tawk.to widget loads only after consent is given for the preferences category — or provide a clear justification if they consider it strictly necessary (e.g., when chat is the site's only support channel).
How to block or delete __tawkuuid
A visitor can manually delete or block __tawkuuid from their browser settings (Chrome, Firefox, Edge, Safari) — typically under "Privacy and security" > "Cookies and site data," where they can search for the Tawk.to domain and remove the cookie, or block third-party cookies generally.
- For site owners: the Tawk.to script should not load automatically on page load, but only after the visitor gives consent for the preferences/functional category.
- A CMP platform like CookieFix can automatically block the Tawk.to chat script until consent is obtained, removing the need to manually configure each script.
Frequently asked questions
It does not contain sensitive data, only a unique technical identifier used to recognize the visitor across chat conversations. It is not dangerous, but it still requires consent under ePrivacy rules as a non-essential functional cookie.
On the next visit, the Tawk.to widget will treat the user as a new visitor and will no longer be able to show the history of the previous chat conversation.
It is set by the Tawk.to service domain, embedded via the site's widget script, so it functions as a third-party cookie from the host site's perspective.
Yes, any site using the Tawk.to widget must declare this cookie in its cookie policy, including its category, duration, and purpose, regardless of whether it is set automatically or only after consent.