What is the ss cookie?
The ss cookie is placed by Tawk.to, a live chat service website owners embed to communicate with visitors in real time. It's set on the .tawk.to domain, meaning it comes from a third-party provider rather than the site itself.
It appears as soon as the Tawk.to script loads on the page, typically alongside the chat widget visible in the corner of the screen, regardless of whether the visitor starts a conversation.
What data it stores
The ss cookie stores technical information related to the current chat widget session, most likely a session identifier used to maintain the connection between the visitor and Tawk.to's servers. The exact value format isn't publicly documented, and CookieFix does not invent technical details it cannot verify.
The data is sent to Tawk.to's infrastructure and used for the technical operation of the chat, not for advertising tracking.
What it is used for
The cookie's purpose is strictly technical: it keeps the chat session active for the duration of the visit, so the widget works correctly (opening the window, sending/receiving messages, reconnecting after a page reload).
For the site owner, this cookie is part of the infrastructure that enables live support for visitors, with no analytics or marketing role.
Does it require consent?
Since it's a session cookie directly tied to the operation of the chat widget (a feature the visitor actively requests simply by using the chat), the ss cookie generally falls under the strictly necessary category. Strictly necessary cookies don't require prior consent under Article 5 of the ePrivacy Directive (implemented in Romania via Law 506/2004), but they still need to be disclosed in the site's cookie policy.
- The site owner should list the "ss" cookie and the Tawk.to provider in the cookie policy.
- If the chat widget is configured to collect additional data (e.g. contact forms, conversation analytics), it's worth checking separately whether other Tawk.to cookies require consent.
How to block or delete ss
A visitor can delete the cookie from browser settings (Chrome, Firefox, Edge, Safari – site data/cookie management section) or block the tawk.to domain using a third-party script blocker extension. Deleting it will temporarily stop the chat widget from working until a new session starts.
For site owners wanting centralized control, a CMP like CookieFix can automatically block the Tawk.to script until the visitor makes a cookie choice, even though this specific cookie is typically classified as strictly necessary.
Frequently asked questions
Generally no, since it's strictly necessary for the chat widget the visitor is actively using. It still needs to be disclosed in the cookie policy.
It's a session cookie, so it's automatically deleted when the visitor closes the browser or the browsing session ends.
The Tawk.to chat widget may not work correctly, or the conversation may not stay active during the visit.
Yes, Tawk.to may set several cookies for the chat to function; each should be evaluated separately by its purpose for correct classification in the cookie policy.