Cookies and Data Collection
This page lists the cookies and data collected by Inbenta products and Help portals. This information is updated regularly as our 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, they are excluded from user acceptance in terms of the requirements of the most relevant regulations in personal data protection.
Developers Portal
The Developers' Portal only uses one cookie:
| Provider | Name | Type | Expiration | Reason |
|---|---|---|---|---|
| Inbenta | PHPSESSID | Technical | Session | To identify the user session |
Chat
The Chat SDK does not use cookies since version 1.7.0 (7th of March 2018). If the Chat escalates to Agent Chat, it uses the Agent Chat cookie (see the Assist section below). When possible, the Chat SDK uses one type of “localStorage” called Indexed DB. The key of the IndexedDB storage is determined by the Chat Identifier (see the SDK Configuration). See below the Indexed DB storage created by the Chat SDK:
| Provider | Name | Type | Reason |
|---|---|---|---|
| Inbenta | accessToken | Technical | To maintain the authorization with the Chat API. The access token is refreshed as soon as the POST /Auth endpoint returns its expiration. |
| Inbenta | accessTokenExpiration | Technical | To know when the access token is going to expire in order to be able to refresh it. |
| Inbenta | avatar | Technical |
To maintain the bot state for the current session:
|
| Inbenta | chatbotUrl | Technical | To know the endpoint of the Chat API that should be used. |
| Inbenta | chatbotUrlExpiration | Technical | To know when the chatbotUrl is going to expire in order to refresh it. |
| Inbenta | sessionExpiration | Technical | To know when the session is going to expire in order to refresh it. It is refreshed every time the user interacts with the Chat app. |
| Inbenta | sessionId | Technical | To get the Chat session identifier. |
| Inbenta | sessionToken | Technical | To maintain the session with the Chat API. |
| Inbenta | sideBubble | Technical | To re-render the side window. |
| Inbenta | actionFieldEvents | Technical | To restore the state when navigating to different pages with the Chat SDK. |
| Inbenta | updatableConfiguration | Technical |
To maintain the bot configuration after it has been updated:
|
Note
Data is stored during a period established by each browser. No personal data is stored and the storage purposes are technical, to ensure the correct operation of the product. Therefore, considering that the regulations regarding personal data protection are not applicable, no previous consent is needed, and no specific retention periods are applicable.
Knowledge
The Knowledge SDK does not use cookies since version 1.45.1 (10th of August 2021), but it stores the following localStorage data:
| Provider | Name | Type | Reason |
|---|---|---|---|
| Inbenta | inbenta_km_api_url_{apiKey} | Technical | To cache the responses of the Knowledge API. |
| Inbenta | inbenta_km_localstorage_{apiKey} | Technical | To know the endpoint of the Knowledge API that should be used. |
| Inbenta | inbenta_km_api_token_{apiKey} | Technical | To store auth token generated to be able to use the KM API. |
| Inbenta | inbenta_km_sessions_{apiKey} | Technical | To store Inbenta session IDs. |
Note
Data is stored during a period established by each browser. No personal data is stored and the storage purposes are technical, to ensure the correct operation of the product. Therefore, considering that the regulations regarding personal data protection are not applicable, no previous consent is needed, and no specific retention periods are applicable.
Search
The Search SDK uses local storage as cache for certain features:
| Provider | Name | Type | Reason |
|---|---|---|---|
| Inbenta | inbenta_search.v1.apis.0.<token> | Technical | To know the endpoint of the Search API that should be used. |
| Inbenta | inbenta_search.v1.auth.<token>.<env>.0 | Technical | To know when the access token is going to expire in order to be able to refresh it. The token is refreshed as soon as the POST /Auth endpoint returns its expiration. |
| Inbenta | inbenta_search.v1.autocompleter.<token>.<env>.0 | Technical | To store the information that is consumed by the autocompleter frontend (for example, the content titles). |
| Inbenta | inbenta_session | Technical | To maintain the authorization with the Search API. |
| Inbenta | inbenta_session_id | Technical | To obtain the Search session identifier. |
Note
Data is stored during a period established by each browser. No personal data is stored and the storage purposes are technical, to ensure the correct operation of the product. Therefore, considering that the regulations regarding personal data protection are not applicable, no previous consent is needed, and no specific retention periods are applicable.
Assist
The Agent Chat SDK collects the following cookies.
Note
Also collected by the Chat soluton escalation to Agent Chat.
| 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 Agent Chat SDK also stores the following localStorage data:
Note
Also collected by the Chat soluton escalation to Agent Chat.
| Provider | Name | Type | Reason |
|---|---|---|---|
| Inbenta | attended | Technical | To store when the chat was attended by an agent. |
| Inbenta | lowestPosition | Technical | To store the chat's lowest position in the queue. |
| Inbenta | survey | Technical | To store if a survey is pending to be displayed, together with the survey’s contents. |
| Inbenta | waitingForAgentShowed | Technical | To store whether the “waiting for agent” message has been shown. |
| Inbenta | lastClosedTime | Technical | To store a timestamp of the last chat closing time. |
| Inbenta | previousToken | Technical | To store the previous and already invalidated user token. |
| Inbenta | transcriptMessageId | Technical | To store the download transcript button message identifier. |
Note
Data is stored during a period established by each browser. No personal data is stored and the storage purposes are technical, to ensure the correct operation of the product. Therefore, considering that the regulations regarding personal data protection are not applicable, no previous consent is needed, and no specific retention periods are applicable.