1. Our Approach: Zero Tracking Bloat

Unlike conventional software platforms that deploy invasive analytics trackers, retargeting pixels, and cross-site marketing beacons, Saathi Bot operates on an ethical, minimal storage philosophy.

We do not sell user data, we do not track visitors across other websites on the internet, and we do not use cookie consent banners designed with deceptive dark patterns.

2. Exactly What We Store & Why

We divide our browser storage into two distinct surfaces: the Dashboard Application (for bot owners) and the Embeddable Widget (for your website visitors).

A. The Saathi Bot Dashboard (For Bot Owners)

When you sign in to manage your bots, we store strictly necessary authentication credentials:

Storage Key / Cookie	Type	Duration	Purpose
sb-access-token / sb-refresh-token	HTTP-Only Cookie / localStorage	Session / 30 Days	Maintains your authenticated session securely via Supabase Auth so you stay logged in.
saathi_theme	localStorage	Persistent	Remembers your dark mode / light mode interface preference.
saathi_byok_vault	Session / localStorage	Until logout	Holds your Bring-Your-Own-Key credentials strictly in local device memory, guaranteeing zero server database exposure.

B. The Embeddable Chat Widget (On Your Website)

When a visitor browses your website and opens the Saathi Bot widget, the storage footprint is exceptionally lightweight:

Storage Key	Type	Duration	Purpose
saathi_visitor_id	localStorage	Persistent	An anonymous random UUID. Keeps the chat window open and preserves conversation context as the visitor navigates between pages on your domain.
saathi_widget_state	sessionStorage	Browser Tab Session	Remembers whether the chat modal was expanded or minimized while viewing your website.

Notice: The embeddable widget sets zero third-party cookies, sets zero advertising identifiers, and does not touch cross-domain cookies.

3. How to Inspect, Clear, or Disable Storage

Because we use native browser localStorage and standard cookies, you or your visitors retain absolute control over stored items at all times:

Using Browser DevTools: Open Chrome/Firefox DevTools (F12 or Ctrl+Shift+I), navigate to the Application tab, and select Local Storage or Cookies to view and delete keys individually.
Clearing Browser Cache: Choosing “Clear Browsing Data” in any browser clears all localStorage keys and cookies instantly.
Incognito / Private Browsing: In private windows, all storage is automatically purged the moment the browser window closes.

4. Updates to this Policy

If we introduce any new functional feature requiring client-side storage, we will update the tables above before deploying the changes to production.