
Blip is on it
Blip is on it
Blip is on it
Blip is on itPrivacy
Last updated: May 2026. This page describes what data S3ND handles when you use s3nd.fun. We try to keep it honest and short.
The current build is a frontend prototype. Token launches, holdings, balances, and trade history are stored in localStorage on your device. Nothing is sent to a S3ND server until the on-chain launch ships.
When you clear your site data or switch browsers, that state is gone. We can’t recover it for you because we never had it.
If you connect a Solana wallet (Phantom, Solflare, Backpack, etc.) we read your public key so we can show your holdings and route transactions. We never request, see, or store private keys or seed phrases — that data stays inside the wallet extension.
On-chain interactions happen between your wallet and the Solana network. S3ND signs nothing on your behalf.
The site is hosted on Vercel. Standard infrastructure logs (IP address, user agent, request path) may be retained briefly for abuse prevention and operational monitoring. We don’t enrich those logs with profiles, fingerprints, or third-party identifiers.
To show USD prices we proxy a server-side request to the Jupiter Price API (with CoinGeckoas fallback). Your browser never talks to those services directly through us, and we don’t forward anything that identifies you.
We don’t set tracking cookies. The wallet adapter and theme toggle use first-party storage (localStorage / sessionStorage) so the site remembers your preferences across reloads.
When the on-chain layer ships, transactions will pass through Solana RPC providers, the Meteora DBC pool program, and the Token-2022 transfer hook. Their behaviour is governed by the respective programs and infrastructure, not by us. Choose RPC providers you trust.
Because we don’t collect personal data, there is little to request, correct, or delete. If you believe we hold information about you and want it removed, write to us at the contact below and we’ll respond promptly.
Questions, concerns, or corrections? Reach the team via the About page or open an issue on the project repository.
If the way we handle data changes, we’ll update this page and bump the “last updated” date. Material changes will be called out in the changelog.
Companion document: Disclaimer.