Your notifications reveal preferences. We treat them accordingly.

Information the service uses

Bitcoin Block Notifier uses your email address to verify access and deliver notifications. It also stores your selected network, mining pool, optional Coinbase-tag filter, future block-height target, preferred currency, timezone, and the block height at which each notification was saved.

For a verified-address notification, the service processes the address and signed message needed to prove control. The monitoring service must receive the address to watch it. The account database stores an opaque watch label derived from a keyed, non-reversible fingerprint; the label contains no characters from the address. The signature and its hash are not retained after verification.

Address monitoring is sensitive

Associating a Bitcoin address with an email account can reveal financial activity. A valid signed message proves control of that address at enrollment; it does not establish identity or legal ownership.

Never submit a seed phrase, private key, xpub, descriptor, or wallet backup. Bitcoin Block Notifier does not need them and will never ask for them.

Donation addresses

When an email is successfully verified, the service assigns that account one Bitcoin donation address and one Bitcoin BLAKE2b donation address. Re-verifying the same normalized email returns the same two addresses. The private account page shows only the address for the network you are viewing.

The account database stores each assignment so the same address can be shown again. These addresses and payments sent to them are public blockchain data, so anyone who already knows an address can inspect its activity. Bitcoin Block Notifier does not publish the email-to-address mapping, donation addresses, derivation indexes, or donation totals in public statistics.

Address inventories are derived privately. Seed phrases, private keys, extended public keys, and wallet descriptors are never sent to the public service. Only the already-derived public addresses and their network labels are uploaded.

The Bitcoin Lightning option creates a new invoice for the amount selected and is handled by an external Lightning provider. The provider may receive ordinary request and payment information. Lightning donations are not tied to the per-email donation-address assignment, and the service does not promise anonymous or untraceable donations.

BLAKE2b public fallback

If the private BLAKE2b node is unavailable, the service can retrieve whole new blocks from mempool.guide and compare them with the watchlist inside the monitoring service. Requests contain public block identifiers and page offsets only. Watched addresses are never included in those requests or sent to mempool.guide.

What public statistics contain

The stats pages show aggregate mining-pool popularity and the most-watched future block height using grouped subscriber ranges. They never publish watched addresses, donation addresses, email addresses, Coinbase-tag filters, donation totals, or individual subscriber records.

Service providers and records

Infrastructure and email providers process the minimum information needed to host the service and deliver messages. Security, verification, delivery, and abuse-prevention records may be kept when needed to operate and protect the service.

Messages sent to support are processed by the email service, stored as normalized plain text in the private support inbox, and forwarded to the operator's private Gmail mailbox. Complete messages are limited to 10 MiB. Attachment bytes and HTML are never stored by the website; only limited attachment metadata is retained in the support record. Gmail scans the forwarded original, but no scanner can guarantee that a file is safe. No automatic receipt is sent. The message and correspondence may be retained as needed to answer the request and protect the service. Never send seed phrases, private keys, passwords, or wallet backups.

Removing a notification stops it from being active and starts any required watcher cleanup. Internet services and backups are not instantaneous, so deletion from every operational copy may take time.