Your data.
Clear boundaries.

How information is handled when you browse QBitcoin or use its tools.

Local wallet secrets

Local key and mnemonic tools process seed phrases, private keys and signing material on your device. These values are not sent to the QBitcoin API or saved in localStorage or sessionStorage. Results remain in the page until cleared or exited. Keep backups private and use the clear action when finished.

Public blockchain requests

Explorer searches submit public identifiers to the QBitcoin API. Block and transaction requests use PublicNode, with Tatum as a fallback. Address balances and confirmed history use Blockstream Esplora. Market snapshots use CoinMarketCap, CoinLore and Kraken through the backend; these feeds receive only a fixed Bitcoin market request, not your search identifiers. Public lookups and their results can reveal financial activity or interest in an address. An already signed transaction is submitted only after you explicitly confirm broadcast.

Browser history, hosting and temporary data

Public explorer identifiers appear in result URLs and may remain in browser history. The API temporarily caches public blockchain results and uses short-lived request counters for rate limiting. Website delivery exposes ordinary connection information, such as IP address and request path, to the servers handling the request. Do not put secrets in any URL.

Cookies, analytics and external assets

The current QBitcoin pages do not set analytics cookies, include analytics trackers or load third-party scripts. Fonts, logos and tool modules are served by QBitcoin. Public blockchain providers handle upstream requests under their own practices.

Privacy questions

Email [email protected] for questions about these practices. A contact email includes the information you choose to send; do not include wallet secrets. This page will be updated when website data practices change.