Legal

Cookie policy

How Par uses cookies and similar browser storage. Effective 14 November 2026; every entry below was checked in a fresh browser against the live build.

Last updated 14 November 2026

Summary#

Nothing on the website, wallet state on the app
Par sets no cookies of its own and uses no analytics, advertising or tracking. The website pages store nothing at all. The app pages load third-party wallet libraries, which keep connection state in local storage and IndexedDB. No cookies are set on any page. Privacy laws treat this kind of storage like cookies, so it is all listed here.

Website pages#

The home, docs, developers, security, terms, privacy and cookie pages set no cookies, no local storage, no session storage and no IndexedDB. There is nothing to accept or opt out of.

App pages in detail#

The vault, guarantee, certificate, payment and Circuit pages load the wallet libraries. They create the entries below as soon as the page loads, even before you connect a wallet. Par's own code does not read them for anything except keeping your wallet connected.

NameTypeSet byPurpose
@appkit/connection_status, @appkit/disconnected_connector_ids, @appkit/active_caip_network_id, @appkit/active_namespaceLocal storageReown AppKitWhether you are connected, which connectors you disconnected, the selected network
wagmi.storeLocal storagewagmiThe connector you used last and the selected chain, so you stay connected between visits
rk-versionLocal storageRainbowKit (used by Mezo Passport)The wallet-list version
WALLET_CONNECT_V2_INDEXED_DBIndexedDBWalletConnect (via Reown)Created on load; holds a WalletConnect session and its encryption keys once you connect through WalletConnect
Wallet-specific entriesLocal storageMezo Passport, your walletMay be added after you connect a wallet, for example to link a Bitcoin wallet to its Mezo account

All of these stay until you disconnect or clear this site's data.

None. The Coinbase and Base Account wallet SDKs, which would contact coinbase.com and cause a Cloudflare cookie there, are switched off in Par. Reown may send connection events to pulse.walletconnect.org from app pages, without setting a cookie. See the Privacy policy for what each provider receives.

Managing storage#

  • Disconnect your wallet from the account menu to end the wallet session.
  • Clear this site's data in your browser settings to remove everything above; you'll need to reconnect next time.
  • Blocking third-party cookies does not affect Par.
  • If you prefer not to have any of this, stay on the website pages: reading the docs and the home page stores nothing.

Changes and contact#

If the website pages ever start storing anything, or we add non-essential cookies such as analytics, we'll update this page first and ask for consent where the law requires it. Questions: open an issue on GitHub, or a private security advisory for anything you'd rather not post publicly.