Public data, private curiosity
Privacy, plainly.
No wallet connection, signatures, account or advertising trackers. Addresses entered for a lookup are public blockchain addresses.
When you search
Opening an example or searching an address loads a report. When fresh blockchain data is needed, the searched public address is sent to Zerion. The home page does not preload balances, and cached reports may be reused without a new provider request.
Limits and storage
Real lookups use a signed, HttpOnly anonymous cookie lasting up to 24 hours to enforce the browser allowance. Request bursts use a daily keyed hash of the connection IP. In production, reports and analytics that need fresh provider data also share a daily network allowance through that hash. Raw IPs are not stored by this application. Expired counters are cleaned in bounded batches as live traffic continues.
If provider caching is enabled, report data may be stored for up to ten minutes and deleted in subsequent cleanup batches. Expired data is never served. URLs contain the searched address and may remain in browser history. Sharing a link shares that address and scope.
Separately, live lookups may add daily totals by query type — requests, cache hits and misses, errors and latency — plus budget warnings. Those aggregates keep no address, IP or cookie and expire after 14 days. They are not the report cache.
External services
When product measurement is enabled, temporary visit and request IDs help count useful reports and feature use. Visit IDs stay in tab memory; they are not saved in cookies or browser storage. Events exclude searched addresses, token amounts and copied text. Detailed events are eligible for deletion after 72 hours; cleanup runs periodically. Aggregated statistics and operational snapshots are retained for 400 days. The security cookie is not reused for analytics.
Token logos may load from Zerion’s CDN without a referrer. Following an explorer link opens that service with no referrer. Hosting and data providers may process request metadata under their own policies. Application code does not log searched addresses, raw provider bodies or keys.
You can clear the site cookie and browser history using your browser settings.