Privacy and this site

What stays in your browser, what goes to third parties, and how AdSense fits in — without marketing spin.

Earlier versions of this project emphasized "no tracking." After adding Google AdSense, that claim would be dishonest. This page replaces it with specifics. Full legal text lives in Privacy Policy and Cookie Policy.

What runs locally

The static HTML, CSS, and JavaScript are served from bitcoinwhale.org (or your cache). Radar filtering, session retention during a visit, Brief heuristics, and Labels search all execute in your browser. We do not operate an application server that logs your txid lookups or IP address.

Radar session memory (~30 minutes, in RAM) holds recent whale sightings so sparse mempool data can accumulate. Closing the tab clears it. Nothing is uploaded to us.

What leaves your browser (APIs)

  • mempool.space — your IP and requested txids hit their servers when you use Radar or Brief. Their privacy policy applies.
  • CoinGecko — price fetch for USD display. Optional to the tools' core logic; may fail silently.

We choose these public endpoints for transparency, not because we control them. Uptime and logging practices can change without notice.

AdSense and consent

The google-adsense-account meta tag is always present for Google site verification. The AdSense script loads only if you click Accept on the cookie banner. Decline keeps the site fully usable without ad scripts. Consent is stored as bw_cookie_consent in local storage.

Google may set advertising cookies after acceptance. Manage preferences via Cookies and Google's ad settings.

What we do not do

  • No user accounts or server-side profiles
  • No first-party analytics dashboard
  • No selling of lookup data
  • No hidden affiliate redirects in educational content

Improving your privacy

  1. Decline AdSense cookies on the banner.
  2. Use a privacy-focused browser or block third-party scripts.
  3. Query mempool.space via Tor or a VPN if your threat model requires it — we do not operate an onion mirror.
  4. Clear site data to reset consent.

Questions

Privacy requests and corrections: Contact. Open-source code: GitHub.