To ensure the functionality of our software, we save cookies about the application status in the end-user's browser. These cookies are technically essential and will populate data only when the chat is being used. Before that their only function is to offer the chat service.
The Userlike Messenger creates a cookie:
In addition to the technical details of the widget status and messenger status, it contains IDs of existing contacts so they can be recognized when visiting again ("reauth", "uuid", "token").
We also use a LocalStorage variable of the same name, it contains technical information about the widget's status, and the number of page impressions and page visits ("page_impressions", "visits").
For our Legacy version:
Userlike Session Cookie: uslk_s
To ensure the functionality of our software, we save cookies about the application status in the end-user's browser. These include the persisted state, machine state, session ID as well as chat statistics. These cookies are deleted at the end of the browser session.
("app_state", "id", "duration", "client_terminating", "client_originating", "chat_meta_id")
In our Unified Messaging version the cookie's name is "uslk_umm_xxxxx_c" - the x are your Widget ID.
Userlike Expire Cookie: uslk_e
To allow the identification of end-users when they return to your website, we save cookies containing user information in the end-user's browser. Each of these can contain an individual user ID, the name of the end-user, the email-address and the number of visits. By default, these cookies are stored for one year, however, you can change this setting in your Widget Configurator at any time.
("uuid", "blocked", "client_name", "client_email", "client_additional01_value", "client_additional02_value", "client_additional03_value", "visits")
In our Unified Messaging version the cookie's name is "uslk_umm_xxxxx_s" - the x are your Widget ID.