Widget cookies & storage

To function properly, the chat widget needs to store some information directly in your browser. Below is a list of all the data it requires.

Local Storage

ebbot_alert_box_visible: Flag used to remember if alert box should be visible or not ebbot_allow_upload: Flag used to control upload flow ebbot_chat_session_client_id: Bot ID ebbot_chat_session_id: Chat ID ebbot_chat_session_name: Auto generated name for the current user ebbot_clicked_buttons: We store a map of pressed button IDs. This allows us to gray out (or disable) those buttons if the user refreshes the page ebbot_initialized: Flag used to remember if there is an active session or not ebbot_input_field_visibility: Flag used to control the input field visibility ebbot_is_agent_handover_logic_executed: A flag indicating whether the user has gone through the contact agent flow ebbot_is_widget_box_visible: A flag to preserve the widget's minimized/maximized state upon page refresh ebbot_last_action: Stores the last user interaction (e.g., button click, user input) ebbot_session_triggers: Holds a list of once per session conversation triggers that we executed ebbot_triggers: Holds a list of regular conversation triggers executed ebbot_agent_message_read_at: Timestamp when last message was read (used for read receipts) ebbot_session_token: Token for authentification of the socket connection ebbot_socket_id: Stores the ID of the most recent socket connection. This is used in multi-tab scenarios to ensure only one active tab maintains the socket connection, disconnecting others. triggers_disabled: holds a flag that can be set through a message that disables conversation starters from that point onward or until toggled attention_seeker_disabled: holds a list of disabled conversation starters (you have a toggle when creating one that says this disables all the other attention seekers) has_unread_notifications: holds a flag that controls the notification indicator snoozed_until: holds the flag if we should send browser notifications or not agents_info: holds information about the agents that were in the conversation (mainly name and profile pic url) so history shows if the convo was passed from one agent to the other rating_type: holds the type of rating display (emoji or star) user_info: holds any user information (initially the generated session name but broken in first and last name, then any info that is set through Ebbot.setUserInfo() flow) disabled_chat_translation: flag that toggles if the end user wants to see agent messages translated or not

The "clear chat when session ends" setting in Ebbot will cause chat data to be saved in session storage rather than local storage.

Personal data

The data our service stores in the user's browser does not contain any sensitive information, such as IP addresses or personally identifiable details.

Although user_info allows for storing various data, we do not recommend using it for sensitive information.

Data expiration time

Data stored in the browser persists across sessions and does not automatically reset. Its data is only cleared based on the user's web browser settings, which may include clearing Browse data manually or upon browser closure.