Risks & disclosures

Current availability

Financial services are not enabled in this preview. Do not send funds to example addresses or dashboard images. A registered account or .nu name does not mean that receiving, payments, swaps or messaging are active.

Passkey wallet creation and secure export/recovery are also not ready for public use. The help instructions describe how supported flows are intended to work when available; they are not confirmation of a live route.

Privacy is not anonymity

A receiving request is designed to avoid sharing your main wallet address directly with the sender. That is a specific privacy benefit, not a promise that no one can link transactions or identify you. Deposits and withdrawals occur on public networks and can be observed and analyzed.

Confidential Intents is intended to reduce public visibility within supported operations. NUvault, connected providers and infrastructure participants can still process information needed to authenticate accounts, execute requests or investigate failures. Applicable provider disclosure and access rules still matter.

Names, contacts, messages, timing, amounts and information you share elsewhere can reveal relationships. A theme switch changes appearance only. No part of NUvault should be treated as a guarantee of anonymity or protection against every observer.

What NUvault is built on

NUvault’s financial integration is built around NEAR Intents and 1Click, with Confidential Intents planned for private balances and supported operations. NUvault supplies its own account experience, .nu name service and interface. It is an independent product, not near.com or an official NEAR-operated service.

Passkey wallets are designed to use Privy infrastructure, and WalletConnect provides a separate wallet connection option when enabled. Messaging has its own integration and remains unavailable here. Each service has dependencies beyond NUvault’s control.

The links below describe third-party technology. They supplement NUvault’s own terms and disclosures; they do not replace them or confirm that a particular NUvault feature is available.

Execution, bridges and network risk

Routes can depend on liquidity, bridges, validators, smart contracts and service APIs. Software defects, congestion, interrupted access, incorrect data or infrastructure failures can delay or prevent settlement and may cause loss.

A transaction hash is evidence of a network operation, not necessarily proof that every later step completed. If submission is uncertain, check the original operation rather than signing another payment. NUvault’s ability to display status depends on information supplied by the relevant services.

Receiving addresses and refunds

Use only the asset, network, address and memo specified by a current request. Do not reuse an address unless the current service explicitly allows it. An expiry, minimum or memo requirement is part of the request, not optional advice.

Late, repeated, incorrect or unsupported deposits can require manual investigation and may be lost. Refunds can incur costs or delays and are not guaranteed. NUvault cannot reverse an external blockchain transfer simply because it was sent by mistake.

Wallet control and recovery

Your wallet and its authentication methods control access. A NUvault name and browser session are not replacements for wallet recovery. Loss or compromise of keys, passkeys, backups or trusted devices can result in lost access or assets.

An embedded wallet also depends on its provider’s security and recovery design. Do not assume that a passkey means recovery is automatic or that every export method is supported. NUvault’s embedded-wallet recovery/export work must be completed before that option is enabled.

Value, fees and service restrictions

Cryptoasset values can change sharply. Stablecoins can lose their intended peg; token issuers may have controls or restrictions. A balance display is not a guarantee of market value, immediate liquidity or the ability to withdraw at any time.

Fees, minimums, routes and eligibility can change. No email or KYC is requested for NUvault account creation, but that does not waive a connected provider’s screening, eligibility or legal requirements. Do not use a service to evade restrictions that apply to you.