Privacy Policy

1.1 Wallet and blockchain information

When you connect a wallet or interact with Popdex market features, we may process blockchain-related information, including your public wallet address, connected wallet status, pool, token mint, market, vault, LP mint, and Buzz Guard addresses, associated token account addresses and readiness status, public token account state, balances, reserves, liquidity-related information, nonce or replay-protection information associated with a pool interaction, transaction signatures, transaction status, confirmation status, and on-chain transaction, event, log, and account data related to Popdex pools or markets.

Popdex does not ask for, need, or intentionally collect private keys, seed phrases, passwords, or wallet recovery secrets. You should never provide them through the Service or support channels. Transactions are approved through your wallet provider, and Popdex cannot access your wallet using private keys or seed phrases.

1.2 Swap, trading, liquidity, Buzz Guard, and attestation information

When you preview or submit a swap, liquidity action, Liquidity Splay interaction, Buzz Guard interaction, or related action, we may process information needed to calculate, validate, attest, submit, and confirm the interaction. This may include the pool or market you interact with, action type, input amounts, minimum output amounts, liquidity amounts, Buzz Guard deposit or withdrawal parameters, route or readiness details, quote token mint information, nonce and timestamp expiry information used for attestation or replay protection, attestation request and response data, transaction signatures, and confirmation status.

Some preview calculations may occur locally in your browser. When you submit an on-chain action, information may be transmitted to wallet providers, Solana RPC providers, attestation infrastructure, and the relevant blockchain network.

1.3 Support information

If you contact us, email us, submit feedback, or open a support ticket, we may collect information you choose to provide. The support form requires a wallet address so Popdex can route, diagnose, and respond to wallet-, transaction-, pool-, chart-, or product-specific support issues. The support form may collect your email address, wallet address, issue category, issue description, optional transaction signature, hidden spam-prevention or honeypot fields, bot-prevention results, rate-limit information, delivery status, and related technical metadata.

Popdex uses Resend for support email delivery, and received support messages may be stored or processed in Google Workspace. Support channels are not intended for seed phrases, private keys, passwords, or other wallet recovery secrets. Never share seed phrases or private keys. If you include wallet recovery secrets in a support message despite these instructions, they may be processed as part of that message, but Popdex does not use them to access wallets and may delete, restrict, or decline to process them where feasible.

1.4 Technical information, logs, and abuse prevention

When you access the Service, Popdex and its hosting providers, infrastructure providers, RPC providers, attestation services, wallet providers, analytics providers, bot-prevention providers, and other service providers may automatically process technical information, such as IP address, browser type and version, device and operating system information, user-agent string, pages or routes requested, referring URLs, timestamps, request metadata, network logs, error logs, security events, and abuse-prevention signals.

Popdex uses Vercel, Vercel logs, Vercel Analytics, BotID, rate limiting, hidden spam-prevention or honeypot fields, and similar safeguards to operate the Service, understand product performance, detect automated abuse, and protect support endpoints and APIs. For support and telemetry rate limiting, Popdex may process IP address or forwarded-IP header values and derive hashed source-IP-derived rate-limit identifiers used to enforce short active quota windows and prevent abuse.

1.5 Product telemetry and analytics

Popdex may collect product telemetry and analytics to understand usage, diagnose errors, improve reliability, and prioritize product work. This may include page views, route transitions, feature usage, client-side error events, wallet connection status, truncated or hashed wallet identifiers, pool identifiers, transaction status events, timing information, browser and device information, and session identifiers such as a browser session value stored in session storage.

Product telemetry is intended for operations, security, debugging, and product improvement, not for selling personal information or cross-context behavioral advertising.

1.6 Cookies, local storage, session storage, and similar technologies

Popdex does not use application cookies, local storage, or session storage for advertising or cross-site behavioral tracking. The Service may use browser storage for operational needs, such as wallet connection state, client-side session identifiers, UI state, analytics events, and error handling.

Browser wallets, wallet-adapter libraries, hosting providers, security services, analytics tools, or future product features may use cookies, local storage, session storage, or similar technologies. If we add non-essential cookies, advertising, or cross-site tracking in the future, we will update this Privacy Policy and, where required, provide appropriate notices and choices.

1.7 Public blockchain and Popdex-indexed data

Blockchain networks are public by design. Wallet addresses, transaction signatures, account addresses, transaction metadata, token transfers, program interactions, and related on-chain activity may be publicly visible, indexed by third parties, and retained indefinitely by blockchain networks and independent infrastructure providers.

Popdex may index, cache, or store public blockchain and pool data in operational databases, including Neon, and may retrieve public chain data through providers such as Helius or other Solana RPC providers. Popdex generally cannot delete, modify, or hide information that has been written to a public blockchain.

Where Popdex controls an off-chain indexed copy, Popdex may delete, suppress, correct, or retain that copy according to operational, legal, security, and product needs, but doing so does not affect the public blockchain or copies held by third parties.

3.1 Blockchain networks and validators

When you submit a blockchain transaction, transaction data is broadcast to the relevant blockchain network and may be processed by validators, RPC providers, indexers, block explorers, analytics providers, and other third parties. This information may become public and permanent.

3.2 Wallet providers

When you connect a wallet or approve a transaction, your wallet provider may receive information about the connected site, requested connection, transaction details, and other wallet-provider-specific data. Your use of a wallet is subject to the wallet provider's own terms and privacy policy.

3.3 Solana RPC providers and blockchain infrastructure

The Service uses configured Solana RPC endpoints to read pool, account, transaction, and wallet-related readiness data and to submit or confirm transactions. RPC providers such as Helius or other configured providers may receive public wallet addresses, pool account addresses, transaction signatures, signed transactions, IP addresses, user-agent information, timestamps, and request metadata, depending on how the Service is deployed and configured.

3.4 Attestation infrastructure

For supported swap, trading, Splay, or Buzz Guard interactions, Popdex may send attestation request data to an attestation signer or upstream attestation service. This data may include public wallet address, pool address, token mint addresses, action type, amounts, minimum outputs, nonce, and related transaction parameters.

3.5 Hosting, cloud, analytics, security, and database providers

We use hosting, cloud, logging, analytics, security, CI/CD, repository, database, and development-service providers to operate and maintain the Service. These providers may process technical information such as IP address, request metadata, logs, device and browser information, analytics events, security events, and operational data. Current providers include Vercel, Vercel Analytics, BotID, Neon, and other infrastructure providers. We may add, remove, or replace providers as the Service changes.

3.6 Support and communications providers

We may share support ticket and communication information with providers that help deliver, receive, store, and manage communications, including Resend and Google Workspace. These providers may process email addresses, message contents, ticket metadata, delivery metadata, and related technical information.

3.7 Legal, compliance, and safety

We may disclose information if we believe it is necessary or appropriate to comply with law, regulation, subpoena, court order, legal process, or governmental request; enforce our terms, policies, or agreements; protect the rights, property, or safety of Popdex, users, or others; or detect, investigate, or prevent fraud, security issues, sanctions evasion, market abuse, or technical issues.

3.8 Business transfers

If Popdex is involved in a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, or similar transaction, information may be disclosed or transferred as part of that transaction, subject to appropriate confidentiality or legal protections.