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. All cookies used by Inbenta are strictly necessary for the solutions to work correctly and do not store or track any personal information. Therefore, are excluded from user acceptance in terms of GDPR.

Developers Portal

There are no cookies from the Developers Portal itself.

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

Chatbot

The Chatbot SDK does not use cookies. If the Chatbot escalates to HyperChat, it uses the HyperChat cookie (see below). When possible the Chatbot SDK uses one type of “localStorage” called Indexed DB. The key of the IndexedDB storage is determined by the Chatbot Identifier (See SDK Configuration). See below the Indexed DB storage created by the Chatbot SDK:

Provider Name Type Reason
Inbenta accessToken Technical Access token is stored to maintain the authorization with the Chatbot API
Inbenta accessTokenExpiration Technical To know when the access token is going to expire in order be able to refresh it.
Inbenta avatar Technical

Contains the bot state for the current session

  • Positioning
  • Information about video avatar
  • If the bot is minimized
  • Conversation history to restore the messages in the conversation window
  • Hyperchat configuration (agentName and agentIcon)
  • Chatbot input status (disabled or not)
  • If the user is in the process of closing the bot
  • Guest name and avatar name (if set - defaults to: “You”)
Inbenta chatbotUrl Technical Endpoint of the Chatbot API that should be used
Inbenta chatbotUrlExpiration Technical Expiration date of the chatbotUrl
Inbenta sessionExpiration Technical Expiration date of the session
Inbenta sessionId Technical Chatbot session identifier
Inbenta sessionToken Technical Session token to maintain the session with the Chatbot API.
Inbenta sideBubble Technical Configuration of the side window to be able to re-render it
Inbenta actionFieldEvents Technical State of the shown form data fields in order to restore the state when navigating to different pages with the Chatbot SDK.

Knowledge

The Knowledge SDK collects the following cookies. 

Provider Name Type Expiration Reason
Inbenta inbenta-km-session-id Technical Session Stores the session id so that all actions of the user are related to the same session.
Inbenta inbenta-km-session-token Technical Session Stores the session token so that all actions of the user are related to the same session.

The Knowledge SDK also stores the following localStorage data:

Provider Name Type Reason
Inbenta inbenta_km_api_url_{apiKey} Technical Acts as cache for the KM API url.
Inbenta inbenta_km_localstorage_{apiKey} Technical Acts as cache for each KM API endpoint request that is performed.

Search

The Search SDK uses local storage as cache for certain features:

Provider Name Type Reason
Inbenta

inbenta_search.v1.apis.0.<token>

Technical

Acts as cache for the Search API url.

Inbenta

inbenta_search.v1.auth.<token>.<env>.0

Technical Cache for the Search API Access token. It stores the token and its expiration time.
Inbenta

inbenta_search.v1.autocompleter.<token>.<env>.0

Technical Cache for the autocompleter data. It stores the information that is consumed by the autocompleter frontend (for example: the content titles).
Inbenta inbenta_session Technical

Cache for the session token.

Inbenta

inbenta_session_id

Technical

Cache for the session ID.

Messenger

The HyperChat SDK collects the following cookies. 

 
Note

Also collected by Chatbot upon Chatbot escalation to HyperChat.

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

The HyperChat SDK also stores the following localStorage data: 

 
Note

Also collected by Chatbot upon Chatbot escalation to HyperChat.

Provider Name Type Reason
Inbenta attended Technical It stores when the chat was attended by an agent.
Inbenta

lowestPosition

Technical

The chat lowest position in the queue.

Inbenta survey Technical It stores if the survey is pending to be displayed and the survey’s contents.
Inbenta waitingForAgentShowed Technical It stores a boolean value to detect if the “waiting for agent” message has been shown.
Inbenta

lastClosedTime

Technical It stores a timestamp of the last chat closing time.
Inbenta

previousToken

Technical It stores the previous and already invalidated user token.
Inbenta

transcriptMessageId

Technical

The download transcript button message identifier.