1337
Download for Chrome

Privacy

Privacy policy

Keep all user data where it belongs on the user's machine. 1337 Wallet is private by design: no analytics, no tracking server, and no 1337 collection of your data — ever.

Last updated 18 September 2026.

Who we are

1337 Wallet is a self-custody Chrome extension. This policy describes what the extension stores on your device and when it talks to the network. There is no 1337 account, no analytics SDK, and no tracking server that receives your vault. There never will be. Responsibility for keys and funds is in the terms of use.

Contact: GitHub · Discord · X.

Private by design

Privacy is only possible when there is no central entity with the power to violate it. Other wallets keep that power: analytics, accounts, or a server that could watch you. 1337 does not. Keep all user data where it belongs on the user's machine. We cannot collect, sell, or leak what we have no endpoint to receive. That is architecture, not a policy we might relax later. See also the privacy FAQ for a side-by-side with MetaMask and Rabby.

What stays on the user's machine

The extension uses Chrome storage on this browser profile:

  • Encrypted vault (seed / private keys) in chrome.storage.local
  • Wallet settings, custom RPCs, and chain preferences in chrome.storage.local
  • Unlocked session (active key metadata) in chrome.storage.session until lock or browser restart

Software keys are encrypted with your password before they are written to disk. Hardware accounts store address and derivation path only. Private keys stay on Ledger or Trezor.

When the extension uses the network

1337 does not phone home. Requests leave your machine only when you use a feature that needs a third party:

  • Public RPC endpoints you choose (balances, sends, dapp reads)
  • LI.FI API when you open Swap or fetch routes (integrator id only; no 1337 backend)
  • Optional Etherscan-compatible API key you paste in Settings (sent to the explorer provider for tx history)
  • Optional The Graph API key for ENS portfolio listing
  • Ledger / Trezor device SDKs and Trezor Connect (connect.trezor.io) when you use hardware accounts
  • Token logos and chain metadata from public HTTPS URLs (e.g. LI.FI catalog)

Those providers see whatever that request contains (for example an address on an RPC call, or a swap quote from LI.FI). We do not operate those services and we do not receive a copy.

What we never collect

  • Analytics, telemetry, crash reports, or usage metrics — now or later
  • Anything sent to a 1337 server. There is no such server, and there will not be
  • Browsing history beyond what Chrome grants for dapp connection
  • Wallet addresses or balances sent to a 1337 database
  • Email, phone, or social login

Dapp connection

Connecting a site shares your selected account address with that origin through the standard Ethereum provider (EIP-1193 / EIP-6963). You can disconnect per site in Settings. The extension injects a provider so dapps can request signatures; it does not sell browsing history.

Children

1337 Wallet is not directed at children. Do not use it if you are not old enough to custody crypto in your jurisdiction.

Changes

If this policy changes, we will update the date on this page. We will not add analytics or a 1337 collection server. New third-party destinations appear here if we add a feature that calls them — those calls still do not phone home to us.

Terms of use · Security · FAQ