Unclaimed SOL Privacy Policy
Last updated: 12 September 2026
Privacy contact: [email protected]
1. Scope
This Policy explains how Unclaimed SOL handles personal information in connection with Unclaimed SOL at unclaimedsol.com and our hosted tools, APIs, widgets, and official bot services that link to this Policy. It also covers information we obtain from public blockchain records in operating those services. In this Policy, “we,” “us,” and “our” refer to the operator of Unclaimed SOL, responsible for the processing described here.
It does not govern independent wallets, protocols, linked websites, or a partner's own website. A partner may separately collect information when it embeds our tools. We are responsible for the processing we determine; those providers explain their own processing in their policies.
2. Wallet information can be personal information
Solana addresses and transactions are public, but they are not necessarily anonymous. An address, domain name, transaction history, or combination of those records may identify you, particularly when linked to an email address or messaging account.
We process wallet information when you connect a wallet, enter an address or supported domain, request a scan, submit a transaction, or subscribe to alerts. We may also encounter your address through public program records or an address submitted by someone else. Public availability does not remove privacy rights that apply to our own processing.
We do not require your wallet seed phrase or private key. Please do not include them in support messages. A signed transaction or wallet address is different from a private key.
3. Information we process
| Category | Examples and source |
|---|---|
| Wallet and on-chain data | Addresses and resolved wallet domains; account ownership and authorities; token and NFT holdings and metadata; balances; supported stakes, rewards, and recovery opportunities; transaction signatures, instructions, outcomes, and timestamps. Obtained from your requests, connected wallets, Solana RPC services, public records, and relevant protocols. |
| Service and accounting records | Scan and claim outcomes, recorded recovery amounts, fee-verification results, pending and verified cashback, payout records, claim history, and partner attribution. Generated by your use and by verification against blockchain records. |
| Alert recipients | Email addresses, browser-push endpoints and subscription keys, Telegram identifiers where applicable, watched wallets, thresholds, verification state, management credentials, notification attempts, and unsubscribe state. Provided by you, your device, the messaging service, and our delivery systems. |
| Technical and diagnostic information | IP addresses received when your device connects, IP-derived identifiers in some backend analytics, browser/device details, wallet-provider type, request timing, feature outcomes, and error reports. Hosting and delivery providers also receive technical connection information. |
| Support and business communications | Information you choose to send, including contact details, messages, and transaction references; partner information where applicable. |
| Airdrop and eligibility information | The requested address, relevant allocation or vesting evidence, claim-status observations, and technical lookup results from approved sources. Some sources receive the queried address to answer the request. |
If you download a tax export, we use recorded wallet activity and available historical prices to prepare it. We do not automatically submit the export to Koinly merely because it uses a Koinly-compatible format. Any upload you make to a tax service is a separate disclosure.
4. Why we use information
We use information to provide requested scans and transactions; verify fees and cashback; maintain history; deliver and manage requested alerts; investigate errors and abuse; maintain reliable infrastructure; answer support requests; and satisfy applicable legal obligations or establish and defend legal claims.
Where applicable law requires a legal basis for processing, the basis depends on the purpose:
| Purpose | Basis, where applicable |
|---|---|
| Requested transaction services, history, and cashback administration | Performance of our agreement, to the extent objectively necessary; legitimate interests in accurate accounting and fraud prevention for supporting checks. |
| Public-chain discovery, owner indexes, and supported eligibility checks | Legitimate interests in locating supported opportunities and providing reliable results, subject to assessment of the impact on affected people. |
| Security, limited operational diagnostics, and support | Legitimate interests in protecting and maintaining the Service, or performance of the agreement when necessary to answer a service request. Where consent is legally required for device access or tracking, legitimate interests do not replace that requirement. |
| Optional alerts and consent-based communications | Your request or consent as applicable to the channel and applicable law; necessary verification and anti-abuse records also support secure delivery. |
| Legally required records or disclosures | Compliance with the specific legal obligation that applies to us. |
We do not rely on acceptance of the Terms as blanket consent to every use of information. Where consent is required, it must be specific and may be withdrawn. Where we rely on legitimate interests, you may object as applicable law provides.
Providing a wallet address is necessary for a wallet-specific scan. A recipient address or endpoint is necessary for that alert channel. You may use other available features without subscribing to alerts. Withholding information necessary for a requested feature may prevent us from providing that feature.
5. Public displays and blockchain records
The Service includes public recent-claim and leaderboard features. These may display or make available wallet addresses, associated public names, claim amounts, timestamps, rankings, and transaction references. An abbreviated address in the interface does not make the underlying record anonymous. Public display can make an activity easier to connect to a person than it was on the blockchain alone. You can request exclusion of your wallet from our recent-claim and leaderboard displays by emailing [email protected]. We handle these requests manually and may ask for proportionate verification before excluding the wallet. Exclusion concerns our public displays; it does not erase blockchain records or records we must retain for another lawful purpose.
Transactions you authorise are transmitted to the public Solana network. Validators, explorers, and others may retain and analyse them independently. We cannot change or erase the blockchain's historical record or recall copies held by independent parties. This does not prevent us from considering a request concerning records or displays we control.
Avoid including contact details or other unnecessary personal information in transaction data. An alert sent to a shared inbox, Telegram account, or device may reveal a watched wallet and an estimate of its recoverable value to anyone with access to that channel.
6. Service providers and other recipients
We disclose information needed for a feature to the providers that operate or support it. The current software integrations include:
| Recipient or category | Purpose and information involved |
|---|---|
| Google Firebase / Google Cloud | Database and Functions infrastructure for service records, claim history, public displays, cashback-related records where used, and alert management. |
| Hosting and database providers | Delivery of the website and API, operational logs, and database storage, including public-chain indexes. |
| Solana RPC providers, including Helius | Wallet/account lookups, transaction simulation and submission, and related blockchain reads. Our browser RPC gateway forwards supported requests to upstream infrastructure. |
| Jupiter and supported protocol or eligibility-source providers | Prices, routes, orders, rewards or allocation evidence, and related requests. Relevant addresses and transaction information may be supplied when needed. |
| PostHog | Selected feature outcomes and operational diagnostics. Events can include wallet identifiers, provider type, request or attempt identifiers, durations, and error categories. Some backend events use an IP-derived identifier. These data are not all anonymous. |
| Sentry | Error reports and technical context used to investigate failures. Depending on the error, reports may contain request or wallet-related information. |
| Resend | Delivery and verification of requested email alerts, including recipient address and message content. |
| Browser push services and Telegram | Delivery of requested notifications and associated recipient or device identifiers and message content. |
| Wallets, embedded-site operators, and sites you choose to visit | Information involved in your interaction, under their own practices as well as any applicable processing arrangements with us. |
Third-party images and badges loaded directly from another domain can expose your IP address, browser details, and information permitted by your browser's referrer policy to that host. Our footer currently includes an externally hosted Findly badge. Clicking a sponsored or external link may also send information to the destination.
We may disclose relevant information to professional advisers, authorities when legally required, or parties involved in a genuine business transfer with appropriate confidentiality and legal safeguards. We do not treat a request from an unverified party as sufficient authority to disclose private recipient information.
7. Browser storage and analytics
The Service uses browser storage for requested functionality, including alert management, push registration or repair state, pending cashback submissions, and claim-session state. Wallet software can also store its own connection preferences. Clearing site data may remove local settings or management access; it does not unsubscribe a server-side recipient or erase blockchain activity.
The browser PostHog integration is configured to use memory rather than persistent analytics cookies or local storage. Automatic click capture, automatic pageview capture, session recording, and person profiles are disabled. Selected events are still transmitted when analytics is enabled. These events may still be associated with a wallet or other identifier even though the browser integration does not retain a persistent analytics identifier.
The restricted airdrop administration interface uses an essential secure session cookie with a one-hour lifetime. It is not needed for ordinary wallet scanning.
You can manage site storage and notification permissions through your browser. You can also contact us to object to processing of your personal information, including analytics, where applicable law provides that right. There is currently no in-app analytics opt-out switch, and sending an email does not automatically change collection in your browser. This does not limit your right to object or our obligation to act on a valid objection under applicable law. To stop a subscribed alert, use its unsubscribe or management control; revoking browser permission alone may leave an inactive subscription record on our servers.
8. Retention
Retention depends on the purpose and the type of record. Disconnecting a wallet or unsubscribing does not automatically delete claim, accounting, or security records. Certain verification and notification records may be kept after a transaction or subscription ends to prevent duplicate credits, repeated notifications, or fraudulent requests.
We determine retention by considering whether information is still needed for the feature you requested, an outstanding payment or complaint, fraud prevention, an applicable recordkeeping obligation, or the establishment or defence of a legal claim. The sensitivity of the information and whether the purpose can be met with less information also inform that decision.
| Record | Factors determining retention |
|---|---|
| Request logs, analytics, and error reports | The period needed to investigate failures, measure service reliability, and detect abuse. Records connected to a specific incident may be needed for longer than routine diagnostics. |
| Claim history, fees, cashback, and payouts | Maintaining the requested history, verifying credits and payments, resolving disputes, preventing duplicate processing, and meeting applicable recordkeeping duties. |
| Alert contacts and delivery records | Providing an active subscription and handling delivery issues. After unsubscribe, limited records may remain necessary to honour that choice and prevent duplicate or unauthorised delivery. |
| Public-chain indexes and public displays | Keeping supported discovery and display features accurate and assessing correction, removal, or objection requests. Public availability alone does not justify keeping every off-chain copy indefinitely. |
| Eligibility evidence and scan records | Completing and verifying the relevant lookup, maintaining supported caches, and investigating errors. Retention differs between transient source evidence and operational records. |
| Support correspondence | Resolving the request, maintaining relevant follow-up history, and addressing related disputes or legal obligations. |
| Backups | Recovery and continuity needs. Removal from an active system may precede expiry of a backup containing the same information. |
You can contact us to ask about retention of a particular record or request deletion. We will explain any reason that requires us to keep information despite your request. Disconnecting a wallet does not submit a deletion request.
Public Solana records remain subject to the network's independent retention. Our inability to delete those records is not a basis to retain all off-chain copies indefinitely.
9. Processing locations
Our infrastructure and service providers operate across multiple locations. Information may be processed where those systems and support teams operate. Where applicable law imposes requirements on transferring personal information between locations, those requirements continue to apply. You can contact us for information about the arrangements relevant to your data.
10. Your rights and choices
Depending on applicable law, you may request access, correction, deletion, restriction, or a portable copy of your personal information, and object to certain processing. You may withdraw consent without affecting processing already lawfully carried out. Some requests are subject to legal exceptions, including necessary accounting or legal-claim records. You may complain to a competent privacy regulator.
Send requests to [email protected]. We may ask for proportionate proof that a request relates to you or to a recipient account you control. We will never require your seed phrase or private key. Control of a wallet does not by itself prove control of every email or device subscribed to that wallet. An authorised agent may act where applicable law permits.
We will respond within the period required by the applicable law and explain any lawful refusal or extension. You will not be penalised for exercising a protected privacy right. A public-display removal request is different from a request to remove an immutable blockchain record, and we will assess the records we control separately.
11. Security, children, and changes
We use access restrictions and technical safeguards designed to protect the information we handle. No system can guarantee absolute security. Protect access to your wallet, inbox, device, and alert-management links. Report a suspected security issue through [email protected].
The Service is intended for adults aged 18 or over. If you believe a child has provided personal information through the Service, contact us so we can assess and address it. Public blockchain records may not reveal a person's age.
We may update this Policy as the Service or our practices change. We will state the effective date and give appropriate notice of material changes. If a new use requires consent, publishing an updated Policy does not replace that consent.