Privacy Policy — Liquid Implode

Last updated: August 2026

Liquid Implode is a self-custody cryptocurrency wallet. This policy explains what happens to your information when you use it.

What we don’t do

We do not collect, store, or have access to your seed phrase, private keys, or password. They are encrypted and stored only in your browser’s local storage, on your own device.
We do not run any servers that receive your wallet data. There is no backend — the extension talks directly to public blockchain networks and the third-party services listed below.
We do not sell, rent, or share any data with third parties for advertising or marketing purposes.
We do not track your browsing activity outside of the wallet’s own interface.

What the extension does send, and to whom

To function, the wallet makes direct requests from your browser to these third-party services. We (the developers of Liquid Implode) never see this traffic — it goes straight from your device to theirs:

Blockchain RPC providers (e.g. public nodes for Ethereum, BNB Smart Chain, Polygon, and other supported networks) — to read balances and broadcast transactions you sign.
0x and PancakeSwap — to fetch swap quotes and execute token swaps you initiate.
CoinGecko and GeckoTerminal — to fetch token prices and price charts.
Trust Wallet’s public asset repository — to display token logos.
The block explorer of the selected network (e.g. Etherscan, BscScan) — only when you click a “view on explorer” link, which opens in your browser like any other link.

These services may log your IP address and the requested wallet/token addresses as part of normal web request handling, under their own privacy policies. We don’t control those policies and encourage you to review them if you have concerns.

Local data

Your wallet (encrypted), selected network preferences, theme preference, and recent in-session transaction history are stored locally using your browser’s storage APIs. This data stays on your device and is never transmitted to us.

Permissions

The extension requests browser “storage” and “tabs” permissions, and host permissions for http/https pages, solely to store your encrypted wallet locally and to inject a standard wallet-connection interface (window.ethereum) so websites (dApps) can detect and connect to your wallet — the same mechanism used by other browser wallets.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new “Last updated” date.

Contact

Questions about this policy can be sent to:takamorisaigo79@gmail.com