To provide the best possible website experience for our customer, and to provide our customers with relevant quality products and services within our website, we place data files called cookies on your device. This policy provides you with the knowledge regarding cookies and how you can manage them for your experience on our website.
A cookie is a small amount of information sent from our website and stored on a user’s computer by the web browser while the user is browsing the website. Every time a user returns to the website, the website recognizes the stored cookie and sends that visit information about the user’s online activity back to the website.
Cookies can help us create a better user experience for users of our website. They also provide us with insight into how people are using our website, which pages are most visited, and which are not so that we can more effectively align our products and services to meet our website user needs.
|PHPSESSID||guardme.eu||20 Minutes||This is used to register your current session with our server, allowing you to login to your account.|
|_ga||Google Analytics||365 Days||These cookies are used to collect information about how visitors use guardme.eu. We use the information to help us improve our site through the collection of anonymous information (e.g. number of visitors to website and where visitors have come to the site from).|
|_gid||Google Analytics||365 Days|
|inisoftwebchat||guardme website / Inisoft Webchat||15 Minutes||This is used to register your webchat session allowing you to navigate around our website while maintaining the webchat connection|
|ACS_Token||Co-Browse||Session||Avaya Co-Browsing Snap-in provides the option to reconnect to an ongoing session after doing a browser refresh. For an agent browser refresh, Client Data gets synced with agent after reconnecting, while for customer browser refresh, the customer can reconnect to the current session. Using Agent Browser Refresh feature, Avaya Co-Browsing Snap-in stores acstoken in browser cookies for both customer and agent during every Co-Browse session. This token gets stored in the respective browser cookies of the agent and the customer as part of initialization. After the termination of thee session, this cookie gets removed.|