Privacy

What we see, written down.

A privacy product should be able to list everything that reaches it on one page. This is that page. No account, no analytics, no cookies, no trackers, no request log. One referral endpoint that stores public facts you choose to send. Everything else stays on your device or goes to parties we name below.

The data map

Four places your data can be. Only one of them is ours.

Your device

  • An encrypted vault: your recovery phrase's derived keys, your wallet map, your activity log, your settings. Locked with a password you choose; unlocked only in memory.
  • A cache of public pool notes so a refresh does not start from zero. Public data, same for everyone.
  • Your RPC URL and privacy profile.
  • An invite code you opened a link with, for seven days, until you apply or discard it.
  • The backup file you export, encrypted with a password of your choosing.

Stored by WiSP: never. Two items on this list are used in requests: the RPC URL you set, and an invite code when you apply it. Deleting your browser data or the backup removes all of it; the phrase brings back everything derived from it (one-time Receive addresses, when that feature is on, are recorded only in your backup).

WiSP's server

  • Serves the app and this site as static files. The server writes no access log and keeps no record of who loaded what.
  • Rate limiting counts requests per address in memory only; the counter is gone when the process restarts.
  • If you apply an invite code, the app sends: the code, the public address that shielded, the public signature of that shield, and your signature proving it. Stored to pay the referrer. All of it is public on chain except its attachment to the code.
  • If you create an invite code: the code, your public funding address as the payout address, and your registration signature.
  • An average $WiSP price over the last 24 hours, served to everyone alike, for the holder fee tiers.
  • If you paste a token address the app does not know, the app asks our server for that token's name and icon, by the token's address only. The server reads them from the chain and the token's own metadata host, caches them, and serves them from our origin, so the token's hosts never see your IP. Nothing says which wallet or account asked.
  • If the trade board is switched on (it is off in this deployment), the server reads the treasury's public trades from the chain and keeps them in memory to serve the board. Public data, the same for everyone; nothing about who looks at it.

Never: IPs on disk, emails, names, wallet maps, trades, balances, phrases, keys.

Parties we name

  • Your RPC provider. Every balance read, simulation and send goes to an RPC, directly from your browser and from your IP. By default that is Helius, on an endpoint WiSP pays for; you can set your own on the app's Privacy page. Either way it sees the addresses it is asked about, and, when you unlock or refresh, the spent-markers of your pool notes, which is how the app tells what your other device did. WiSP has no server in that path and receives nothing from it.
  • The pool's relayer (Privacy Cash) receives each exit from the pool: the zero-knowledge proof, the fee and the destination address. It cannot read who you are from the proof.
  • The pool's indexer serves the pool's encrypted notes, the same list for every user, so your browser can find yours. To learn where its own notes sit in the pool's tree, the app then asks the indexer for the positions of exactly those notes: the indexer sees which encrypted notes your browser selected, from your IP, though not what is inside them.
  • Jupiter, only for tokens that trade outside Pump: it sees the trading wallet, the token and the amount, as any swap aggregator would. It never sees your deposit or your other wallets. Its price list also supplies the SOL price and the price of those tokens, so the app can show what a holding is worth; that request carries token addresses only, never a wallet or an amount.
  • NEAR Intents, only when you arrive from or leave to another chain (Zcash, Bitcoin, Ether, USDC): the app asks its 1Click service for a quote and a deposit address from your browser, and checks the swap's state until it settles. It sees the amount, the destination and refund addresses you give and your IP, as any swap site would; WiSP holds no key for it and runs no server in that path. On an exit the pool pays its deposit address, so the public record is a pool withdrawal of that amount to that address, and a payout to Bitcoin, Ether or USDC is public on that chain (it answers status questions about a swap address to anyone, so the two can be matched; a shielded Zcash payout cannot); on an entry the SOL reaches your funding address from a swap, not from your other wallet. Its screening can hold or refund a swap; a refund returns to the refund address, or to your funding address on an exit.
  • The hosting edge (Fly.io) terminates TLS for the site, as with any website, and sees your IP in transit.

Each party sees its own step. The one that sees your funding address and your position wallets together, from your IP, is your RPC provider: choose it with care.

Solana

  • Your shield, every position wallet's trades, every sweep and every exit are public and permanent, like every transaction on the chain.
  • The fee to WiSP's treasury and buyback wallet is paid as public transfers in each trade.
  • Amounts and timing are visible; standard sizes and the slower privacy profiles exist to keep them from pointing back at you.

What the chain does not record: which of those wallets are yours. Amounts, timing and the fee transfers can still be correlated by someone who tries; the standard sizes and the slower profiles exist to blunt that.

Not collected

The usual list, each one absent by design.

No analytics, no trackers, no advertising

There is no analytics script, pixel or third-party tag on the site or in the app. The landing page's content security policy forbids every outbound connection; the app's allows only your RPC, the pool, Jupiter, NEAR Intents' swap service and WiSP's own app host.

How to checkView source: the policy is in the page header. Watch the network tab: the only hosts are the ones named above.

No cookies, no account, no email

WiSP sets no cookies and has no sign-up. Your browser's local storage holds your encrypted vault and settings for you, not for us; we cannot read it.

How to checkApplication tab → Cookies: empty for both hosts.

No request log

The app server does not write access logs. Your IP is used in memory to limit how many requests one address can make in a minute, then forgotten. The hosting provider's edge sees your connection as any host would; we do not export or store its logs.

How to checkThe server's behavior is described in detail on the Security page; source publication is an open item there.

No sale, no sharing, no profiling

WiSP does not sell, rent or share personal data, and uses none for advertising or profiling. The referral records exist to pay referrers and are not used for anything else.

Legal processThose referral rows are the only records we could ever be compelled to produce. What they contain is listed above.

Retention and deletion

You delete yours. We keep almost nothing to delete.

On your device: everything is under your control. Clear the app's storage or delete the backup and it is gone (locking the app keeps the encrypted vault in the browser). Keep the phrase and you can rebuild the account from the chain at any time; one-time Receive addresses, when that feature is on, come back only from a backup that lists them.

On our server: referral codes and claims are kept while the referral program pays out, because each payout re-checks them, and so is each code's daily total (credited, paid, owed), which the server shows only to a request signed by that code's payout address. There is nothing else. Ask us at info@usewisp.trade to remove a code you registered and we will, which ends its rewards; an address's totals are deleted with the last code that pays it.

On Solana: nothing can be deleted by anyone, including you and us. That is the public half of every entry in your log.

Age: WiSP is not directed at anyone under 18.

Changes: this page carries its last-updated date. A change in what the server stores is published here in the same release as the server.

Your RPC

The one party that sees your addresses together.

Any Solana app needs a node to read balances and send transactions. That node sees the addresses it is asked about, from your IP, which is the one place your wallets can appear side by side. WiSP keeps that party out of its own hands: the app talks to the RPC directly from your browser, with no WiSP server in between. The default is Helius, on an endpoint WiSP pays for so the app works the moment you open it; WiSP sees none of that traffic. Prefer a provider you chose? Paste the URL with your own key from Helius, QuickNode, Triton, Alchemy, Ankr, dRPC, Shyft, Syndica or Chainstack on the app's Privacy page, which always shows which endpoint is in use. A node you run yourself is not accepted yet: the page may only connect to those providers.

Nothing to leak, on purpose.

SecurityComplianceHome

last updated 2026-10-20 · questions and removal requests: info@usewisp.trade