Desktop
Download
Privacy

Privacy Policy

How the wallet treats local settings, public onchain data, website requests and external ecosystem services.

Overview

Effective date: May 20, 2026. Arbitrum Wallet is designed to keep privacy expectations visible. Onchain activity is public by nature, local wallet preferences should stay on the user's device where possible, and external services are identified before they open.

This policy explains the website and desktop wallet experience for Arbitrum Wallet. It does not change the public nature of blockchain records or the separate policies of third-party services.

Scope

This policy covers the Arbitrum Wallet website, download pages and desktop app surfaces that are controlled by this project. It also explains what happens when the product links to official Arbitrum ecosystem resources, community channels, GitHub or external apps.

  • Public blockchain data is visible to anyone who can read the relevant network.
  • External websites and apps apply their own privacy notices, terms and security practices.
  • Users should review the destination domain before connecting a wallet or approving a transaction.

Wallet data

The wallet may process public addresses, token balances, transaction hashes, route details, network names and other public metadata needed to display balances, bridge flows and activity. This information may be requested from RPC providers, explorers, bridge services or other infrastructure used by the selected network.

  • The website does not ask for a recovery phrase or private key.
  • Do not share recovery phrases, private keys or signing codes with support accounts, websites or community messages.
  • Transaction data submitted to a blockchain becomes part of public network history.

Local data

The desktop app may store settings on the user's device so the product can reopen in a useful state. Local data can include selected networks, display preferences, recent route choices, cached balances and interface state.

  • Clearing app data may remove preferences, cached state and recent local history.
  • Device backups, operating system accounts and local disk security can affect who can access local app data.
  • If account import or signing is supported, key material should remain protected by the local account flow and should never be entered into the website.

Website data

When someone visits the website or downloads a release, normal delivery systems may receive technical request data such as IP address, user agent, referring page, requested file, date and time. This data is used to deliver pages, protect the service and diagnose operational issues.

The site does not need wallet connection data to show static docs, privacy text or download links.

Retention

Local app data remains on the user's device until it is changed, cleared or removed with the application. Operational website logs, if used, should be kept only as long as needed for security, reliability, debugging and compliance.

Public blockchain data cannot be deleted by this website or desktop app because it is maintained by the relevant network.

Your choices

Users can reduce unnecessary exposure by keeping sensitive material off websites, clearing local app data when needed, verifying release files and reviewing each external destination before connecting a wallet.

  • Use official domains and checksum links when installing builds.
  • Disconnect wallet sessions from external apps that are no longer needed.
  • Use a separate account for testing or for apps you do not fully trust.

Updates

This policy may be updated when the website, desktop app, analytics, release process or third-party integrations change. The effective date at the top of this page should be revised whenever the policy changes materially.