R0AR Wallet privacy and data

This page summarizes privacy choices in the extension. The public R0AR documentation and wallet privacy policy are available at docs.r0ar.io.

Wallet data and backups

Your recovery phrase or private key is encrypted with your wallet password before it is saved. The password is not stored or sent to R0AR. While unlocked, signing key material is held by the extension service worker and in Chrome's session-only storage so the session can survive a service-worker restart. It is cleared when you lock the wallet or the browser session ends. Device-unlock verification is handled by the browser and operating system; R0AR does not receive fingerprint or face data.

Account names and addresses, wallet settings, the address book, connected-site approvals, custom networks and tokens, transaction/activity records, portfolio history, NFT records, cached artwork, and provider-consent choices are stored locally in Chrome extension storage. Some portfolio and price records have separate encryption; not all settings and metadata use the wallet-vault encryption. OpenSea, Alchemy, and NFTScan API keys are stored in Chrome extension storage and are not encrypted at rest by R0AR. Custom RPC URLs may contain provider credentials, so protect your Chrome profile.

When you choose to export a backup, R0AR creates an encrypted .r0ar archive protected by the backup master password. It can include wallet accounts and settings, site approvals, portfolio and activity history, NFT gallery data and cached artwork, provider-consent choices, and saved OpenSea, Alchemy, and NFTScan API keys. R0AR does not upload the archive. You choose where to save it; any cloud or operating-system backup service you use has its own practices. Device-unlock credentials, Chrome host permissions, and active WalletConnect sessions are not transferred. The backup master password becomes the restored wallet's unlock password.

RPC, network, and price providers

When a wallet opens with network access enabled, token discovery checks a bounded range of ERC-20 transfer history through the selected RPC; balances and other blockchain features also use that endpoint. The scan may continue farther back when you choose Continue scan, and a wallet refresh or Rescan checks for newer transfers. Built-in public endpoints are operated by PublicNode. An RPC operator may receive your IP address, public wallet address, requested balances or other blockchain data, and connection metadata. Custom RPC requests go directly to the endpoint you select. R0AR does not proxy this traffic or control the provider's retention or use. Discovered token records and hide choices are stored locally for each wallet and network.

When you request approximate USD prices, DefiLlama receives asset identifiers and ordinary connection metadata such as your IP address, not your wallet address or balances. Last-known prices are cached on this device. When you choose to browse the RPC directory, Chainlist receives your IP address and request metadata; that request does not include your wallet address or balances.

NFTs and delegations

Manual ERC-721 ownership checks use the selected RPC and send it the contract address and token ID; they do not send your wallet address to an NFT indexer. NFT discovery choices are off until enabled. Ethereum discovery uses Blockscout. OpenSea discovery is available on its documented supported networks and requires your own OpenSea API key. Alchemy discovery is available on Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, and World Chain and requires your own Alchemy API key. NFTScan collection floors and rarity are available on BNB Chain and require your own NFTScan API key. Enabled NFT discovery and artwork-caching choices can be inherited by other wallet accounts on supported networks; Settings → Privacy lets you opt out each wallet separately. Collection market-data consent remains specific to the selected wallet and network. Selecting a wallet can start discovery automatically only when a discovery choice is enabled, the provider supports the selected network, its key is configured, and its Chrome host permission is already granted. Missing keys or permissions cause no provider request or permission prompt; manual discovery remains available in Collectibles. Discovery providers receive the selected wallet’s public address, network, IP address, and request metadata. Market-data providers receive NFT identifiers and selected chain, but not your wallet address or account name. OpenSea and NFTScan send keys in request headers; Alchemy sends its key in the request URL. Requests go directly from the extension to each provider; R0AR does not receive, bundle, or proxy these keys. Market-data requests start only when you choose Load floors & rarity and are not repeated automatically.

When automatic artwork caching is enabled for a wallet, selecting that wallet can request uncached images only from hosts with Chrome permission already granted. The HTTPS host named in NFT metadata or the IPFS gateways ipfs.io, dweb.link, and gateway.pinata.cloud may receive your IP address and the requested image URL. Artwork requests omit credentials and referrers and are not proxied by R0AR. Automatic caching does not request new permissions. You can still choose “Allow image hosts and cache artwork” in Collectibles to request permission for the exact image hosts needed. Artwork is cached locally when its source allows it. Opening Collectibles reads the local cache only and never requests uncached artwork by itself. When you load collection floors and rarity, OpenSea receives NFT contract addresses, token IDs, collection slugs, and the selected chain; NFTScan receives contract addresses, token IDs, and the selected chain. Neither receives your wallet address or account name. OpenSea may return a collection-level marketplace reference; NFTScan returns floor prices in the collection’s currency and rarity ranks when available. These are not guaranteed sale proceeds or item-specific sale values. Both requests require provider-specific consent and a personal API key and run directly from the extension.

When you choose to check incoming delegations, Delegate.xyz receives the selected public wallet address, network, IP address, and request metadata.

WalletConnect, websites, and swaps

If you choose to pair through WalletConnect, R0AR communicates with the WalletConnect relay. The relay may receive your IP address and connection or relay metadata; session message contents are encrypted between participants. The current wallet configuration disables SDK telemetry and peer-verification requests. App details supplied by a peer may be unverified.

A website you explicitly connect can read the approved public address and current network. It can request signatures or transactions, but each requires a separate approval in a R0AR-owned window. A website can independently observe public blockchain activity for an address it knows.

When you request a CoW Protocol quote, check an order, or request cancellation, R0AR contacts CoW Protocol directly at api.cow.fi. CoW may receive your IP address, public wallet address, chain, token pair, amounts, expiry, and signed order details. Your recovery phrase, private key, and wallet password are not sent. Any required token allowance is a separate on-chain transaction submitted through your selected RPC.

Use, sharing, and control

R0AR Wallet does not add analytics, advertising, or telemetry and does not sell wallet data. Data leaves your device only when you use the providers and connected sites described here. Those third parties have their own privacy policies. R0AR Wallet's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Use Settings to manage connected sites, provider access, saved history, and wallet data. Removing local data does not delete public blockchain records, copies held by third parties, or backup files you saved elsewhere. Chrome profile backups, operating-system backups, and other software on your device are outside R0AR's control.

For questions, use the R0AR Wallet publisher contact information shown in the Chrome Web Store listing.