PRIVACY

Your Privacy Choices

Effective October 4, 2026

Do Not Sell or Share

BuildAWallet does not sell personal information and does not share personal information for cross-context behavioral advertising. We do not use advertising pixels, session-replay tools, keystroke-recording analytics or cross-site behavioral advertising on BuildAWallet pages. Because our current practice is already “do not sell or share,” you do not need to submit a separate opt-out request to receive that treatment.

Global Privacy Control

If your browser sends a Global Privacy Control (GPC) signal, we treat it as a request not to sell or share personal information. Our current no-sale/no-cross-context-sharing practice already satisfies that preference. We will not ask you to turn GPC off to use the service.

Checking this browser's GPC signal…

California privacy rights

If California privacy law applies to BuildAWallet or to a particular processing activity, you may have rights to know, access, delete and correct certain personal information; to opt out of sale or sharing; to limit certain uses or disclosures of sensitive personal information; and to receive equal service for exercising privacy rights, subject to legal exceptions and verification requirements. BuildAWallet does not require you to waive non-waivable privacy rights as a condition of using the service.

Data-minimization choices

You can browse public information without creating a HUMAN account, avoid saving or publishing wallet designs, clear local browser storage, avoid entering personal information into design or support fields, and stop using the service. Never provide BuildAWallet with a seed phrase, private key, wallet password, API key or session token.

Public blockchain addresses and transactions are public by design. If the browser or Android wallet queries a public RPC provider, that provider may receive the public address or transaction request together with ordinary network metadata such as an IP address.

Requests and questions

Do not put private account information in a public GitHub issue. For non-sensitive questions, you may use the project's public issue tracker. BuildAWallet should maintain a private contact channel for verified privacy-rights requests before collecting information that requires an individualized response.