Cookies and Data Collection

This page lists the cookies and data collected by Inbenta products and Help portals. This information is updated regularly as products evolve.

Developers Portal

There are no cookies from the Developers Portal itself.

Provider Name Type Reason
GitHub _octo, logged_in,
_gh_sess,
has_recent_activity
Technical Needed to add preview code snippets hosted in GitHub
Google _ga, _gat, _gid Technical Saves the information regarding the use of the website.
(More info)
Cloudflare __cfduid Technical Client security
(More info)

Help Center

Provider Name Type Reason
Inbenta SSINB, LSSINB Technical Cookies that authenticate the user inside the Inbenta system.
Google _ga, _gat, _gid Technical Saves the information regarding the use of the website.
(More info)
Cloudflare __cfduid Technical Client security
(More info)

Chatbot

The Chatbot SDK does not use cookies. However, it does use local storage. If the Chatbot escalates to HyperChat, it uses the HyperChat cookie (see below). 

The Chatbot App does not use cookies. However, it does use accounts, and accounts uses cookies both to log in the user and to maintain the logged-in session. 

Knowledge Management

The KM SDK collects the following data. 

Provider Name Type Reason
Inbenta inbenta-km-session-id Technical Stores the session id so that all actions of the user are related to the same session.
Inbenta inbenta-km-session-token Technical Stores the session token so that all actions of the user are related to the same session.
Inbenta XSRF-TOKEN Technical Security cookie to avoid malicious exploits of a website where unauthorized commands are transmitted from a user that the web application trusts.
Inbenta api_token Technical Stores the API token in order to avoid requests to the API while the token is valid.
Inbenta laravel_session Technical Handles the user session in the application.
Inbenta (Dynamically generated) Technical Stores relevant information for the app avoiding requests to the backend and improving the performance of the app.
Inbenta laravel_session Technical Handles the user session in the application.
Inbenta (Dynamically generated) Technical Stores relevant information for the app avoiding requests to the backend and improving the performance of the app.

Search

Search does not use cookies.

Case Management/HyperChat

The HyperChat SDK collects the following data. 

Note: Also collected by Chatbot upon Chatbot escalation to HyperChat.

Provider Name Type Reason
Inbenta i.cc Technical Authenticates the user in the live chat. This cookie is created when  chat session is started and removed when the chat session is closed.