Privacy

Short version: VAPE has no accounts, sets no cookies and runs no analytics or trackers. Your settings and the coins you star stay in your own browser.

What stays in your browser

• Display settings and stars — chains, filters, theme, chart mode and the coins you star live in this browser's localStorage. VAPE's server never stores them; to show a starred coin's figures, the page asks the server for that coin the same way a coin page does (below).
• Your connected wallet — if you connect a wallet to trade, this browser remembers its public address and keeps a local copy of your trade receipts until you disconnect your last wallet.
• Anyone who uses this browser profile can see what is stored there; a private window forgets it when it closes.

What leaves your browser, and who sees it

Every request carries your IP address, as all web requests do. VAPE's pages tell your browser to send no referrer, so the services below are not told which VAPE page you were on, and VAPE sets no cookies of its own.

• VAPE's server (the public instance is hosted by Hugging Face) — the boards and coin pages you open, including the coins you star, a few at a time. The classic page's rotation read also sends up to 12 of your classic-page stars, so the server can read those coins' tapes; the new terminal does not.
• Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — both pages load their fonts from it.
• Coin logos load from wherever each coin's listing hosts them — usually DexScreener's image servers (dd.dexscreener.com, cdn.dexscreener.com), sometimes CoinGecko's or X (Twitter)'s.
• DexScreener (api.dexscreener.com) and GeckoTerminal (api.geckoterminal.com) — the new terminal asks them directly from your browser during ordinary use, not only for a pasted address: on the boards, on coin pages and their charts, and in search. Those reads carry no cookies and no referrer; the services see the coin and pool addresses asked about. The classic page does not ask them.
• The Base and Robinhood Chain public nodes (mainnet.base.org, rpc.mainnet.chain.robinhood.com) — on the new terminal, a Base or Robinhood Chain coin page's chart reads the pool's live trades from them, with no cookies and no referrer; the nodes see the pool addresses asked about. The classic page asks them only if you trade (below).
• Binance (fapi.binance.com) — the classic page's paper-desk BTC chart.
• If you trade — quotes and swaps go from your browser to KyberSwap (aggregator-api.kyberswap.com: the new terminal's Base and Robinhood Chain routes) and the chain's public node (mainnet.base.org, rpc.mainnet.chain.robinhood.com), or to Jupiter (lite-api.jup.ag, api.jup.ag: Solana). They see the tokens and amounts, and your public address once a swap is built. Your wallet app talks to its own node under its own policy. Solana balance and transaction-status reads go through VAPE's server, which shields your IP address from the node; the address passes through, may sit in a short in-memory cache, and is never written to disk or logged.

What VAPE's server keeps

• No record of who asked for what. Request logging is switched off in the code. The server counts how often each part of the site is used (paths only, no IP addresses). To limit abuse it keeps a per-connection request counter in memory, keyed by a salted one-way hash of the IP address — a new salt at every restart, so the raw address is never stored. When a coin read is unusually slow it notes which coin the read was about — never your IP address.
• Hugging Face, which hosts the public instance, sees standard request data (IP address, browser, the URL requested and the time) under its own policy.
• Trade receipts — optional, sent from your browser after a trade you make. They are stored under a keyed hash of your address, not the address itself, so the database cannot be listed to learn who trades here. The public site answers a lookup by address with counts only — how many receipts are verified, refuted or still unverified — never the receipts themselves. Receipts stay unverified until VAPE's own chain read confirms the transaction.

When accounts ship

A future release may add optional accounts. If it does, this policy will be updated before launch to state exactly what is stored and by whom; sessions will use httpOnly cookies, credentials will never appear in URLs, and account data will never be sold. The same applies before any fee features ship.

Your rights

If you are in a jurisdiction with data-protection rights (for example the GDPR), you have the right to access, correct or erase personal data we hold. Beyond transient infrastructure logs, the one thing VAPE stores that traces to a wallet is the hash-keyed receipt ledger described above; your settings and stars are in your own browser, under your control. Questions or requests: contact the operator via the channels linked from the terminal.

Changes

This page is versioned with the product; material changes are stated here.

VAPE v578.61 · This page is served by the engine itself and describes the product as currently shipped. · Disclaimer · Privacy · Security