Skip to content
Fluence Foundation

Cookie Policy

Last updated: May 25, 2026

1. What Are Cookies

Cookies are small data files stored in your browser when you visit a website. They allow the site to remember information about your session across page loads and browser restarts. In addition to cookies, web applications may use localStorage — a browser-based key/value store that persists data beyond a single browser session.

Fluence Foundation uses cookies and localStorage exclusively for authentication and preference storage. We do not use any advertising, tracking, or analytics cookies of any kind.

2. Cookies We Use

The following cookies are set automatically by Supabase (our authentication provider) when you sign in to Fluence Foundation. They are strictly necessary for the platform to function — without them you cannot remain authenticated.

sb-[project]-auth-token

Purpose: Stores your Supabase authentication session token so you remain signed in between page loads without requiring re-entry of your credentials.

Type: Strictly necessary

Duration: Session — cleared when you sign out or when the 8-hour session window expires.

Set by: Supabase SSR (@supabase/ssr) on behalf of Fluence Foundation

sb-[project]-auth-token-code-verifier

Purpose: Stores the PKCE (Proof Key for Code Exchange) code verifier generated at the start of the Supabase sign-in flow. This is a security measure that prevents authorization code interception attacks.

Type: Strictly necessary

Duration: Short-lived — cleared automatically after the login flow completes (typically within seconds of signing in).

Set by: Supabase SSR (@supabase/ssr) on behalf of Fluence Foundation

Note: The [project] portion in each cookie name is replaced with the Supabase project reference identifier for the Fluence Foundation instance.

3. localStorage We Use

In addition to cookies, Fluence Foundationwrites two entries to your browser's localStorage. Unlike session cookies, localStorage data persists across browser restarts until explicitly cleared.

fluence-foundation-auth

Value: A JSON object containing your authentication token, user ID, email address, role, and login timestamp.

Purpose: Persists your authenticated session across browser tabs and page refreshes during the 8-hour session window. Used by the Zustand authentication store to keep you signed in without requiring network requests on every navigation.

Cleared: When you sign out of Fluence Foundation or when the session expires and you re-authenticate.

theme

Value: The string “dark” or “light”.

Purpose: Remembers your dark or light mode preference. This value is read before the page fully renders to apply the correct theme immediately and prevent a flash of unstyled content (FOUC) on page load.

Cleared: When you sign out of Fluence Foundation.

4. What We Do NOT Use

Fluence Foundation does not use any of the following:

The Lexend typeface used on this site is loaded via Next.js's built-in font optimization (next/font/google), which downloads fonts at build time. No runtime request is made to Google Fonts servers when you visit the site.

5. Managing Cookies

You can clear cookies and localStorageat any time through your browser's settings:

Please be aware that clearing authentication data (the fluence-foundation-auth localStorage entry or the Supabase cookies) will sign you out of Fluence Foundation. You will need to sign in again to access your account.

Because Fluence Foundationuses only strictly necessary cookies — required for authentication and session management — we do not display a cookie consent banner. Strictly necessary cookies are exempt from consent requirements under applicable data protection regulations, including Brazil's LGPD.

6. Contact

If you have questions about this Cookie Policy or how Fluence Foundation uses browser storage, please contact us at:

Fluence Foundation
Email: fluencefoundation@gmail.com