Information processed

ALPHA processes the wallet addresses you connect, the selected network, transaction hashes, the token details and image of a launch, and the technical request data needed to run and secure the service. ALPHA does not ask for your name, email address or phone number.

Signing in stores a session record on the server: a hash of the session token, the wallet, the network and the expiry. The sign-in message, the signature and your IP address are not kept. Linking wallets stores the link proof: the wallets, the signed message, the signatures, the time and the chosen name.

Diagnostic logs

When something fails, and at each step of a launch, a trade or a wallet connection, the browser sends ALPHA a diagnostic report. It holds the area of the app, the error text with addresses, hashes and long numbers masked, the page path without its query, the app version, the browser family, the screen size and the last few steps in the app. Launch and trade reports also hold the wallet address and transaction signatures, which are public on chain, and a failed transaction’s report holds its hash and a shortened sender address. Wallet connection reports hold the wallet’s brand name, never its address. Reports are kept for 30 days. Your IP address is never stored with a report; the client identity used to limit abuse is held in memory only.

ALPHA uses no analytics, advertising or tracking cookies.

Public by design

Blockchain activity is public and stays available independently of ALPHA. Wallet names, public profiles and linked profiles are public too: anyone can see what a wallet launched, holds and traded, and which wallets share a linked profile.

Browser storage and session

The interface uses browser storage for watchlists, drafts, chart layouts, pending transactions, the wallet connection and your acceptance of these terms. It sets only first-party cookies: one that remembers the entry acknowledgement for a year, one for the selected network, one that ties an uploaded launch image to your browser for seven days, and, when you sign in, a secure session cookie that the page itself cannot read. The session keeps profile changes signed in for seven days after its last use, at most 30 days, and never authorizes funds. Clearing browser data removes local preferences and drafts, but it cannot remove confirmed blockchain records.

Why information is used

Information is used to provide the features you ask for, keep sessions secure, prevent duplicate or unauthorized actions, recover pending transactions, investigate failures, protect the platform and meet legal obligations. ALPHA never needs your private key and will never ask for it.

Service providers and networks

Cloudflare carries every request to this site and sees your IP address and request details. WalletConnect (Reown) relays the connection between this site and a wallet app. Your wallet and its own network provider see the transactions you sign. ALPHA’s servers read the chains through public RPC providers and build routes through trading venues such as Jupiter, KyberSwap, Uniswap and Meteora, which receive the trade details and wallet address needed for that route. Launch images, and on Solana the token metadata, are stored permanently and publicly on Arweave. Each of these providers processes information under its own terms. A transaction sent to a public network is shared with that network and its participants.

Your controls

You can disconnect a wallet, sign out, unlink wallets, clear local browser data, remove saved drafts and decline optional actions. Send requests about information held by the service to ALPHA on X, @alphapadxyz. They must be authenticated, for example by a signature from the wallet concerned, before they can be completed. Legal retention, fraud prevention, security records and public blockchain records may limit deletion.