Cookie & Browser Storage Notice

Agent Smith uses browser storage and, where enabled, cookies and related scripts to operate the Service, keep you signed in, remember preferences, and support core product functionality.

This notice explains the types of storage typically used by the website and web app. It should be read alongside our Privacy Policy and Beta Terms of Service.

In the EU, EEA, and UK, rules generally require clear notice and, where storage or access is not strictly necessary for the Service to function, a meaningful choice for the user.

Strictly necessary storage used for core product functionality, account access, or security may not require consent. Other storage or third-party scripts may require consent depending on how they are used.

During beta, Agent Smith intends to use a consent experience that blocks non-essential scripts until you make a choice. That implementation may roll out progressively. Until a consent manager is fully active site-wide, this notice describes both our current technical behavior and our intended approach.

At this stage, Agent Smith does not intend to rely on marketing pixels or non-essential analytics SDKs.

If we later introduce analytics, advertising, or other optional tracking technologies, we will update this notice and, where required, present an appropriate consent banner before enabling them.

In production environments, Supabase authentication session data is typically stored in sessionStorage when the browser supports it. This usually means your session does not survive a full browser restart.

In non-production environments, the client may prefer localStorage when available.

If browser storage is unavailable, such as in stricter private-browsing modes, the app may hold session data in memory only for the current page load.

When you use email sign-in or OTP-based login, the app may temporarily store your email address and related timestamps in sessionStorage so the sign-in flow can resume after a refresh.

This helps avoid broken login flows and improves continuity during authentication.

The public website assistant may keep the current tab's chat transcript in sessionStorage for the duration of that session.

In practice, this usually means the conversation remains available while the tab stays open and disappears when the tab is closed or site data is cleared.

Where enabled in a specific deployment, optional third-party services such as captcha tools or error-reporting services may use their own cookies or browser storage according to their own technical setup and documentation.

If those tools become active in a way that requires additional notice or consent, this page will be updated accordingly.

You can usually control or clear browser storage through your browser settings, including cookies, cached site data, localStorage, and sessionStorage.

Please note that clearing or blocking certain storage may affect sign-in, saved preferences, and other core product behaviors.