Cookie Policy

“Cookies” are small text files a site can store in your browser. “Local storage” and “session storage” are related browser features that let a site keep small pieces of information on your device between page loads. In this Policy we use “cookies” as shorthand for all of these, except where we need to be specific.

The Interface is a non-custodial staking front-end. It keeps its footprint small and uses only the storage it needs to function. It does not use cookies to identify you, follow you across other sites, or build a profile of you.

The Interface uses only the cookies and local-storage entries that are strictly necessary for it to work. Under Article 5(3) of the ePrivacy Directive, strictly necessary storage does not require your consent, but we list it here so you know exactly what it does:

• Wallet-session storage (set by the wallet-connect tooling, e.g. RainbowKit/WalletConnect): remembers which wallet provider you connected and the state of that connection, so you stay connected between page reloads and are not asked to reconnect on every visit. It is cleared when you disconnect your wallet or clear your browser storage.
• UI preference storage: remembers small interface choices — such as the network chip you last interacted with — so the page renders in the right state immediately and does not flicker on reload.

These entries are held in your browser's local storage and on your device. They are not sent to us as advertising or tracking identifiers, and we do not read them to recognise you on other websites.

The Interface sets no advertising, profiling, or cross-site-tracking cookies. In particular, it does not use Google Analytics, Facebook Pixel, or comparable third-party tracking or re-targeting tools, and it does not sell or share storage identifiers with advertisers or data brokers.

If we ever add a tool that relies on non-essential cookies (for example, an analytics product that is not strictly necessary), we will show you a consent banner first and will not set those cookies unless and until you agree.

A small number of providers are involved in serving the Interface and connecting your wallet. They may set their own cookies or see request metadata as part of that handshake. This mirrors the providers described in Section 5 of our Privacy Policy:

• Wallet-connection providers (e.g. WalletConnect, RainbowKit): facilitate the cryptographic handshake between your wallet and the Interface and may set their own cookies or storage to do so. Their handling of that data is governed by their own policies.
• RPC and CDN/hosting providers: serve the Interface, protect it against attack, and relay your on-chain reads and signed transactions. They see IP addresses and request metadata in transit but are not used by us to set tracking cookies.

We do not control cookies set by these third parties. Where they act as independent controllers, their own privacy and cookie notices apply.

You can view, manage, and delete cookies and local storage at any time through your browser settings. Most browsers also let you block or limit storage, though blocking the strictly necessary entries above may stop parts of the Interface from working — for example, the Interface may not be able to keep your wallet connected.

Clearing cookies and local storage will disconnect any active wallet session: the Interface will forget which wallet you connected and you will need to reconnect. Clearing storage does not affect your wallet, your funds, or any transactions you have already signed — those live on-chain and in your wallet, not in the Interface.

We may update this Policy from time to time. When we do, we will revise the “Last updated” date at the top. If a change is material — for example, if we introduce any cookie that is not strictly necessary — we will take reasonable steps to bring it to your attention through the Interface, including, where required, by asking for your consent first.