HAZEWALLET · RUSTCAN LLC
Privacy Policy
Effective November 13, 2026
HazeWallet is the self-custody wallet product operated by RustCan LLC, a United States business. This policy covers hazewallet.com, HazeWallet web widgets, the HazeWallet Chrome extension and the HazeWallet iPhone app; the local-storage and permission descriptions also apply to our Android app where available. For support, privacy questions or requests, email support@hazewallet.com.
Self-custody does not mean that using a wallet is anonymous or that no personal information is processed. We distinguish information held locally on your device, information handled by our servers and providers, and public blockchain information.
1. Keys, passwords, backups and preferences
The normal wallet creates/imports keys, decrypts the wallet and signs transactions locally. It does not require a hosted HazeWallet account or send your wallet password, unencrypted private keys or recovery secrets to our servers. Unlocked keys exist in device memory while needed. The saved wallet record is password-encrypted: the web wallet uses browser IndexedDB; iOS uses device-only Keychain protection; Android uses a Keystore-protected local file excluded from normal app backup. Device compromise, malicious software or unsafe sharing can still expose information.
Optional Lenient viewing. After password confirmation and a new sign-in, Lenient mode can retain public viewing across refreshes and return visits for up to eight hours without activity. Its local browser/WebView record contains public receiving accounts, the selected asset, a digest identifying the encrypted wallet and timestamps. This public record is not password-encrypted and contains no wallet password, private key or signing grant. Anyone using the device may see balances, addresses and activity while viewing access remains valid. Sensitive actions in Lenient mode require a fresh wallet password. Manual Lock removes the return-viewing record. The timer depends on the device clock; invalid or backwards timestamps require unlocking. An expired record is removed when Haze next checks it. Standard and Strict use their selected locking rules.
Local browser/app storage also holds preferences such as display currency, balance visibility, asset filters/favorites, security settings, cached market information, terms-acceptance version/time and relevant operation state. These records are not all encrypted with your wallet password. Web widgets operate from HazeWallet's origin; browser storage restrictions can affect persistence across sites.
Backup export produces an encrypted wallet file for a destination you choose. Native export uses a temporary cache file and the system share sheet. Your chosen file, cloud, email or messaging service receives a copy and applies its own practices. Private-key display/copy and paper-wallet recovery are local features; be careful with screenshots, clipboard history and cloud-synced files. Never send a wallet password, private key or wallet backup to support.
On iOS, optional Face ID/Touch ID protects a separate device-only wallet unlock key in Keychain. The app receives an authentication result, not your face or fingerprint data, and does not save your wallet password for this feature. It does not send this unlock key to HazeWallet. Biometric access is not a transferable recovery backup.
HazeWallet Chrome extension
The Chrome extension stores its password-encrypted wallet in its own browser IndexedDB, separate from hazewallet.com. Wallet passwords and unencrypted private keys stay on-device; unlocked keys are held in page memory. Preferences can be stored locally without wallet-password encryption. Restoring from the website requires your encrypted backup and password. Removing the extension or clearing browser data can remove this saved wallet.
The extension contacts the HazeWallet HTTPS relay for wallet/network data and signed-transaction broadcasts. Public addresses, network/token identifiers, balances/activity queries, amounts and signed transactions are processed to provide these services, as described below. It also contacts TokenPrinter (tokenprinter.fun) directly at its read-only PEP clean-output protection endpoint, sending a public address and transaction/output references to verify inscription carriers, reservations and current spendability. TokenPrinter receives the connection IP address and request metadata; this check sends no wallet password or private key. The relay and its network/edge providers can also receive IP addresses and ordinary connection metadata. All executable extension code is bundled locally. This release has no content scripts, browsing-history collection, website-content reading, dApp injection, extension telemetry, remote executable code or third-party frames. Optional MoonPay Buy/Sell pages open in a separate browser tab and revoke sensitive-action authorization; Standard/Strict lock the wallet, while Lenient may retain public viewing. Those pages follow MoonPay's privacy practices. Selected QR images are decoded locally. Opening external support or explorer links uses a separate browser tab and the destination applies its own privacy practices.
The Chrome extension's use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. HazeWallet does not sell extension user data, use it for advertising, transfer it for unrelated purposes, or use it to assess creditworthiness or for lending.
2. Address queries, transactions and network recipients
To show balances, spendable outputs, activity and transaction status, the wallet submits public addresses, selected networks, token identifiers and related transaction requests to HazeWallet's HTTPS relay. The relay queries configured nodes, RPC services and indexers. When you approve a send, it broadcasts the signed transaction, whose public contents include addresses, amounts and other network-required data. Signing keys and the wallet password are not needed by the relay.
The current deployment uses operator-run blockchain nodes and network-dependent services, including BlockCypher, Blockchair, SoChain, Dogechain, mempool.space, litecoinspace.org, Peppool.space and the configured Pepecoin Blockbook service at bongendpoint.realmasterkush.com. EVM reads/broadcasts use configured public network RPCs, including PublicNode, Alchemy, Base, Optimism, Avalanche, Arbitrum, BNB Chain, Gnosis, Cronos, Sonic, Kava, Kaia and Flare/Songbird endpoints. Solana uses its public mainnet RPC and Stellar uses Stellar Horizon. Only the services relevant to a query or fallback receive that query; this is not a claim that every service receives every wallet address.
Some Pepecoin features query TokenPrinter (tokenprinter.fun) directly for token balances, clean-output/protection checks and Whippet operations. These requests can include a public address, transaction/output references, token identifiers and signed public transaction or order data. Optional token creation/listing can publish user-selected project metadata or artwork. The iPhone app uses a restricted native network reader for PEP protection checks; those requests still reach TokenPrinter even though camera processing and signing are local. Services contacted directly can see your IP address and request metadata; relay-side providers generally see the relay connection, plus the query data.
Market and asset-artwork services use public coin/contract identifiers, including requests to CoinGecko/GeckoTerminal and DEX Screener, and cache results. Normal catalog/logo requests are served through HazeWallet or bundled assets rather than sending private wallet keys to an image service. Market queries can reveal which assets are of interest. Opening an independent block explorer shares the linked public address or transaction with that site.
Our nodes can import queried addresses as watch-only records and keep import/backfill status and operational messages containing those addresses. Watch-only records do not include spending keys. Blockchain transactions are public, may be linked to a person, and can remain indefinitely. RustCan LLC cannot erase or reverse public blockchain records.
3. Hosting, Cloudflare, logs and widget telemetry
The website and relay are self-hosted on RustCan LLC's Beelink infrastructure and delivered through Cloudflare. Cloudflare and the host process connection information such as IP addresses, requested URLs, timestamps, user-agent/request headers and security/error information to deliver traffic, prevent abuse and diagnose problems. Cloudflare can provide traffic/security analytics and set service/security cookies when its protections require them. Its processing and retention depend on the services/settings used and Cloudflare's privacy policy. We do not treat the absence of a browser analytics beacon as the absence of network or security processing.
The application uses in-memory IP-based rate counters. Ordinary API enforcement windows are one minute; entries can remain until reuse, size-based cleanup or process exit. Listing-request abuse controls separately use hashed client identifiers and one-hour windows. These controls are distinct from infrastructure logs.
The web embed reports coarse events such as widget loads, wallet opens/closes, creation, successful transaction events and errors. Its event store keeps the embedding site domain/origin, software version, event counts and first/last event times. It does not store wallet keys, passwords, addresses, balances or IP addresses in those event records; the HTTP request and security processing still expose connection information. Aggregate site counters and discovered domains can be visible on our public analytics page. No full embedding-page URL path is retained by this event store. The current native app suppresses the web wallet-create telemetry and contains no advertising or analytics SDK.
The site's normal design resources, fonts/fallback font choices and wallet libraries are served locally or bundled. There is no Google Fonts or advertising script included by the current main-page markup. Optional checkout, remote resources selected by a widget host, external links and updates can involve other providers. A site embedding HazeWallet can run its own analytics and has its own privacy practices; this policy does not govern that host's separate processing.
4. Support, listing forms and connections
If you email us, we process your email address, message, attachments and relevant support details to respond and investigate. Our support mailbox uses Private Email mail infrastructure. Only include a public transaction ID/address or device information if needed; it may reveal financial activity. Email providers and any destination you choose handle messages under their own practices.
The asset-listing form sends project name, ticker, network, public contract/website, contact email, notes and consent to HazeWallet. The server saves a private request/delivery record and queues forwarding to our support address when email delivery is configured. A queued acknowledgment does not mean that email was delivered or that an asset will be listed. A legacy onramp-introduction endpoint can save a submitted name, email, country, requested asset and message; no forwarding webhook is configured in this deployment. These are separate from wallet creation.
The per-asset provider-request feature creates an editable email draft locally. Opening the email/share application or provider's contact form lets you choose whether to send it. The chosen email service/provider receives what you send; Haze does not automatically send those drafts. Default drafts identify HazeWallet and the public asset/network, not your wallet secrets or balance.
If you approve a connection to a supported external application, it can receive the selected public address and a signed, scoped authorization challenge. This can link that address to an account/activity at the requesting application. Connection/session metadata can be held locally and by that application. The consent screen identifies the requesting site; a connection is not disclosure of your private key. TokenPrinter is a currently allowed connection recipient.
5. Payment, swap and MoonPay services
MoonPay is the provider for new Buy, Sell and Trade flows where the product and wallet channel are enabled. Selecting a flow sends the exact asset, network, amount and public receiving, source or refund addresses through Haze to MoonPay. Buy checkout is bound to the customer connection using a server-signed hash of its IP address. MoonPay also receives ordinary connection information when its pages open. Commerce merchant checkout is not enabled.
Buy and Sell use signed MoonPay pages. Payment, bank and identity-verification details are entered in MoonPay's checkout under its policies. Depending on the flow and eligibility checks, MoonPay may request your name, email, address, phone number, date of birth, identity documents, photographs or videos. Its verification providers may process biometric information under their own notices. Haze does not receive those documents or biometric data. The native payment view is separated from the wallet bridge; Chrome opens a separate browser tab. Sell currently uses MoonPay's deposit instructions and a separately reviewed manual wallet transfer. Opening or closing a page does not confirm payment or payout.
When you open Buy in an embedded widget, Haze checks the embedding site's origin. If you request site approval, Haze stores the site origin and your contact email to notify HazeWallet support and follow up about the request. Haze clears the contact email from its request record after the email provider accepts delivery and keeps a site marker to prevent duplicate requests. The email provider and HazeWallet support may retain the message separately.
Trade shares the selected source and destination chain/token identifiers, spend amount, slippage, source, destination and refund addresses with MoonPay Trade and the protocols used by the selected route. Haze verifies the route's native deposit request before showing its local signing review. Haze checks the signed funding transaction in memory before broadcast and retains its transaction hash for recovery; it does not retain that raw signed transaction in the MoonPay operation record. Public blockchain transfers and route protocols can link addresses and transaction activity.
Haze stores operation identifiers, a hash of the receipt access token, the approved asset/address/amount binding, provider identifiers, status, relevant transaction hashes and timestamps in private server records. Signed webhooks trigger authoritative status checks; only a minimal reconciliation hint is retained in the webhook queue. Local or exported activity receipts include a recovery token and must be kept private. A receipt cannot sign a wallet transaction or reveal a wallet key.
New Stripe/Link, SimpleSwap, Meld, Guardarian and Onramper initiation is retired. Existing authenticated legacy receipts can still be used for status recovery. Ordinary wallet sending and receiving remain available independently. Final provider fees, eligibility, limits and payment terms are shown in the relevant flow. See MoonPay's Privacy Policy and the exchange-service disclosure.
6. Retention and removal
- Local wallet and preferences: remain until you remove them or device/browser storage is cleared. Forget wallet removes the saved wallet record, not funds, all preferences or exported backups. iOS Keychain records can survive uninstall. Native temporary backup-sharing files are cleaned on a later launch; exported copies remain at their destinations.
- Watch-only addresses, import status and aggregate telemetry: no time-based automatic expiry is implemented. These records persist until operator removal or storage replacement. Watch-only data and logs are separate from public blockchain history.
- Asset-listing queue: records older than 90 days are removed on the next startup/background cleanup. Email copies are not removed by that job.
- Legacy introduction requests: the local file keeps up to the latest 500 submissions and has no time-based expiry.
- Exchange recovery: MoonPay operation and reconciliation records currently have no automatic time-based deletion. Pending legacy receipts remain available for reconciliation; terminal legacy records follow their adapter retention and cleanup rules. Local receipt histories are preserved rather than removed solely because of age or list size. Exported copies remain wherever saved. Ask us to review a Haze-held record for removal; provider-held records follow the provider's own policies.
- Support mail, local operational logs and operator copies: there is no uniform automatic deletion schedule. They are managed according to the support issue, security/investigation needs and applicable recordkeeping obligations. Ask us to locate and review a record for deletion. Mailbox, Cloudflare and other independent provider records follow their own settings/practices; application cleanup does not guarantee deletion of those copies or operator backups.
7. Why information is used and how it is protected
We use the information described above to provide requested wallet/network services, respond to support and listing requests, maintain service reliability, prevent misuse, recover transaction status and meet applicable obligations. Where data-protection law requires a legal basis, this can include performing a requested service/contract, legitimate interests in operating and securing the service, consent for optional disclosures where required, or compliance with a legal obligation. We do not claim that every privacy law applies to every user.
Controls include local password encryption/signing, HTTPS, native secure storage, approval checks and separation of private server records from publicly served files. Some operational/request records are stored as server files rather than encrypted wallet vaults. No system is guaranteed secure; protect your devices, backups and status receipts. Providers and public networks may process information outside your country, including in the United States. Protections and rights may differ by location.
8. Your choices, applicable rights and contact
Accounts and provider records: Haze wallets are created locally without a Haze account. Optional MoonPay services have their own account and verification flows. For MoonPay account deletion or access to MoonPay-held records, use the contact and rights instructions in MoonPay's Privacy Policy. For Haze-held data, follow the email instructions below. Provider legal retention requirements can apply after an account closes.
You can choose not to use optional provider/connection features, decline camera access, disable biometric access, change local preferences, disconnect supported application sessions, and remove local storage after safely backing up your wallet. Camera frames and selected QR images are decoded locally; paper-wallet private keys are validated on-device, not uploaded by the scanning feature. Scanning does not itself authorize a payment. Your browser/device controls cookies, storage, clipboard and permissions; blocking necessary storage can prevent wallet persistence.
Depending on the law applicable to you, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to processing, withdraw consent, appeal a decision on a request, or complain to your privacy regulator. Email support@hazewallet.com with the request and enough information to locate the relevant record. We may need proportionate verification; we will not ask for a wallet private key, wallet password or recovery backup. Rights can have legal exceptions, and we cannot delete public blockchains, files only on your device, or independently controlled provider data. Contact those services for their records.
9. Changes and related terms
We will update this page and its effective date when our practices change, including before a planned provider becomes active where additional disclosures are needed. Our Terms describe self-custody responsibilities. Privacy and support contact: support@hazewallet.com.