What is the twk_uuid_ cookie?
twk_uuid_ is an HTTP cookie created by the Tawk.to live chat script, a popular messaging and support tool used on websites. The cookie name is not fixed: the twk_uuid_ prefix is followed by a string that identifies the specific property (site) registered in the site owner's Tawk.to account.
The cookie appears in the browser as soon as the Tawk.to chat widget loads on the page, regardless of whether the visitor opens the chat window, because the script needs a unique session identifier from the moment it renders.
What data it stores
The cookie stores a unique identifier (UUID) assigned to the visitor or chat session, used by Tawk.to to link messages to the same person across visits or page reloads. The value is an alphanumeric string generated by the platform and has no direct link to identifying data such as name or email, unless the visitor enters those voluntarily in the chat.
Data associated with this identifier is sent to Tawk.to's servers for processing and to display the conversation in the operator's dashboard.
What it is used for
From the site owner's perspective, twk_uuid_ lets the chat widget recognize returning visitors and preserve conversation history, so a support agent can see prior context without asking the user to reintroduce themselves. For Tawk.to, this cookie is essential to the basic functioning of the messaging service — routing messages, assigning conversations, and showing agent online/offline status.
Does it require consent?
CookieFix classifies twk_uuid_ under preferences (functional), since it is not strictly necessary for the site's core operation (the site still works without chat), but supports a feature the site owner chose to offer visitors. Under GDPR and the ePrivacy Directive (transposed into Romanian law via Law 506/2004), cookies in this category require the visitor's prior consent before being placed.
Site owners must declare this cookie in their cookie policy, include it under the appropriate category in the consent banner, and make sure the Tawk.to script does not load before the visitor gives consent.
How to block or delete twk_uuid_
A visitor can delete or block this cookie from browser settings (Chrome, Firefox, Edge, and Safari all allow deleting per-site cookies or blocking third-party ones), though this may affect the chat widget, which could lose conversation continuity.
At the site level, the owner must ensure the Tawk.to script does not fire automatically before consent. A CMP such as CookieFix can automatically block the Tawk.to script from loading until the visitor accepts the relevant cookie category, preventing the cookie from being set without authorization.
Frequently asked questions
It is a cookie set by the Tawk.to live chat widget to uniquely identify a visitor or chat session on a site using this service.
Yes, since it is classified as preferences/functional, it requires the visitor's prior consent under GDPR and ePrivacy rules.
Its typical duration is around 6 months, after which it expires automatically from the browser.
By using a consent management platform that blocks the Tawk.to script from loading until the visitor accepts the corresponding cookie category.