Security and Data Safety

Never enter spending credentials

A seed phrase or private key can authorize Bitcoin transactions. Stack2One has no field for either and support will never request them. Do not include them in notes, backups, screenshots, or email.

Local tracker storage

Goals, manual holdings, purchase history, plans, and preferences are stored in browser localStorage. There is no Stack2One account or cloud-sync database in this implementation. Exported backups contain the information you entered and should be protected accordingly.

Optional external lookups

Refreshing the BTC price contacts Stack2One's internal price endpoint, which retrieves a normalized quote from Coinbase or Kraken. Adding or refreshing a watch-only public address sends that address to mempool.space from your browser. Public addresses cannot spend Bitcoin, but they can reveal financial activity and relationships. Manual tracking avoids that disclosure.

Self-custody safety

Stack2One is not a wallet and cannot recover funds, reverse transactions, or verify a backup of wallet keys. Test any custody process with small amounts and use authoritative wallet documentation.

Report a concern

Send non-sensitive security reports to contact@stack2one.com. Do not include live credentials, personal transaction records, or information that could expose funds.