Privacy Policy

Last updated: May 18, 2026

The short version: Vamp Launcher is non-custodial. We never see your private keys, we never see your seed phrase, we don't store accounts. The only personal-ish data that leaves your device is your public Solana wallet address (because you signed a transaction on a public blockchain) and standard web request metadata to our infrastructure provider, Cloudflare.

1. What Vamp Launcher is

Vamp Launcher is a non-custodial token launcher for the pump.fun bonding curve protocol on Solana. It is distributed as:

A Chrome extension ("Vamp Launcher Lite") distributed via the Chrome Web Store
A web application hosted at vamplauncher.com/app

Both surfaces are operated by the Vamp Launcher team. This policy covers both.

2. What we DON'T collect

To be explicit, none of the following ever leave your device or enter our systems:

Private keys, seed phrases, or recovery phrases. The launcher never asks for them. Transactions are signed locally by your Phantom wallet via Phantom's window.solana injected provider.
Email addresses, names, or contact information. There is no account system. There is nothing to sign up for.
Browsing history or activity outside the launcher. The content script that adds the "V+" button to trading sites (Axiom, GMGN, Padre) only reads the visible token mint addresses on the current page to populate the launcher's clone form. It does not transmit your browsing history anywhere.
Trade history beyond what's on the public blockchain. We do not maintain a database of your launches, buys, or sells. Anything visible in the Positions tab is read fresh from Solana on each load.

3. What does technically leave your device

3.1 Your public wallet address

When you connect Phantom, the launcher reads your public Solana address so it can query your token balances and build transactions. This address is also written into every transaction you broadcast — it is on the public Solana blockchain and visible to anyone using a block explorer. We do not store it on our servers.

3.2 Token metadata requests

When you click "V+" on a token row to clone metadata, the launcher sends the token's mint address to our Cloudflare Worker (vamp-ipfs-proxy.mr-domino126.workers.dev) which fetches the token's public on-chain metadata. The mint address is public on-chain information. We do not log or persist these requests beyond Cloudflare's standard infrastructure logs (typically 24-72 hours).

3.3 Solana RPC requests

By default, the launcher routes Solana JSON-RPC calls through our Cloudflare Worker, which proxies them to Helius (a Solana RPC infrastructure provider). This means we technically see the RPC requests your launcher makes (e.g. fetching account balances, sending transactions). These requests contain your public wallet address and the on-chain operations you're performing — all of which is public information on the Solana blockchain anyway.

You can opt out of the worker proxy at any time by setting your own RPC URL in Settings (e.g. your personal Helius URL). When you do that, RPC requests go directly to your provider and bypass our infrastructure entirely.

3.4 Standard web request metadata

Our hosting provider, Cloudflare, automatically receives standard HTTP request metadata when you load vamplauncher.com or call our Worker:

IP address (for routing the response back to you)
User agent (browser identification)
Referrer URL
Timestamps

Cloudflare uses this data for DDoS protection, bot detection, and performance analytics on our behalf. Their data handling is governed by Cloudflare's Privacy Policy. We do not separately store or analyze this metadata.

4. What's stored locally on your device

The launcher saves a small amount of data in your browser's local storage (or Chrome extension storage when used as an extension):

Your preferred RPC URL (default: our worker proxy)
Your default slippage percentage

This data never leaves your device. You can clear it at any time by uninstalling the extension or clearing your browser's site data for vamplauncher.com.

5. Chrome extension permissions

The Vamp Launcher Lite extension requests the following Chrome permissions, each with a specific purpose:

storage — to save your RPC URL and slippage preferences locally
declarativeNetRequest — to strip Content-Security-Policy headers on supported trading sites (axiom.trade, gmgn.ai, padre.gg, axiompro.app) so the launcher iframe can be embedded for one-click cloning
Host permissions for trading sites only — to inject the V+ button on token rows. The extension has zero access to any other website

The extension does not request permissions to read your tabs, history, cookies, or any websites outside the four listed trading terminals.

6. On-chain transactions and the 0.5% platform fee

When you launch, buy, or sell tokens through Vamp Launcher, the transaction includes a SystemProgram.transfer instruction that sends 0.5% of your buy/sell amount to a fixed dev wallet. This fee instruction is part of the same atomic Solana transaction signed by your Phantom wallet — Phantom shows you the fee transfer before you approve.

Like all Solana transactions, the fee transfer and the transactions themselves are permanently and publicly visible on the Solana blockchain via any block explorer (Solscan, Solana Explorer, etc.). This is inherent to public blockchains, not something we control.

7. Third-party services we use

Cloudflare — hosting (Pages) and serverless infrastructure (Workers)
Helius — Solana RPC provider, accessed only server-side from our Worker
pump.fun — the on-chain bonding curve protocol your transactions interact with. Their privacy practices are governed by pump.fun's policy
Phantom — the wallet provider you connect to sign transactions. Their privacy practices are at phantom.app/privacy
DexScreener, IPFS gateways — public API calls made from our Worker to fetch token images and metadata. No user data is sent to them — only the token mint address being queried

8. Analytics

We do not use Google Analytics, Mixpanel, Amplitude, or any user-tracking analytics service. The website includes Cloudflare Web Analytics, which is privacy-focused, does not use cookies, and does not track users across sites. See Cloudflare Web Analytics for details.

9. Cookies

The launcher does not set any cookies. The marketing website (vamplauncher.com) does not set any cookies. Cloudflare may set technical cookies for DDoS protection and bot mitigation — those are not used for tracking.

10. Data retention

Because we don't have a database of users or trades, there is nothing for us to retain. Cloudflare's infrastructure logs are typically retained for 24-72 hours for security purposes, then discarded.

11. Children's privacy

Vamp Launcher is not intended for use by anyone under 18. Cryptocurrency trading involves significant risk and is restricted to adults in most jurisdictions. We do not knowingly collect any information from minors.

12. Your rights

Because we do not collect personal information, most data-subject rights (access, deletion, portability) don't have any data to apply to. If you would like to opt out of using our Worker proxy entirely, set your own RPC URL in Settings. If you uninstall the extension, all locally-stored preferences are deleted with it.

13. Changes to this policy

If we materially change this policy, we'll update the "Last updated" date at the top and post a notice on the website. Continued use after a change indicates acceptance of the updated terms.

14. Contact

For questions about this privacy policy or to exercise any rights described above, email [email protected]. We aim to respond within 72 hours. A community Discord is also planned for general discussion.