Privacy & security — WhiSPa Wallet

⚠ Reusing one normal address

Every payment to you is clustered under one address, forever.
Anyone who has paid you sees your balance and history.
Posting it publicly ties your identity to all of it.

✓ One Silent Payment address

Each payment lands on a fresh output, unlinked to the rest.
Observers see unrelated outputs — your history stays private.
Publish it anywhere; only your scan key finds your coins.

No address reuse, ever

Share one code for years; reuse of the public address never becomes reuse on the chain.

Nothing to coordinate

No asking senders for a fresh address, no invoice trail showing who paid what.

Fewer signals to analyse

Clustering relies on address reuse and single-owner inputs. This removes both.

What this doesn't do Limits

It protects the receiving side. Coins you spend still carry their history, so coin control still matters.
It isn't a mixer — amounts and timing stay visible, even when the links don't exist.
Network privacy is separate: who broadcasts, and from which IP, isn't covered here.
BitMail lookups are ordinary DNS queries, visible to the resolver. The payment stays private.
Your keys are your responsibility — there's no password reset for bitcoin.

Security

The server never holds your keys

A full server compromise still can't move your bitcoin.

🔑

Seeds never reach the server

Generated and held on your device. There's no seed column in the database to leak — and no one to recover it for you.

📱

Account + device confirmation

A new device must be confirmed by email before it reaches a wallet, so a stolen password isn't enough.

✍️

Local signing

Transactions, PayJoins included, are signed on your device. The backend can't author one for you.

👁

Scanning is opt-in

Background scanning uploads your scan key only: it can detect coins, never spend them, and you can turn it off.

None of that helps if the app itself is fake. The Android builds are sideloaded, so check the one you downloaded before installing it — verify a download →