Last updated: November 13, 2026
The controller responsible for data processing described in this policy is:
Hadamard Corporation
8206 Louisiana Blvd NE, Ste A #2316, Albuquerque, New Mexico 87113, USA (Entity ID 7388314)
German branch (Zweigniederlassung): c/o Matteo Ludwig, Rudolf-Hahn-Straße 67A, 53225 Bonn, Germany —
registered AG Bonn, HRB 29251, VAT ID DE449785620
Contact: info@hadamard.com
This policy covers bb84.com, the BB84 Wallet app (iOS and Android), and the services described below. It does not cover hadamard.com, which has its own privacy policy.
BB84 Wallet is a self-custodial, non-custodial cryptocurrency wallet application. This policy explains what data the app and its supporting backend services collect, how it is used, and your rights.
BB84 Wallet does not collect, transmit, or store any of the following:
There is no mandatory account registration: you can use the wallet without giving us any personal data. Personal data is only processed by our servers if you use one of the optional features described in sections 8–15 (for example a public profile, notifications or a support ticket), and limited technical diagnostics are described in section 13.
The following data is stored exclusively on your device — in the iOS Keychain or the Android Keystore (hardware-backed secure storage where available):
This data never leaves your device except as described below, and is never transmitted to any server we operate in a form that would let us reconstruct your keys.
When you perform transactions, your wallet address and transaction data are submitted to the BB84 L2 blockchain network (Chain ID: 42069000) and, for deposits and withdrawals, the Ethereum mainnet. Blockchain transactions are public and permanent by nature — once broadcast, we cannot alter, hide, or reverse them.
The app connects to:
These connections log your IP address as part of standard server operation, for abuse prevention and rate limiting. We do not correlate these logs with your on-chain identity.
If you resolve or use a bb84.eth subdomain, the request is served by our self-hosted ENS gateway. Like any web server, it logs requesting IP addresses for operational and abuse-prevention purposes.
To read Ethereum data and broadcast your Ethereum transactions (deposits, withdrawal proofs and finalization), the app connects to the public RPC service PublicNode, operated by an independent third party. PublicNode receives your IP address and the requests and signed transactions your app sends to it, and processes them under its own privacy policy. Transactions you broadcast become public on the Ethereum blockchain.
If you link an external Ethereum wallet in the app (e.g. MetaMask, via WalletConnect in Settings → Connectors), that wallet only signs an ownership statement; the app verifies it and stores it on your device only, unless you share it yourself. WalletConnect connections (also when you connect an OTA to a website) are end-to-end encrypted and pass through WalletConnect's relay and verification services, operated by a third party, which receive your IP address and the encrypted messages and process them under their own privacy policy. External wallets, including any wallet you use to send funds to a bb84.eth name, are independent software subject to their own privacy policies.
You can attach an optional profile to a one-time address (OTA) in Settings → Profile. It may contain a display name, date of birth, email address, phone number, postal address (street, postal code, city, country) and a profile picture — only the fields you choose to fill in. Saving a profile requires an on-chain ownership proof from the OTA, so only the holder of that OTA can create or change it.
Profiles are public by default: anyone who knows the OTA address or its bb84.eth name can retrieve the profile through our gateway, and other BB84 users may see your name and picture in their app. If you switch the profile to private, all profile fields including the picture are hidden from every requester. You can change or delete your profile at any time in the app or by contacting us. Profiles are stored until you delete them.
The profile screen offers "Sign in with Apple" and "Sign in with Google" solely to pre-fill your name and email address. The sign-in happens between your device and Apple or Google under their privacy policies; we do not create an account for you and do not receive any access tokens. The pre-filled data only reaches our servers if you then save it as your profile (section 8).
If you used Sign in with Apple, Apple may send us server-to-server notifications (for example when you change your email-forwarding preference or delete your Apple ID link). We verify and log these events (up to the last 500 events) to be able to honour them.
If you enable push notifications, the app sends us your device's push token (an Expo push token), the OTA addresses you want to be notified about and your notification preferences (incoming/outgoing). We use this to notify you about incoming and outgoing transactions on those OTAs. Notifications are delivered through Expo (650 Industries, Inc., USA) and Apple Push Notification service or Google Firebase Cloud Messaging. We store the token until you disable push notifications or it becomes invalid. We also keep the last known balance of registered OTAs to detect changes.
If you add a notification email address, we store it together with the OTA addresses it is linked to, its verification status, the number of verification attempts, your notification preferences and the last known balance of those OTAs. We send a verification email and, after verification, transaction notifications through Resend (Resend, Inc., USA). You can remove the email address at any time in the app; it is then deleted.
If you open a support ticket (in the app or on bb84.com), we store the name and email address you enter, your messages and our replies, the ticket source, timestamps and the IP address the ticket was sent from. The app keeps a random access token on your device so that you can read replies. We use this data only to handle your request. Resolved tickets are archived after 90 days without activity and deleted automatically when their retention period ends, counted from the end of the calendar year of the last message: 3 years for general requests (documentation in case of legal claims, Art. 17(3)(e) GDPR), which we delete earlier on request; 6 years for tickets that are business correspondence, e.g. about a payment, withdrawal, fee or complaint, which we are legally required to keep (§ 257 German Commercial Code, § 147 German Fiscal Code; Art. 17(3)(b) GDPR) and cannot delete before then.
To detect and fix errors, the app sends technical event and error logs to our server. A log entry contains a random installation ID (not linked to your identity), the app version and platform, the screen and a short message, and — where relevant to the error — a shortened OTA address, a transaction hash or an amount. Logs are stored on our server and rotated once they reach a fixed size (older entries are then deleted).
If you approve a connector request in the app (Settings → Connectors), we store the requesting app's name and website, the scopes you granted, the OTA addresses and — if you granted the profile scope — the profile data you chose to share, together with hashes of the access tokens and usage counters. The connected app can read this data and the balances and transactions of the shared addresses. If you granted it, it can also propose payments, which are only sent after you confirm them in the app; if you set up an AI budget for it, it can pay from that budget address without asking. You can disconnect an app at any time in the app; its access ends immediately.
AI assistants such as Claude can connect through our MCP server (https://bb84.com/api/connect/mcp)
with the same approval in the app. The assistant registers itself with its name and redirect address (OAuth client
registration). Registrations that are never used are deleted after 24 hours at the latest. The data the assistant reads (balances,
transactions, profile, depending on the scopes you granted) is passed to the assistant's provider and processed there
under that provider's privacy policy, for example
Anthropic for Claude.
We do not receive or store your conversations with the assistant.
If you allow it (scope payment proposals, can be switched off when approving), a connected app or assistant can propose a payment: recipient, amount, currency and an optional note. We store the proposal, the connection it came from, its status and, once you sent it, the transaction hash. A proposal is never executed automatically. It is only paid if you open it in the app and confirm it in the normal Send flow. Proposals expire after 24 hours and are deleted 7 days after they were created.
With the same scope an assistant can ask us to call a paid service for you (pay_and_call): an API or a tool of another provider that asks for payment. Our server then calls that service itself. The service sees our server's address, not yours, and receives the request the assistant specified. We store that request, the service's host name and the price it asked together with the payment proposal and, after you paid, the service's answer. All of it is deleted 7 days after the proposal was created. The payment proof we send to the service is the transaction hash of your payment; the transaction itself is public on the bb84 chain. The service's answer is passed on to the assistant. If you gave the assistant an AI budget, such a call can be paid from that budget without another confirmation in the app.
Authorised Hadamard staff can view the data described in sections 8–14 for a given OTA (profile, linked OTAs, notification settings, support tickets, current on-chain balance) in our protected admin interface, solely to provide support and to operate and secure the service. Access to that interface requires authentication and is logged.
The app requests camera access solely to scan payment QR codes (e.g. bb84.com payment requests) in the Send screen. No images are stored or transmitted.
On devices that support passkeys (iOS 18 or later), wallet backups are encrypted with a passkey for bb84.com that is created on your device and kept by your passkey provider (by default iCloud Keychain). The encryption key is derived on your device from the passkey and is only released after Face ID / your device passcode; it never reaches us. Besides the backup file you save yourself and the optional iCloud Drive backup, the app automatically stores one end-to-end encrypted copy of the wallet backup on our server as a last-resort recovery option, so you can restore your wallet with your passkey alone if your device and every other copy are lost.
We store only the ciphertext, a random-looking identifier and a hash of an access token (both also derived from your passkey on your device), the upload time, and — for a short time in our server logs — the IP address of the request. We cannot decrypt the backup, link it to your OTA addresses or profile, or recover your wallet without your passkey. We keep the five most recent uploads per backup. When an upload no longer contains OTAs that the previous one had (for example after deleting the wallet, renewing an OTA or restoring an older backup), the previous copy is additionally set aside so later uploads cannot push it out; up to three such older copies are kept, so a backup consists of at most eight copies. You can delete your server backup at any time in the app under Settings → Wallet → Server backup → “Delete server backup” (also offered after “Delete wallet”); this removes all copies from our server immediately and switches the server backup off on that device until you switch it back on. You can also contact us (section 25). Deleting the passkey for bb84.com from your passkey provider makes the stored copy permanently unreadable.
| Processing | Legal basis |
|---|---|
| Sending notification emails via Resend | Art. 6(1)(b) GDPR — performance of the contract you request by opting in |
| Server logs (RPC, ENS gateway) | Art. 6(1)(f) GDPR — legitimate interest in operating, securing, and rate-limiting the service |
| Ethereum RPC requests via PublicNode | Art. 6(1)(b) GDPR — necessary to carry out the Ethereum transactions and balance queries you request |
| WalletConnect connections (linking external wallets, connecting OTAs to websites) | Art. 6(1)(b) GDPR — necessary to establish the connection you request |
| Optional profile, push and email notifications | Art. 6(1)(b) GDPR — providing the optional feature you enable; for voluntarily published profile data also Art. 6(1)(a) GDPR (consent, revocable by deleting or hiding the profile) |
| Support tickets | Art. 6(1)(b) GDPR — handling your request |
| App diagnostics logs | Art. 6(1)(f) GDPR — legitimate interest in detecting and fixing errors |
| End-to-end encrypted server backup | Art. 6(1)(b) GDPR — providing wallet recovery as part of the app; Art. 6(1)(f) GDPR — legitimate interest in protecting you against permanent loss of funds |
| Wallet connectors | Art. 6(1)(a) GDPR — your consent when approving a connector, revocable by disconnecting it |
| Internal support access, Apple sign-in notifications | Art. 6(1)(f) GDPR — legitimate interest in support, security and honouring account-link changes |
Resend, Expo, Apple, Google, PublicNode and WalletConnect are used as described above and may process data outside the EU/EEA (including in the United States). Where this occurs, transfers rely on the providers' own compliance mechanisms (e.g. Standard Contractual Clauses); please refer to their respective privacy policies for details.
Server access logs and app diagnostics logs are rotated on a routine schedule for operational purposes. Profiles, notification settings and connector data are kept until you delete them or disable the feature; encrypted server backups (latest five uploads plus up to three older copies set aside, see section 17) are kept until you delete them in the app or ask us to delete them; support tickets are kept as described in section 12. Blockchain data cannot be deleted by anyone (section 5).
Subject to applicable law, you have the right to request access to, rectification of, or erasure of personal data we hold about you, to restrict or object to processing, and to data portability. To exercise these rights, contact us at info@hadamard.com. You also have the right to lodge a complaint with a supervisory authority — for our German branch, the competent authority is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW).
Private keys are stored in the iOS Keychain / Android Keystore, which provide hardware-backed encryption on supported devices. We recommend keeping a secure backup of your wallet export file and storing it in a safe location offline. Because BB84 Wallet is non-custodial, we cannot recover lost wallets or reverse transactions — the encrypted server backup (section 17) can only be opened with your own passkey.
BB84 Wallet is not intended for users under the age of 18. We do not knowingly collect information from minors.
We may update this policy as the app evolves. Material changes will be reflected by updating the "Last updated" date above. Continued use of the app after changes constitutes acceptance of the updated policy.
For questions about this privacy policy or to exercise your rights, contact: info@hadamard.com