LEGAL

Privacy Policy

Effective October 5, 2026

1. Scope and privacy baseline

This Privacy Policy applies to BuildAWallet.xyz, its HUMAN website, machine/API services, and the BuildAWallet Android wallet. BuildAWallet is designed to minimize collection. We do not sell personal information or share it for cross-context behavioral advertising. We do not use advertising pixels, session-replay tools, keystroke-recording analytics, cross-site behavioral advertising, or session-replay recording on BuildAWallet pages.

The HUMAN wallet derives keys locally and stores recovery material encrypted on the device. It does not send recovery phrases, private keys or wallet passwords to BuildAWallet servers. The optional machine wallet-generation endpoint temporarily creates a recovery phrase in server memory after explicit consent, returns it once with no-store headers, and records only its rate-limit counter. Prefer the local agent kit when generation must remain on your device. Never put wallet secrets in chat, design fields, support messages or API requests.

2. Notice at collection: what we process and why

Depending on the feature you use, we may process: (a) an email address used to send a passwordless sign-in link; (b) authentication and security records such as hashed account identifiers, hashed session tokens, challenge records, expiry times and account timestamps; (c) public wallet addresses, transaction identifiers and public blockchain queries that you submit; (d) wallet-design choices, saved-design identifiers and publication choices; (e) API-plan, payment, entitlement and usage information; and (f) ordinary network/security metadata processed by our infrastructure providers, such as IP address, browser/device information, timestamps and request logs.

We use this information to provide requested features, deliver sign-in links, authenticate sessions, save designs when requested, read public blockchain data, verify payments, meter API access, prevent abuse and replay, maintain security, troubleshoot service problems and comply with applicable obligations. We do not use it to build advertising profiles.

3. HUMAN login and browser storage

When you request a confirmation email, our transactional email provider processes the address and delivery metadata needed to send the message. BuildAWallet normalizes and hashes the address before storing the account, challenge and session records in Cloudflare D1; the raw address is not stored in the authentication database. The browser session token is stored only as a hash. The browser receives a Secure, HttpOnly, SameSite=Lax cookie, and a six-digit email code confirms the account so the wallet build can continue on the setup page.

Wallet drafts, Studio preferences, an optional email display hint and other UI state may be stored locally in your browser. The website's Terms/Privacy acknowledgment is recorded in first-party, versioned local browser storage so the service can remember that you accepted the current documents. We do not use those records for advertising.

4. Wallet keys, Android and self-custody

The web wallet and generated Android WebView project derive keys locally from a recovery phrase. Recovery material is encrypted using AES-GCM in IndexedDB, with either a password-derived key or an optional device-local non-extractable key. On a device vault, scripts running on that same origin can request decryption; it is not a substitute for device security. Earlier native Android releases use their separate on-device implementation.

Public wallet addresses, transaction requests and signed transactions are sent to blockchain RPC providers. Clearing browser/WebView storage or uninstalling the app can remove the local vault. Keep an offline recovery backup. BuildAWallet cannot recover lost recovery material.

5. Service providers and disclosures

Cloudflare provides hosting, Workers, security and D1 storage for first-party authentication, billing, metering and wallet-guide history, and may process request/security metadata. Our transactional email provider processes the email address and delivery metadata needed to send confirmation messages. Public blockchain RPC providers receive the chain queries necessary to provide balances, transaction data or broadcasts. GitHub hosts public source code and Android release downloads and may process requests under its own privacy terms. Payment and x402 infrastructure may receive public wallet, transaction and settlement information needed to verify a payment.

We disclose information to service providers only as reasonably needed for the service, security, payment, delivery or legal functions they perform. We may also disclose information when reasonably necessary to comply with law, protect rights or security, investigate abuse, or complete a business transaction subject to applicable legal requirements. Public blockchain information remains public independently of BuildAWallet.

6. Sale, sharing, tracking and Global Privacy Control

We do not sell personal information and do not share personal information for cross-context behavioral advertising. We do not embed third-party advertising pixels or session-replay technology on BuildAWallet pages. If a 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 applies that preference. See Your Privacy Choices.

7. Retention

Local drafts and Android wallet data remain on the device until removed by the user or app/browser storage is cleared. Short-lived authentication challenges and sessions include expiry times. Account, payment, entitlement, usage and security records may be retained as reasonably necessary to operate the service, prevent duplicate redemption or abuse, resolve disputes and comply with obligations. Infrastructure providers maintain logs according to their retention settings. Public blockchain records are outside BuildAWallet's control and generally cannot be erased.

8. California and other privacy rights

If applicable law gives you privacy rights, those rights may include access/knowledge, correction, deletion, portability, objection, opt-out of sale or sharing, limitation of certain uses of sensitive personal information and non-discrimination for exercising privacy rights, subject to verification and legal exceptions. BuildAWallet does not require you to waive rights that applicable law says cannot be waived.

California users can review Your Privacy Choices. BuildAWallet's current practice is not to sell personal information or share it for cross-context behavioral advertising. If that practice changes, we will update our notices and implement legally required choices before the new practice begins.

9. Security and age

We use measures such as hashed bearer credentials, authenticated sessions, rate limits, local encrypted key storage and transaction confirmation flows. No system can guarantee absolute security. BuildAWallet's wallet products are intended for adults age 18 or the age of legal majority where they live and are not directed to children.

10. Contact and changes

We will update this policy when material practices change and will update the effective date above. For privacy-rights requests or a private privacy question, contact privacy@buildawallet.xyz. Do not send a seed phrase, private key, wallet password, API key or session token. Non-sensitive product issues may also be reported through the public project issue tracker, but public issues should never contain personal or confidential information.

Wallet guide conversations

If you use Byte, your chat messages and non-secret build context are sent to the configured AI provider, and the conversation is stored under the pseudonymous identifier for your verified BuildAWallet account so it can continue across devices. The request disables provider-side storage where supported; the provider still processes the request. You can clear the conversation from the chat. The app refuses recognizable recovery phrases and labeled private keys before sending, and checks again on the server; do not rely on detection as a guarantee that every secret will be recognized.