Short version. The Polkadex Explorer is a read-only window onto a public blockchain. We don't run analytics, we don't set tracking cookies, we don't sell or share data with third parties. We store a handful of small items in your browser's local storage to remember your preferences, and our server logs the kind of request data a normal web server logs.
1. Who we are
The Polkadex Explorer (explorer.polkadex.ee) is operated by the Polkadex Foundation. This policy covers the explorer specifically; the Foundation's wider organisational privacy policy is available at the Polkadex Privacy Policy.
2. What we store about you
The explorer stores three kinds of data:
a) On-chain data. All blocks, extrinsics, events, balances, validators, governance proposals, and votes you see on this site are already public on the Polkadex Mainnet. We index them so you can browse them efficiently. Anyone with a Polkadex node has access to the same data. We cannot delete on-chain data — that's a property of the blockchain itself, not of this explorer.
b) Local storage on your device. We keep a small set of keys in your browser's localStorage so the explorer remembers your choices between visits. See the Cookie & Storage Notice for the full list. This data never leaves your device unless you explicitly sign a transaction or post a community label.
c) Server logs. Our backend logs the standard request data a web server records: source IP (often a Cloudflare IP, since we're behind Cloudflare), user-agent, requested URL, response code, and timestamp. We use these to debug errors and measure traffic shape. Logs are retained for 30 days and then rotated out.
3. Wallet addresses and signatures
If you connect a wallet, the explorer reads your account's public address from your wallet extension. Public addresses are not personal data on their own under most privacy frameworks — they are pseudonymous identifiers anyone can derive from a public key — but they can become personal if linked to your identity, which is something you control. We never request your private key, mnemonic, or secret seed phrase. Any wallet extension that asks the explorer for these is malicious.
When you post a community label, a discussion message, or a vote, your wallet signs the action with your private key. The signed payload — including your address and the signature — is stored on our server (for labels and discussions) or broadcast to the chain (for votes). You can ask us to remove labels, votes, or discussion messages you authored; contact us via the channels listed below.
4. Third-party services
The explorer integrates with:
— Cloudflare as a CDN and DDoS shield. Cloudflare sees your IP. Their privacy policy is at cloudflare.com/privacypolicy.
— Browser wallet extensions (Polkadot.js, Talisman, SubWallet, Nova Wallet) when you click Connect Wallet. The explorer doesn't share any data with them; they expose your account list to us with your explicit permission.
— A PDEX price feed (CoinGecko/Coinpaprika public API) that runs server-side. Your browser does not contact these endpoints directly.
We do not load Google Analytics, Mixpanel, Segment, advertising pixels, or any other analytics/tracking script. The explorer's JavaScript bundle is self-hosted; there are no third-party scripts loaded from external CDNs that could fingerprint you.
5. Your rights (GDPR / UK GDPR / CCPA)
You have the right to (a) know what personal data we hold about you, (b) request a copy, (c) request correction or deletion, and (d) object to processing. For the explorer specifically:
— Local storage: clear it any time via your browser settings, or click "Reset preferences" on the Cookies page.
— Community labels, votes, discussion messages: message us with the wallet that signed them (we'll verify via a fresh signature) and we'll delete them.
— Server access logs: we don't have a way to identify you within them unless you tell us your IP and time-window, but if you do, we'll delete matching entries on request.
— On-chain data: we cannot delete this. It's on the blockchain, not on our server.
6. Children
The explorer isn't directed at children under 16. We don't knowingly process data from anyone under 16. If you believe a child has used the explorer in a way that needs attention, contact us.
7. Changes to this policy
We'll update the "Last updated" date at the top of this page when this policy changes. Material changes will also be announced on our community channels.
8. Contact
Open an issue at github.com/Polkadex-Substrate or reach the team via the official channels listed at polkadex.ee.
