Cookie Policy

Exactly what's stored on your device — and why.

Last updated: March 2026

Short version: BridgeFlow only stores data that is strictly necessary to keep your wallet connected and the app working. We have no analytics, no advertising, and no third-party tracking of any kind. No consent banner is shown because there is nothing to consent to beyond what you explicitly trigger by connecting your wallet.

What Are Cookies & Local Storage?

Cookies are small text files a website saves to your browser. Local storage is similar but stores data directly in your browser rather than sending it with each request. Both are used to remember information between page loads.

BridgeFlow is a decentralised finance application. It does not have a traditional login system or user account database. Your identity is your blockchain wallet — we never collect your name, email, or any personal identifiers. The only state we store in your browser is what's needed to keep your wallet session alive.

What We Store

Strictly Necessary

Required

These are essential for the application to function. They cannot be disabled.

Name	Type	Duration	Purpose
wagmi.store	localStorage	Session	Stores your wallet connection state so you remain connected when navigating between pages.
wagmi.wallet	localStorage	Persistent	Remembers which wallet provider you used (e.g. MetaMask, WalletConnect) to reconnect automatically.
__Host-next-auth	Cookie	Session	Next.js internal session token. Set only when a session is active; never contains personal data.

Analytics

Not used

BridgeFlow does not use any analytics cookies or third-party tracking services.

Advertising & Marketing

Not used

BridgeFlow does not use advertising networks, retargeting pixels, or marketing trackers.

Why There's No Cookie Banner

Privacy law (including GDPR and CCPA) only requires a consent banner when a site sets non-essential cookies — for example, analytics or advertising trackers. Cookies that are strictly necessary for the service you explicitly requested are exempt from this requirement.

Because BridgeFlow stores only wallet-connection state — data that is essential for the application to work and that you trigger by pressing "Connect Wallet" — no consent banner is legally required or appropriate. Showing one would be misleading, since it would imply we have optional tracking to consent to.

If we ever introduce analytics or any other non-essential storage, we will implement a proper consent mechanism before deploying it.

Third-Party Services

WalletConnect

Wallet bridge

None in your browser. Relay is server-side.

Alchemy / RPC

Blockchain node provider

None. JSON-RPC calls only; no cookies set.

Chainlink Functions

AI optimizer automation

None. On-chain automation; no browser storage.

Firebase Hosting

CDN & static hosting

May set a single session cookie for CDN routing. Contains no personal data.

How to Clear Stored Data

You can clear all locally stored data at any time through your browser. Doing so will disconnect your wallet from BridgeFlow — you can reconnect immediately.

Chrome / Edge

Settings → Privacy → Clear browsing data → Cookies and site data

Firefox

Settings → Privacy & Security → Cookies and Site Data → Clear Data

Safari

Settings → Privacy → Manage Website Data → Remove All

Alternatively, disconnect your wallet using the button in the app header — this clears the session data automatically.

Questions?

If you have questions about how BridgeFlow handles your data, open an issue on the GitHub repository or reach out via the community channels listed on the homepage.

Home Analytics Treasury Dashboard