Privacy policy

Splits (splits.fun) helps you launch coins across supported chains and claim creator fees. This page explains the data used for launches, wallets, funding, and account sign-in.

What we collect

• Sign-in identity. When you sign in with X, GitHub, Farcaster, Discord or Google, our authentication provider (Privy) gives us your account's permanent numeric id, your username or email address, and, where the provider offers it, your display name and profile picture. That is all we request. We never receive your password.
• Wallet addresses. The embedded wallet created for you at sign-in, and any wallet you connect or link.
• On-chain activity. Coins launched, trades and claims, which are public on their respective blockchains.
• Account and email fee targets. For existing launches that named a fee recipient, we store the handle or email they typed so that the coin's page can show who it pays. Email targets are stored in full but shown to the public only in masked form.
• Coin details and uploads. Names, tickers, descriptions, images, and links are sent to storage and launchpad services to create public token metadata.
• Basic technical logs such as request timestamps and error reports, kept briefly to run the service.

Why we collect it

• To prepare launches, request funding quotes, and show transaction progress.
• To match fees split with an account to the person who owns that account, and let them claim.
• To show who a coin pays and to display your own coins and fees on your profile.
• To keep the service working and secure.

What goes on chain

Wallet addresses, transactions, and token information are public on the chains you use. Account-based fee routing records a hash of the platform and account id, or of the lowercased email. Public blockchain records cannot be deleted. Uploaded token metadata can also remain publicly accessible.

Who we share it with

• Privy handles authentication and embedded wallets under its own privacy policy.
• Neon hosts our database and Vercel hosts the site.
• Relay, launchpads, and RPC providers receive the wallet, quote, metadata, or transaction data needed for the actions you request. Pinata and upload storage services host token images and metadata.
• Identity lookup services (a RapidAPI provider for X, the public GitHub, Farcaster and Discord APIs) receive the handle a launcher typed so we can resolve it to an id.

We do not sell personal data and we do not use it for advertising.

Retention and deletion

Account data is kept while you have an account. Contact us through the link below to request deletion of your account data; we will remove what is in our database within 30 days. On-chain records and hashes cannot be removed by anyone.

Cookies and storage

Authentication uses browser storage to keep you signed in. The launch flow also saves public recovery data locally, including coin details, wallet addresses, allocations, funding quotes, and transaction references. Generated Solana and EVM launch-wallet keys stay in memory and are not saved in browser storage or the recovery record. Your exported key backups are files you control. Clearing local storage removes the recovery data. We do not use this storage for advertising.

Contact

Questions or deletion requests: message Splits on X. Read the docs for launch and wallet guidance.