Privacy Policy

Wallet addresses. When you connect a wallet we see its public address. We record addresses that launch tokens, hold tokens we are calculating payouts for, and claim payouts. These are already public on-chain; we index them so the Service can function.

Token balances over time. Payouts are time-weighted, so we periodically record how much of a token each address holds. This builds a history of your holdings for tokens launched here.

IP address. Used to rate-limit abusive traffic and to determine the country a request comes from, so we can show the notices some jurisdictions require. We do not build advertising profiles from it.

Content you submit. Token names, symbols, descriptions and images. These are published on-chain and to IPFS, permanently and publicly.

Correspondence. If you email us, we keep the email.

We do not collect names, postal addresses, dates of birth, government identifiers or payment card details, because the Service never asks for them. Never send us your private key or seed phrase — no legitimate request for these exists, and we will never ask.

To operate the Service: indexing holders is how payouts are calculated; recording claims is how we prevent the same payout being claimed twice; recording trades is how we determine what holders are owed.

To protect the Service: rate limiting depends on identifying repeat callers.

To comply with law: including showing jurisdiction-specific notices and responding to lawful requests.

We use third parties to run the Service. Each sees only what its function requires, and each has its own privacy policy:

Hosting and database — our application host and managed database provider store the data described above. Blockchain data providers — we query Solana through third-party RPC providers, which see the addresses we ask about. Swap routing — quotes and swap transactions are built by a third-party aggregator, which receives the addresses and amounts involved. IPFS pinning — images and token metadata are uploaded to a pinning provider and published to the public IPFS network.

We do not sell your data, and we do not share it for advertising. We may disclose data where required by law or to protect our rights.

You may ask us to delete data we hold in our own database, and we will do so where we are not required to keep it. But two categories are outside our control entirely.

Transactions on Solana — every launch, trade, distribution and claim — are permanent, public and replicated across a network we do not operate. Nobody can delete them.

Images and metadata pinned to IPFS are addressed by their content and may be copied by any node on the network. We can unpin our own copy, but we cannot guarantee removal from the network.

Deleting our records would also not remove the underlying on-chain activity, and may prevent you from claiming payouts you are owed.

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing of your personal data, to data portability, and to complain to a supervisory authority. Where we rely on legitimate interests, you may object.

Because we hold no account identifying you, we may be unable to link a request to specific data without you demonstrating control of the relevant wallet.

We do not currently publish a support address. Until we do, the practical way to limit what we hold is to stop transacting through this site — nothing further accrues once you do.

Holder snapshots and distribution records are retained while they may be needed to calculate or evidence payouts. Rate-limiting records are short-lived. Correspondence is kept while relevant.

The Service does not use advertising or tracking cookies. Your browser may store data locally so the interface can remember your wallet connection; this stays on your device.

The Service is not for anyone under 18 and we do not knowingly collect data from them.

Our providers operate globally, so data may be processed in countries other than yours, including ones with different data protection laws.

We may update this policy by posting a revised version with a new date.