ZAPSdocs
How Zaps Works

Privacy & the Wallet Promise

Your X identity is never publicly mapped to your wallet addresses. Here is exactly what is public and what is not.

Live now

The question every trader asks before linking a wallet: "if I connect, does my X identity get publicly mapped to my wallet addresses?"

The answer is no. This page is the promise, stated plainly.

The wallet promise

  • The link between your X account and your wallets is private. It exists only to compute your scores.
  • Wallet addresses are never displayed on any profile, feed, roster, or leaderboard.
  • Public surfaces show derived results only: scores, zaps, aggregate volume, protocols touched. Never which wallets produced them.
Aggregates are public · Addresses are not · No 0x on any public surface

What this means in practice

Your public profile shows your trading day the way a scoreboard would: trades today, volume today, zaps earned, the protocols you touched. All of it is derived from activity that is already public onchain. Zaps makes that activity legible, without ever revealing which addresses it came from.

Enforcement is technical, not editorial: no wallet address appears in any public response from the platform, and addresses are never sent to analytics.

Why trading data is shown at all

Your trading history is already public. That is what a blockchain is. What Zaps adds is interpretation: turning raw onchain activity into scores, standing, and proof, attached to an identity you chose to claim. What Zaps never adds is the reverse mapping. Nobody can go from your name to your wallets through Zaps.

Connecting costs nothing

Linking a wallet is a free signature that proves ownership. It is not a transaction, requires no gas, and grants Zaps no control over funds. Zaps is non-custodial everywhere: your funds never touch the platform, and trading always happens from your own wallets on the venues you already use.

On this page