First Row / Data overview
Understand what stays local. And what becomes public.
Data handling depends on the features enabled for this deployment. Without First Row sign-in configured, the site provides a local draft preview. Connected account and mainnet actions use the services and records described below.
Your browser draft
The nomination and launch forms keep the entered X handle, optional note, token name, ticker, description and current step in this tab’s session storage, with an in-memory fallback. Writing or reviewing a draft alone does not send those fields to the First Row backend or look up the creator on X.
Reloading can restore a draft. Closing the tab normally ends its storage session, although browser session restoration may restore it. Anyone able to use your open browser tab can view it. It is not an encrypted private message.
Sign-in and identity checks
When enabled, X and Privy handle sign-in. First Row sends a Privy access token to its dedicated Convex backend to authenticate requests. The backend retrieves the linked X identity from Privy and stores the Privy account identifier, numeric X ID, handle, display name and verification time. It also uses the X API to resolve a nominated handle to its numeric account identity.
Connecting a Solana wallet shares its public address with the application and wallet provider. It does not by itself authorize a payment or designate a creator payout wallet. Wallet signatures are requested separately for the specific claim or withdrawal you review. Typing an X handle does not sign you into X or connect an X Money account.
Saved nominations and transaction records
Choosing Save nomination sends the draft details to First Row’s Convex service. Account records associate the nomination with its owner and the verified creator identity. Pending nominations and optional notes are access-controlled in the application; this does not make them inaccessible to service operators or their infrastructure providers.
Launch and payout workflows retain the details needed to prepare, submit and reconcile transactions. These include public wallet and mint addresses, metadata references, transaction messages and signatures, status, timestamps and observed balances or chain slots. Signed transaction records are retained to reconcile uncertain submissions and retry the same transaction safely.
Do not include secrets or sensitive personal information in an optional note or token details. First Row does not request your wallet’s private key or recovery phrase through these forms.
Metadata, confirmed launches and public chain data
Preparing a token can upload its name, ticker, description, image reference and creator attribution to a retrievable metadata URL before the token launch is confirmed. Token details are intended for publication. An unpublished listing is not a guarantee that its prepared metadata is confidential.
Confirmed listings can display creator attribution, token details, mint addresses and transaction links. Solana transactions, wallet addresses, token ownership, claim bindings and transfers are public chain data and can link an X identity to a wallet. Other sites may copy, cache or index metadata and chain records.
Removing a local draft or an application record does not erase confirmed blockchain history or copies held by third parties.
Hosting and external services
Vercel delivers the website. Privy, X and Convex support the enabled identity and application flows. Solana RPC services, wallets and Pump.fun handle the corresponding network and market interactions. Requests can create operational records such as network, device, request and error information with the relevant service.
Following a market, explorer or other external link sends you to that provider. Each provider’s own data practices also apply. Availability and data processing can change when the operator changes a provider or enables an additional feature.
Storage controls and remaining operating details
You can clear the browser draft using your browser’s site-data controls and sign out of an enabled account. Those actions do not delete backend records, hosting logs, published metadata or onchain transactions. No automatic backend deletion or fixed retention period is promised by this page.
Before public account and transaction features are enabled, the operator must publish its identity and contact route and finalize retention periods, applicable user rights and a process for account or data requests. A legal and privacy review of those operating details remains an activation requirement.
