Your key stays.
Know what travels.

On your device

DOVR generates and restores wallet keys in your browser. The saved private key is encrypted using your password and stored in the browser’s local database, alongside its public address and wallet format information.

Your password, complete DOVR1 recovery code and decrypted private key are not sent by the wallet to DOVR’s server or an RPC provider. Unlocking decrypts the key locally. The recovery code is unencrypted and gives control of the wallet; save it offline.

The browser also saves pending transaction information, including the actual signature and public transfer details, so an interrupted submission can be checked. A local cross-tab signal contains the public wallet address and a timestamp to coordinate wallet state.

Network requests

Loading the website sends ordinary connection information to DOVR’s hosting provider, such as your IP address, requested URL and browser request headers. The site checks mainnet connectivity using public network information; this does not require a wallet address.

Check wallet

After your disclosure acknowledgement, the wallet sends your public address to DOVR’s service. Its configured Solana RPC receives the address and requests for its balance and recent signatures.

Prepare a transfer

DOVR’s service receives the sender, recipient and amount. The RPC receives the transaction information needed to read fees and simulate the transfer.

Submit and reconcile

The service and RPC receive the signed transaction or its signature. A signature authorizes the exact signed message; it is not your private key.

For requests proxied by DOVR, the RPC sees DOVR’s server connection while the hosting service sees your connection. Direct connections made by a protocol SDK can disclose your IP address to that provider. Provider logs and retention are controlled by the relevant service; DOVR does not promise that these requests are anonymous or unlogged.

Signatures

Each wallet signature requires its own review. The review identifies the network, request and relevant amounts, recipients, programs or fees before approval. Reject a request if the details do not match the action you intended.

Umbra can request a deterministic message signature to derive protocol keys locally. That derivation signature is separate from a transaction and does not by itself transfer SOL. Protocol transaction signatures can spend real value and are reviewed separately.

Locking the wallet, hiding the page or leaving the signing flow cancels a pending review. A transaction already submitted to the network cannot be cancelled by closing the page.

Protocol providers

DOVR integrates Umbra’s V18 mainnet encrypted balances and includes preview support for recipient transfers and Stealth Pool notes. These operations depend on third-party programs, cryptographic components and supporting services, including RPC, computation, note discovery and relay services.

Depending on the operation, these providers receive public wallet or account addresses, encrypted protocol data, note or claim information, transaction signatures and request metadata. Encryption of a balance does not hide every account interaction or the fact that you used a service.

Note discovery, proof generation, claim submission and staged recovery have different responsibilities. Service availability is not a guarantee that a private transfer or withdrawal has completed. Funded tests verified a deposit, restored-session balance recovery, own-queue reset and withdrawal to the same wallet as native SOL. A separate recipient transfer did not settle; its underlying cause remains undetermined. Recipient settlement and Stealth Pool note redemption remain unverified, and new recipient value writes are disabled in this release.

Read Umbra’s protocol documentation and DOVR’s private-route explanation to understand these boundaries. DOVR does not claim an independent audit of its integration or of third-party services.

Public records

Solana is a public ledger. Ordinary SOL transfers publish the sender, recipient, value, signature and related account activity. Receiving SOL at a DOVR address does not make that address private.

Protocol deposits and withdrawals have public entry and exit points. Their amounts, timing and associated accounts can reveal information even when a balance or note is encrypted. Direct encrypted-amount transfers also expose both participants and their relationship. Stealth Pool notes use a separate maturity, proof and claim mechanism; they are not immediate transfers.

Public chain records cannot be removed by clearing this site’s storage. Opening a Solana Explorer link also sends a request to that separate website.

Your choices

• You can read the site and create or restore a local wallet without requesting that wallet’s balance.
• You acknowledge the public-data disclosure before checking the wallet or preparing a public transfer.
• You can reject a signature review and lock the wallet whenever you finish.
• You can clear DOVR’s site data through your browser settings. Save your recovery code and unresolved signatures first.

Clearing local data does not erase public blockchain records, reverse submitted transactions or delete information already handled by independent providers.