← Home/Privacy Policy
LEGAL / UPDATED SEPTEMBER 29, 2026

Privacy Policy

This policy explains how fundadomain.fun handles information when you browse tokens, connect a wallet, launch a token, verify a website, or claim domain fees. It includes our use of Google Search Console data.

About this policy

This policy applies to the fundadomain.fun website and application services, operated under the name fundadomain.fun. External services, including wallet applications and Google, also have their own privacy policies.

Connecting a wallet and verifying a domain are optional. You can read this policy without connecting a wallet or accepting the risk notice. DNS and domain-email verification are alternatives to Google verification.

Information we collect

  • Wallet and transaction records: public wallet addresses, authentication signatures, prepared or submitted transactions, transaction identifiers, launch and claim status, and fee amounts. We do not request or store your connected wallet's seed phrase or private keys.
  • Token and website information: names, symbols, descriptions, uploaded images, metadata locations, mint addresses, and domains associated with launches.
  • Verification records: the domain, selected wallet, method, challenge status, attempts, expiry times, and verification time. Email verification processes an administrative address at your domain and a one-time code. Challenge secrets are stored as hashes. Google authorization temporarily stores a PKCE verifier for the authorization exchange.
  • Technical information: request timing, error and security records, and browser or network information processed by hosting providers. Application abuse-prevention records use a keyed hash of the requesting IP address; infrastructure providers may process the original IP address.

Google Search Console data

If you choose Verify with Google Search Console, we request the read-only permission https://www.googleapis.com/auth/webmasters.readonly. This permission allows reading Search Console information. Our implementation uses it only to retrieve the properties your account can access and their permission levels through Google's sites-list API.

We compare the returned property URLs and permission levels with the exact domain you submitted. Verification requires a matching Domain property with owner access. This check proves domain control so that the selected wallet can be authorized to claim that domain's fees.

The authorization code, access token, and returned property list are processed on the server for this check. We do not persist the access token or full property list in our application database, and we do not request a refresh token. We retain the verification result, domain, associated wallet, method, and timestamps. We do not retrieve your Google profile, Gmail messages, contacts, Drive files, or Search Console search-performance reports.

Google authorization data is not added to token metadata, uploaded to IPFS, or written to Solana. Infrastructure providers process it as necessary to run the verification request. We do not sell Google user data or use it for advertising, credit decisions, or training general-purpose AI models. We do not routinely provide humans access to the returned property list. Retained verification records may be accessed as needed for support and security.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

How we use information

We use information to perform requested actions: create token metadata, prepare and confirm launches, display token information and market activity, verify domain ownership, associate a domain with a wallet, and authorize fee claims. Operational records help prevent replay attacks and abuse, enforce challenge limits, diagnose failures, resolve disputes, and protect the service.

Domain verification authorizes fee claims. It does not certify a charity, orphanage, organization, token, or user-submitted description. Information you submit about a cause or website may be displayed publicly with the token.

Public blockchain and IPFS information

Solana wallet addresses, confirmed transactions, token activity, and fee payouts are public. Token names, descriptions, images, metadata, and linked domains are intended for public display. Verification status and on-chain payouts may reveal an association between a domain and a wallet.

Token images and metadata are uploaded through Pinata to public IPFS storage. Others can copy, index, or retain them. Do not include private information in descriptions or files. We cannot erase blockchain records or remove copies independently retained by IPFS nodes and other services.

Providers and sharing

We do not sell personal information. Information needed for requested features is processed by these providers:

  • Vercel and Neon: hosting, server execution, database storage, and associated technical records.
  • Google: authorization and Search Console ownership checks when you choose Google verification.
  • Email delivery provider: the administrative email address and verification message when email verification is used.
  • Pinata and IPFS: token images and metadata for public distribution.
  • Solana RPC and Pump.fun: public addresses, launch instructions, signed transactions, and related on-chain activity.
  • Dexscreener, Jupiter, and wallet providers: relevant public token or wallet information for charts, swaps, and wallet actions. Embedded services may receive your IP address, browser headers, and their own storage identifiers.

We may disclose necessary records to meet applicable legal requirements or address fraud, security incidents, or disputes. Providers may process information in countries different from your own. External services have their own privacy practices.

Cookies and browser storage

Local storage remembers acceptance of the risk notice. Session storage helps recover pending launches. Domain verification can create a short-lived, HTTP-only claim-session cookie; each fee claim also requires a fresh signature from the verified wallet. Wallet software and embedded third-party tools may maintain their own connection or preference information.

Clearing site data removes browser-held information and may interrupt a pending flow. It does not remove database records, revoke Google access, or erase blockchain transactions.

How we protect information

Safeguards include HTTPS, server-side credential handling, hashed verification secrets and session tokens, expiring challenges, request limits, wallet-signature checks, and restricted database access. Production claim-session cookies use security attributes. Google authorization uses state and PKCE checks. Access to retained records is limited to operational needs. No website, provider, or blockchain system can guarantee complete security.

Retention and deletion

We retain launch, domain-to-wallet association, verification, and payout records while needed to operate the service, authorize claims, maintain transaction history, investigate abuse, resolve disputes, or meet applicable obligations. There is no single fixed retention period for every record.

Google and email challenges expire after 10 minutes, DNS challenges after 24 hours, and claim sessions after 30 minutes. Expiry prevents further use; it does not automatically delete the database record. Google access tokens and returned property lists are not persisted in the application database. Provider logs and backups may have separate retention periods.

You may request review, correction, or deletion of off-chain personal information. We may need proof of control of the relevant wallet or domain. Records necessary for security, disputes, legal obligations, or ongoing fee ownership may need to be retained. Blockchain records and independently held IPFS copies cannot be deleted by us.

Your choices and Google access

You can decline Google authorization and choose DNS or domain-email verification. To revoke Google access, open your Google Account connections, select fundadomain.fun, and remove its access. Revocation prevents future use of that grant; it does not automatically erase a previously stored verification result.

You can disconnect your wallet through your wallet application and clear website browser data. Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of personal information. Exercising a right does not reverse an on-chain transaction.

Privacy questions and requests

For privacy questions or requests concerning Google verification, contact the developer using the support email shown on Google's consent screen for fundadomain.fun. Include the domain or public wallet address concerned, the information you want reviewed or deleted, and a way to reply. Never send a wallet seed phrase, private key, verification code, or Google access token.

Revoking Google access and requesting deletion are separate actions. We review requests against the retention needs described above and may ask you to demonstrate control of the relevant domain or wallet.

Policy updates

Effective September 29, 2026. Changes will be published on this page with an updated date. If our use of Google data changes, we will update our disclosures and request additional permission when required.