What are tawk.to cookies and what do they do?

The tawk.to widget uses several types of cookies to help you communicate more effectively with your customers. We also store temporary data.

Website cookies are small snippets of data shared with site visitors and stored in their computer drives when they land on web pages. 

Cookies save you time by keeping you logged in to your favorite websites, recognizing you when you return, and displaying languages based on your location.

They enable you to adjust widget greetings for time zones. They even allow you to share special offers based on specific page visits.

Just like home-baked cookies, web cookies don’t last forever. The expiry time dictates how long they are stored or shared.

Let’s take a quick look at what they do and why they are important.

The tawk_uuid_propertyId cookie tracks unique visitors to a website. It uses Universally Unique Identifiers (UUIDs) made up of randomly generated 128-bit numbers. This cookie is dynamic and changes based on property ID values. 

To view your property ID, select Select the ⚙️Administration (gear) icon in the upper tab menu. You’ll find it under Property ID in the Overview panel.

The first time you visit a website, the website’s server generates a unique code and sends it to be stored on your computer as a cookie.

The tawk_uuid_propertyId cookie does not store your personal details. However, it can help websites remember your preferences and create a more personalized user experience.

When you log into a website with your name and email. Your credentials are verified and a session ID is created, which is sent to your computer in a session cookie (ss). That way, you don’t have to log in every time you visit the page.

Session cookies don’t contain any personal data. The data is not shared, and no third parties could access or identify you even if they did view the information in the cookies.

After you log out or close the browser, the session cookie is automatically deleted.

When a visitor opens a page from a website and our widget is already appearing in multiple browser tabs on that site, the TawkConnectionTime cookie manages requests to load the widget simultaneously

The twk_idm_key cookie is a session cookie that is added only if no twk_uuid is found. It is destroyed once the page is closed. Its purpose is concurrency control. If multiple pages are open at the same time, then multiple connection requests will be made at the same time. A unique identifier is generated to lock a page from making the connection first. Once a connection is made, it will release the lock and the rest of the pages will then be able to make the connection.

Preference cookies tailor the visitor experience on your website by remembering details such as preferred language or video player settings.

While it’s possible to block all cookies in your browser, some features in tawk.to will only function correctly with cookies. Our goal is to continually improve your experience on our site.

The token twk_token_5cc820b82846b90c57ac2bd8 is held in localStorage.

The following are used for local storage and are set by the navigator.locks plugin:

• $navigator.locks-requestQueueMap
• $navigator.locks-clientIds
• $navigator.locks-heldLockSet

$navigator.locks-* data is stored only once and then removed. It acts as a lock on a resource, so if there are multiple tabs open and they all display the widget, priority is given to the first connection made. This only happens if the visitor is connecting to the first (no cookie with uuid found)

PreviousNav is used for Session storage. Both Session storage and cookie data are removed when a tab is closed.

If a website has enabled a consent form for the chat widget, then no cookie will be added until the visitor submits the consent form. If no consent form is enabled, the cookie will be stored without consent.

Learn more about how we use cookies in our Privacy Policy.

Need help? Chat with our support team or schedule a call.