Privacy Policy
This Privacy Policy explains what information the SLICE Interface at getslice.fun collects, why, and what you can do about it. We collect as little as possible: there are no user accounts with passwords, no email lists, no advertising trackers and no analytics cookies.
Much of the data the Interface works with — wallet addresses, transactions, token metadata — is public on the Solana blockchain or on IPFS by its nature. We cannot change or delete data that lives on a public blockchain.
Contents
01Information we collect
When you sign in with X or GitHub — your account ID, username, display name, profile image, and (for X) verification status. We use the sign-in only to confirm who you are. We do not store your access tokens, cannot post on your behalf and never see your password.
About named recipients who have not signed in — when a token names an X or GitHub account, we look up that account's public profile (ID, username, name, avatar, banner, verification) through the X or GitHub API so balances can be tied to the right account.
Wallet and on-chain data — wallet addresses you connect or withdraw to, addresses that deploy or register tokens, signed messages used to authorise withdrawals, automatic payouts or splits, and the transactions and balances recorded in our ledger.
Token content — the name, ticker, image, description and links you submit when launching. Images and metadata are pinned to IPFS and are public and permanent.
Technical data — IP address, browser user agent and request details, used for security, abuse prevention and rate limiting. Rate-limit counters are kept in memory for minutes; server logs are kept for a short period and then deleted.
Referral data — if you arrive through a referral link, the referrer's X handle is stored in a cookie and, if you launch a token, saved with that token.
02How we use it
- to operate the Interface: launch and register tokens, split fees, show balances and pay withdrawals;
- to make sure balances go to the right account owner and to prevent fraud, double spending and account takeovers;
- to show public pages such as token pages, recipient profiles, feeds, leaderboards and share cards;
- to run the referral program, endorsements, automatic payouts and featured posts on our X account;
- to secure, debug and improve the Interface, and to comply with legal obligations.
03Legal bases
Where data protection laws such as the GDPR apply, we process data because it is necessary to provide the service you request (performance of a contract), for our legitimate interests in operating a secure and transparent fee-splitting service and in crediting fees to the correct recipients, and to comply with legal obligations. Where consent is required, we ask for it and you may withdraw it at any time.
04What is public
Token pages, recipient profiles (name, handle, avatar, tokens, amounts earned and withdrawn), withdrawal feeds, endorsements and on-chain transaction signatures are public by design — transparency about where fees go is the point of SLICE. Recipients who do not want to appear can opt out at any time.
05Sharing with third parties
We do not sell personal data or share it for advertising. We use service providers that process data on our behalf or independently:
- hosting and infrastructure providers (servers, databases);
- Solana RPC providers, which receive wallet addresses and transactions to read and submit them;
- X and GitHub, for sign-in and public profile lookups;
- IPFS pinning services, for token images and metadata;
- market-data and swap services such as pump.fun, Jupiter, GeckoTerminal and DexScreener, which receive token addresses (not your personal data);
- your wallet provider, which you choose and which has its own privacy policy.
We may disclose information if required by law or to protect the Interface and its users from fraud or abuse.
06International transfers
Our service providers may process data in countries other than yours. Where required, transfers are protected by appropriate safeguards such as standard contractual clauses. Public blockchain data is replicated worldwide by the network itself.
07Retention
- ledger entries, withdrawals and related records — kept as long as needed to pay balances, keep accurate accounts and meet legal obligations;
- cached public profiles — refreshed regularly and removed when no longer linked to any token;
- sign-in sessions — up to 14 days; sign-in state cookies — 10 minutes;
- server logs — a short period for security, then deleted; rate-limit counters — minutes;
- on-chain and IPFS data — permanent and outside our control.
08Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict its processing, and to withdraw consent. You can also stop payments to your account and be hidden from the Interface through the Claim page.
Some data cannot be deleted: anything on a public blockchain or IPFS, and ledger records we must keep to account for funds. To exercise your rights, message @getslicedotfun on X from the account concerned. You also have the right to lodge a complaint with your local data protection authority.
09Security
We use encrypted connections, signed and HTTP-only session cookies, separated hot and treasury wallets, rate limiting and access controls. No system is perfectly secure; keep your wallet and accounts safe and never share your seed phrase — we will never ask for it.
10Children
The Interface is not intended for anyone under 18, and we do not knowingly collect data from minors.
11Cookies
We only use a few first-party cookies needed to run the Interface. See the Cookie Policy for the full list.
12Changes and contact
We may update this policy; the “Last updated” date shows the current version. Questions or requests: message @getslicedotfun on X.