Skip to content

Privacy and data

A privacy tool that collects your data would defeat its own purpose. This page says exactly where the address you scan goes.

The scan engine is part of the page. Your browser asks public services for the address’s history and computes the score and the findings itself. The result stays in your browser.

The scan has to ask public services about the address. Your browser asks them directly, so each of them sees your IP address together with the address you scan, as it would if you looked the address up on its website yourself. Nymra’s server does not, except for a request the relay retries. If that matters to you, use a VPN. The threat model lists who sees what.

ServiceWhat it is askedWhy
Public block explorers: the Blockscout explorer of each chain, and RoutescanThe history of the address, and of a few related wallets such as its funderThe transactions, transfers and labels the findings are built from
Public RPC nodes, mostly PublicNode, plus some chains’ own nodesWhether the address sent a transaction or holds the native coinThe quick check per chain
Blockscout’s ENS service and a public Ethereum nodeThe ENS names the address owns, and the records of its primary namePublic identity
The Nymra relay, when an explorer refuses your browser, and for the chains it holds a key forThe same request as the explorerSo the scan can finish

When you enter an ENS name, the Terminal turns it into an address through a public Ethereum node, or Blockscout’s ENS service if that fails.

The exchange label list is part of the page, so looking up a label never leaves your device.

Normally your browser talks to the public explorers directly. When an explorer refuses your browser, because of too many requests or a bot check, the scan sends that request again through the Nymra relay at nymra.si/p. The relay passes it to the explorer and passes the answer back.

BNB Smart Chain and Linea are always read through the relay: their free API needs a key, and the key has to stay on a server.

  • The relay sees the request, so it sees the address you scan.
  • It keeps no log: no URL, no address, no IP address.
  • It forwards only the read requests a scan makes (an address and its transaction lists, and a few read-only node calls), only to the explorers and nodes in the open chain register, and refuses everything else.
  • Only Nymra’s own pages and services can use it. Another website that tries is refused, so it is no open proxy.
  • The explorer then sees the relay’s request instead of your browser’s.

The relay’s code is public in the privacy-scan repository.

  • No list of the addresses people scan.
  • No scan results.
  • No account, no cookie and no profile. No trackers, no analytics and no third-party scripts on the site or in the docs.
  • Nothing about who scanned what is sold, shared or published.

The image and the link you share leave the address out, unless you tick “Put the address on the card and in the link”; a warning then reminds you that anyone who sees them can see the address. With the tick, the link carries the address after a # (/terminal/#q=...). Browsers keep that part of a link to themselves, so the site’s host never receives it.

The Terminal can fill in your own address from a connected wallet. It asks the wallet for the address and nothing else: never a signature, a transaction or an approval. Pasting the address works the same.

These docs remember your light or dark choice in your browser, and the open state of the menu for the current tab. Search runs in your browser on an index that is part of the site.

Everything a scan shows was already public. Scanning a wallet does not make it less private: it shows what anyone with an explorer and patience could work out. Every link Nymra reports is a likelihood with a confidence, never a claim of who owns a wallet.

Questions about data or security: security@nymra.si.