Your choice
Checking traffic measurement status…
The opt-out saves only a yes/no preference in this browser. Do Not Track and Global Privacy Control also disable measurement, even if you select Allow here.
What anonymous traffic statistics count
When enabled, our own server counts views of public pages, page loads that start a visit, landing pages, broad referral categories such as Google or Reddit, approximate countries, device categories, and browser families. Each category is totaled separately by UTC day. We do not store individual visit records or connect these categories into visitor profiles.
A “visit entry” means a fresh page load or tab; refreshing can count again. It is not a unique person or a session. The statistics cannot identify returning visitors, reconstruct browsing journeys, or reliably count unique people. Countries and other audience categories with fewer than five entries in a reporting period are combined.
What analytics never saves
No IP addresses or IP hashes, cookies, visitor IDs, fingerprints, wallet addresses, balances, transfer amounts, transaction signatures, form contents, precise locations, raw user agents, or full referral URLs are stored in analytics. Only fixed public page paths are accepted; URL queries and fragments are excluded.
Country estimation uses a downloaded database on our server. The connection address is read temporarily for that lookup and discarded without logging, hashing, or saving it in analytics. It is never sent to an external geolocation API. We do not request browser location permission or collect cities or coordinates. VPN and Tor use can make a country estimate inaccurate or unavailable.
Daily counters are retained for 90 days. Reports are private and require an administrator credential. There are no advertising pixels or third-party analytics scripts.
Network connections and other services
Connecting to a website necessarily exposes a network address to the hosting infrastructure. The no-IP-storage promise above describes our analytics. Your browser also contacts services needed for features you use, such as your chosen Solana RPC provider and wallet software. Those services have their own privacy practices.
Searching tokens or entering a swap amount connects your browser directly to Jupiter for token information and price quotes. Preparing a swap shares your public Solana wallet address with Jupiter so it can build the transaction. Your wallet signs locally and your chosen Solana RPC receives the signed transaction. Jupiter and your RPC provider have their own privacy practices. Pending swap signatures and signed transactions are saved in your browser until confirmation, so an uncertain transaction is not automatically sent again.
Country data is provided by IP Geolocation by DB-IP under the Creative Commons Attribution 4.0 license. Only the downloaded country database is used; DB-IP receives no visitor lookup requests from us.
Bridge records are separate
Solana balances, token transfers, and bridge records are public. Records can associate a Solana wallet with Pearl addresses, transfer amounts, and timing. These are operational blockchain records, separate from anonymous website statistics. Read the bridge privacy explanation before transferring.
The bridge can save wallet-related preferences and pending withdrawal information in your browser for its functionality. Those records are not sent to analytics. The statistics opt-out stores only a yes/no preference.