ØData handling
Privacy policy
What passes through sØl, what stays in your browser, and what becomes public on Solana.
Last updated · August 2, 2026
- 01.
What does this policy cover?
This policy describes how sØl processes information when you use s0l.app to scan Solana addresses, close token accounts and reclaim their rent, or send tokens to multiple recipients.
- 02.
Do I need an account or profile?
No. sØl does not require an account, login, name, email address, or other profile information to use its tools.
- 03.
What happens when I scan a wallet?
The browser sends the public wallet address to an sØl API route. The sØl server validates it and sends the relevant public-address queries to Helius RPC, which reads Solana data. The scan result then returns through the sØl server to your browser. The address therefore transits both sØl's server and Helius; it is not fetched directly from the blockchain by your browser.
- 04.
Are scan results stored on the server?
Incinerator scan responses, including the queried wallet address and returned token-account data, may be stored in the application's server-side data cache to speed repeat requests. The cache revalidates after 20 seconds, but an entry may remain until it is refreshed or evicted. Hosting logs and upstream providers may retain request data separately under their own practices.
- 05.
What stays in my browser when I use the bulk sender?
Recipient lists and uploaded CSV contents are parsed and held in browser state. The browser uses the configured Solana RPC connection to read balances and account state, builds transactions locally, and asks your wallet to sign them. sØl does not intentionally send or store the recipient list through an application API.
- 06.
What analytics may be collected?
When a Google Analytics ID is configured, Google Analytics 4 may collect page views, feature interactions, device and browser information, approximate location, cookies, and similar online identifiers. We use that information to understand aggregate traffic and improve the tools, not to build sØl user profiles.
- 07.
What can appear in server logs?
Vercel and other hosting infrastructure may create standard request and security logs containing information such as IP address, timestamp, browser details, requested path, and query string. Because scan addresses are sent in query strings, a queried public wallet address may appear in those logs. Hosting providers control their own retention and access practices.
- 08.
How does rate limiting use IP addresses?
The application keeps an IP-based request counter in server memory for a one-minute window to limit abuse. That in-memory rate-limit map is not intentionally written to disk or joined to wallet addresses, and it disappears when the server instance restarts.
- 09.
What operational transaction data is sent to Telegram?
After a paid transaction confirms, sØl may send a private operational alert containing the tool name, summary details, and transaction signature. The message does not include a separate wallet-address field, but the public signature can be used to identify the payer and transaction participants on Solana. Telegram processes the alert under its own terms.
- 10.
What information does sØl not ask for?
sØl does not ask for private keys, seed phrases, passwords, legal names, email addresses, government identifiers, or account registration. Your wallet provider handles signing; sØl cannot sign a transaction for you.
- 11.
How is processed information used?
Information is used to deliver scan and transaction-building features, operate and secure the service, enforce rate limits, diagnose failures, monitor paid transactions, understand usage, and improve performance. Public blockchain data is used to show balances, accounts, and transaction results.
- 12.
Is information sold or shared for marketing?
sØl does not sell or rent information and does not intentionally share it with third parties for their own marketing. Information is disclosed to infrastructure and service providers only as described in this policy or when required by law.
- 13.
Which service providers receive data?
Helius receives wallet-address and account queries used to read Solana. Vercel hosts the application and may process request logs and cached responses. Google may process analytics data when analytics is configured. Telegram may process operational transaction alerts. Wallet providers and Solana RPC infrastructure process requests initiated through your connected wallet.
- 14.
How are cookies and Do Not Track handled?
Google Analytics may set cookies when it is enabled. You can block or clear them with browser settings or privacy extensions, although blocking storage can affect some site behavior. sØl does not currently respond to Do Not Track browser signals.
- 15.
What is permanently public on Solana?
Submitted blockchain transactions and their participants are public and permanently recorded on Solana. sØl cannot alter or erase confirmed on-chain data. Links to explorers and other external sites are governed by those sites' privacy practices.
- 16.
How long is information retained?
The in-memory rate-limit window lasts one minute. The incinerator data cache revalidates after 20 seconds but may keep stale entries until refresh or eviction. sØl does not maintain a separate user-account or wallet-history database. Vercel, Helius, Google, Telegram, wallet providers, and Solana retain information under their own policies; confirmed Solana data is permanent.
- 17.
Where can processing occur?
sØl and its providers may process information in the United States and other countries where their infrastructure operates. Those locations may have privacy laws different from the laws where you live.
- 18.
How is the service secured?
The production site uses HTTPS and response headers intended to reduce common browser attacks. Wallet signing remains inside your wallet provider. No internet service can promise absolute security, and public wallet addresses, signatures, and blockchain activity should not be treated as confidential.
- 19.
What privacy rights may apply?
Depending on your location, you may have rights to know about, access, correct, delete, restrict, port, or object to processing of personal information, and rights concerning sale or discrimination. These rights can be limited where data is public, belongs to a provider, is required for security, or is permanently recorded on Solana.
- 20.
Is the service intended for children?
No. The services are not directed to anyone under 18, and sØl does not knowingly ask children for personal information. If a dedicated privacy contact channel is published, reports about child data can be made through that channel.
- 21.
What about third-party links?
The site links to blockchain explorers, wallet providers, token sites, protocols, and other external services. sØl does not control their data practices. Review a third party's policy before providing information to it.
- 22.
Can this policy change?
Yes. Material changes will be signaled by changing the Last updated date on this page. Continued use after a change is governed by the updated policy.
- 23.
How can I make a privacy request?
sØl does not currently publish a dedicated email address or request form. We will update this policy when a working privacy contact channel exists. Until then, browser controls can limit analytics, but they cannot erase confirmed Solana transactions or data held independently by third-party providers.
Third-party policies: Helius · Vercel · Google · see also our Terms of Service.