Legal

Privacy

When launch notifications are enabled, the server sends confirmed public launch details to the operator’s configured Telegram chat: network, launch type, token and creator addresses, token metadata, verified purchase or liquidity amounts, wallet count, and explorer links. Telegram does not receive private keys, encrypted vault data, CSV files, wallet signatures or authentication cookies. Delivery records are stored separately from encrypted wallet records.

Token metadata, trades, and balances are read from supported networks. Wallet addresses appear on-chain whenever you sign a transaction. The launch-wallet vault stores creator, network, token, launch type (Direct V4 or Pons V2), launch-transaction and launch-wallet records, encrypted private keys, and balance snapshots in MongoDB. Wallet signatures create short-lived authentication sessions in secure cookies. Launch Club does not sell personal information.

RPC providers, your wallet, and the public block explorer will see the requests and transactions you initiate. Vault keys are sent over HTTPS to this server, encrypted before database storage, and never included in chain requests. The server operator can decrypt them; this is not end-to-end encryption. Only import dedicated first-buy wallet keys or CSV files into the wallet controls, never seed phrases or your main wallet key.

When the official Bubblemaps viewer is enabled on a supported network, your browser connects directly to Bubblemaps. The provider receives the public token address, network, public partner ID, your IP address and browser connection data, including this site’s origin. Its own site may use cookies or local storage. Launch Club does not send vault records, private keys or authentication cookies to the viewer. Unsupported testnets do not load it. Opening an external Bubblemaps link also connects you to that provider.

Private-key imports are validated in your browser. Drafts entered in the inline wallet editor are not sent to a server or included in CSV backups; canceling an edit discards its draft. Clicking OK adds the validated key to the wallet list and subsequent CSV backups. New direct-launch UI launches automatically save generated and imported wallet keys after confirmation. Existing direct launches can import their original CSV. Login challenges expire after five minutes, sessions after 15 minutes, and key save/export audit records after 90 days. Launch-wallet records and encrypted keys are retained until an operator-approved deletion request. Keep an independent offline backup.

The Pons V2 bundler also saves generated or imported sniper keys to encrypted MongoDB storage after launch confirmation, linked to the authenticated creator, Robinhood mainnet, token and declared exempt wallets. This background backup does not wait for successful sniper buys and does not delay their submission. Failed or unfinished saves require a retry with the original keys; keep the CSV until backup is confirmed. The server operator can decrypt these keys. With your explicit launch authorization, the browser signs the listed opening buys locally and sends signed transactions to Robinhood mainnet. A public-only tab session journal stores the network, approved amounts, wallet addresses, transaction hashes and wallet batch IDs for recovery, never private keys or signed raw transactions. Your connected wallet handles atomic call batches and may use its own execution provider. Closing the tab removes browser session data, but not the encrypted server backup or public on-chain records.