Cookie Policy
Last updated: September 14, 2026
This policy explains the cookies and browser storage FluentChat uses on this website, in its dashboard, and in its embeddable chat widget.
1. What cookies and browser storage are
Cookies are small files placed by a website in a browser. Local storage is browser-managed storage that stays put until the visitor, the browser, or the application clears it. Session storage works the same way but is emptied as soon as the browser tab is closed. All three let a service remember a session or a preference.
We use the word storage below to cover all of them.
2. Dashboard cookies and storage
We use necessary session and security cookies to authenticate dashboard users, maintain their signed-in session, protect requests, and keep the service secure. Blocking these cookies can prevent the dashboard from working. Expired sessions and tokens are pruned as part of our service operations.
Your sign-in itself lives in those cookies. Alongside them, the dashboard keeps a few things in your browser so it can pick up where you left off. None of it is sent to a third party, and none of it is used for advertising.
| Key | Purpose | Category |
|---|---|---|
isLoggedIn | A yes/no flag so the app knows to fetch your account on load. Not a token — the real session lives in the cookie. | Necessary |
user (session storage) | Your account details for display — name, email, team. Cleared when you close the tab. | Necessary |
live_chat_message_drafts_v1 | Replies you have typed in the inbox but not sent yet, so a refresh does not lose them. | Functional |
fluentbot.conversation-search.recent.{teamId} | Your last few conversation searches, per team. | Functional |
fbt-inbox-filters | Remembers the filters you left the inbox on. | Functional |
fluentbot-theme | Remembers a light or dark theme preference. | Functional |
bot_embed_platform_v1 | Remembers which install guide you last opened on the embed screen. | Functional |
sidebar_width, inbox_queue_width, inbox_visitor_width, playground_history_width, conversations_history_width | Widths of panels you have dragged to resize. | Functional |
fbt_chunk_reload_attempted (session storage) | Marks a one-time reload after a new version ships, so the page cannot reload in a loop. | Necessary |
3. Chat widget local storage
When a customer embeds FluentChat, the widget may use the following first-party local-storage keys on that customer’s website:
| Key | Purpose | Category |
|---|---|---|
fbt_session_token | Keeps a visitor’s widget session continuous across page loads. | Necessary |
fbt_chat_id | Restores the active conversation. | Necessary |
fbt_visitor_email_{botId} | Remembers an email that a visitor supplied for a particular bot. | Functional |
fbt_mode_{chatId} | Remembers whether the visitor selected the AI or human conversation mode. | Functional |
fbt_theme_preference | Remembers a light or dark theme preference. | Functional |
These values remain until cleared by the visitor, browser, or widget. Legacy storage keys may be read only to migrate an existing session and are then removed.
4. This website
Our public website and documentation set no cookies and run no analytics or advertising scripts. They keep one value in local storage:
| Key | Purpose | Category |
|---|---|---|
starlight-theme | Remembers a light or dark theme preference. It is written on your first visit with a default of light, and updated if you use the theme picker. | Functional |
5. Necessary and optional technologies
The tables above mark each item Necessary or Functional.
Necessary means the product does not work without it — signing in, staying signed in, keeping a conversation attached to the right visitor. These are set without asking, because asking would be asking whether you want the thing you just requested.
Functional means it only remembers a convenience: a draft, a theme, a panel width, an email you already typed. Nothing here is strictly necessary, so in regions where consent is required for non-essential storage, that consent is needed before these are written. We do not use any of it for advertising, profiling, or tracking people across sites, and none of it is shared with an ad network.
Where FluentChat is embedded on a customer’s website, that customer controls the page and the consent banner on it. They are responsible for collecting consent where it applies and for describing the widget in their own privacy and cookie notices. Anything they add on top — analytics, marketing pixels, or other non-essential technologies — is theirs to disclose and theirs to get consent for.
6. Your choices
You can clear cookies and browser storage in your browser settings, and most browsers let you block them per site. Clearing widget storage can end a conversation session or remove saved preferences. Clearing dashboard storage signs you out and drops unsent drafts and saved layout preferences. You can also ask the website operator that embedded the widget about its consent choices and privacy practices.
7. Related policies and contact
Read our Privacy Policy for details about personal-data processing and our Terms of Service for service terms. Questions about this policy can be sent to contact@fluentchat.ai.