Self-custody explained
Why no account also means no safety net.
BitHedge asks for nothing because it has nowhere to put it. There is no server, no account system, and no company in the middle of your transactions. That is worth being precise about — including about what it does not buy you.
Know Your Customer rules exist because certain businesses hold, move, or exchange other people’s money, and regulators want those businesses to know whose money it is. Exchanges, brokers and custodial wallet providers all fall inside that perimeter. They ask for your passport because the law asks them to.
A non-custodial wallet is outside it. BitHedge never holds your coins, never takes an instruction on your behalf, and never touches a payment — it helps your phone sign a transaction with a key that has only ever existed on your phone. There is no customer relationship to know. This is also why we cannot freeze, reverse, or recover anything: the same structural fact produces both.
This is the part most “anonymous bitcoin wallet” pages skip. The Bitcoin blockchain is a permanent public record. Every amount and every address is visible to anyone, forever, and chain analysis is an entire industry built on connecting those dots. Choosing a wallet that does not ask your name changes none of that.
What actually links a person to coins, roughly in order of how often it happens:
| Leak | Who learns what | Does a no-KYC wallet fix it? |
|---|---|---|
| Withdrawing from a KYC exchange | The exchange links your verified identity to the receiving address | No |
| Address reuse | Anyone can see all payments to that address are the same party | Partly — a fresh address per payment helps |
| Querying a public blockchain server | The operator sees your IP and which addresses you care about | No — running your own node does |
| Wallet analytics and crash SDKs | Third parties learn your device, usage, sometimes your balance | Yes, if the wallet genuinely embeds none |
| Publishing an address anywhere | Everyone, permanently | No |
No account, ever. No email, no phone number, no name, no document. Nothing to breach, nothing to subpoena, nothing to lock you out of.
No analytics of any kind. No advertising SDK, no attribution SDK, no crash reporter, no third-party library that phones home. The App Store privacy label reads Data Not Collected because there is nothing to declare.
A fresh receiving address every time, so your payments are not trivially linked to each other on-chain.
Your own node, if you have one. Point the app at it — on your local network or over a .onion address — and it will talk only to your node. It will never quietly fall back to a public server, because falling back would hand your wallet to exactly the party you ran a node to avoid.
It will not mix your coins, hide your transaction from the chain, or make your holdings untraceable, and it will not help you avoid an obligation you have. If you want stronger on-chain privacy, that is a real field with real tools and real trade-offs — but it starts with understanding that the ledger is public, not with picking a wallet that skipped a signup form.
Yes. KYC is an obligation on businesses that hold or exchange money for customers. A non-custodial wallet does neither — it is software that helps you use a key you already hold — so there is no account to open and nothing to verify. BitHedge asks for no name, no email, no phone number, and no document.
No, and any wallet that implies otherwise is misleading you. Bitcoin is pseudonymous: every transaction is public forever, and addresses can be linked to each other and, with enough context, to a person. Skipping KYC at the wallet means the wallet does not know who you are. It does not erase what the blockchain records, and it does not undo an identity check you passed at an exchange.
Holding your own bitcoin in your own wallet is legal in most jurisdictions, and no KYC applies because there is no financial institution in the relationship. That is separate from your obligations: buying, selling, and in many places spending or gifting bitcoin can be taxable events you must report regardless of which wallet you used. Nothing here is legal or tax advice — check the rules where you live.
Several things. Your IP address, seen by whichever blockchain server your wallet queries. The exchange you originally withdrew from, which knows your identity and the address it sent to. Reusing an address, which links payments to each other. Posting an address publicly. And the ordinary metadata of who you pay. A no-account wallet closes exactly one of these, and running your own node closes the first.
No. There is no BitHedge server for it to talk to. Your phone queries public Esplora servers — mempool.space, failing over to blockstream.info — directly, so those operators see your IP and the addresses you ask about, and we see nothing at all because we are not in the path. Pointing the app at your own node removes even that.
Not from the wallet's side — tap Receive, share the address, done. But whoever sends it may have their own obligations, and if you are withdrawing from an exchange, that exchange already knows who you are and will record the address it paid. The wallet not asking is not the same as nobody knowing.
Why no account also means no safety net.
The one change that closes the IP leak entirely.
The complete list of endpoints the app contacts.