Privacy Policy

Who is responsible

This policy explains how Claim Fund, maintained by Mike, handles information when you use claim.fund and its API. For privacy questions or requests, contact mike@dangervalley.com. Do not send a seed phrase, private key or signed transaction with a privacy request.

This policy should be read alongside our Terms of Use. Public blockchain information is not necessarily anonymous: a wallet address may identify a person when combined with other information.

Information we process

• Public blockchain data: wallet and token addresses, fee entitlements, asset amounts, configured recipients and public transaction records used to build and refresh the fee index.
• Wallet lookups and connections: addresses you enter, the public address exposed by a connected wallet and token addresses you ask us to check.
• Claims: transaction contents, your public wallet signature, claim amounts and authorization data needed to prepare, simulate, verify and submit an approved transaction. A signed transaction is different from your private key.
• Claim cards: when the post-claim dialog or a receipt share action opens, we use the public transaction signatures to generate an image of your executed claim amounts before the service fee. The image and its link are public and may be copied or cached by anyone who receives the link. We do not post to social media automatically.
• Technical requests: IP addresses, requested URLs, request timing and ordinary connection or device information processed by our infrastructure to deliver and protect the Service. An address included in a request URL may also be visible to infrastructure providers.
• Messages: information you choose to include when contacting us.

We do not ask for or need your private keys or seed phrase. Browsing the site and checking public addresses does not require creating a Claim Fund account.

Why we use it

We process information to display fee estimates, answer wallet lookups, check live balances, prepare and submit claims you approve, maintain local activity, prevent abuse, troubleshoot problems and respond to requests.

Where data protection law requires a legal basis, processing necessary to provide the Service you request relies on performance of a contract or steps you request before it. Our legitimate interests in maintaining a useful public fee index and securing and operating the Service support other necessary processing, subject to your rights. We rely on legal obligations or consent where applicable.

We do not sell your personal information. Optional product and traffic analytics are described below.

Optional analytics

When configured and you allow analytics, Google Analytics 4 and PostHog Cloud measure page visits, referral sources, campaign tags and actions such as wallet searches, connections, claim attempts and confirmations. We use a browser identifier to understand the steps in a visit. We do not send entered wallet addresses, transaction signatures, search text, RPC error details or searched-wallet balances as analytics event properties. Session recording and automatic click/form capture are disabled in the application.

Analytics scripts load after you choose Allow analytics. Declining does not prevent searches or claims. You can change your choice through Analytics settings in the footer; this stops future browser events. A consented claim event already queued on our server may still be delivered. Changing your choice does not automatically delete events already received by providers. Their retention and processing settings also apply.

Our separate server claim register records successful transactions submitted through Claim Fund, including public wallet addresses, signatures, asset amounts and service fees. This operational record does not depend on optional analytics consent. It supports reconciliation and aggregate figures such as total claimed and the number of unique claiming wallets.

Browser storage and cookies

The application uses first-party browser storage for these functions:

• Claim activity: claim-fund-receipts in localStorage keeps up to 50 recent records, including the wallet address, signature, status, time and claim label. These records remain in that browser until removed or replaced by newer entries. Clearing them does not remove blockchain records.
• Analytics choice: claim-fund:analytics-consent:v1 in localStorage remembers Allow or Decline. When allowed and configured, Google Analytics uses its _ga cookies and PostHog uses browser storage for visitor/session identifiers. These are separate from the local claim activity list.
• Wallet preferences: your wallet software or its connection library may maintain its own connection settings under its own controls and policy.

You can inspect, block or clear cookies and local storage through your browser. Clearing site data resets local history and preferences. Some convenience features may stop working when storage is blocked. Following the creator is optional.

Providers and public transactions

Vercel hosts the website, and DigitalOcean hosts our API and public fee index. RPC infrastructure, including the configured Helius provider and PublicNode connections, processes blockchain requests. Our API can forward wallet addresses and transaction data to RPC providers for the checks, simulations and submissions you request. Your browser may also connect directly to blockchain or wallet infrastructure.

If you allow configured analytics, Google and PostHog receive analytics requests and ordinary connection information. See Google’s privacy policy and PostHog’s privacy policy.

Wallet providers, token-image and metadata hosts, and external sites you open receive requests according to their own policies. X links are ordinary external links; we do not embed an X social widget. We serve the creator portrait and application fonts locally.

When a signed transaction is submitted, it is shared with network infrastructure and may become a public, persistent Solana record. Anyone can inspect public blockchain records. We cannot delete or edit those records.

We may disclose information when required by applicable law or when necessary to investigate abuse, protect the Service or establish or defend legal claims. Infrastructure providers may process information in countries outside your own, under their applicable contracts and transfer arrangements.

Retention and security

The public fee index is stored on our server and refreshed as blockchain data changes. We retain index records and recent verified snapshots to provide lookups and operate the Service. It is not a record of which addresses each visitor searched.

To update indexed balances after a claim, our server retains the public transaction signature, affected account addresses, reconciliation status and verified source balances. Pending updates can resume after a restart. Recent activity in your browser may be sent to our API to reconcile an earlier claim.

The server claim register persists independently of daily index snapshots. Each signature is counted once after finality, with separate amounts per token. We retain this record for service operation, aggregate reporting and reconciliation. Where analytics is allowed, a random browser/session identifier can also be retained with that submission to deliver a confirmation event; wallet addresses and signatures are not sent with that event.

Generated claim cards and their public amount metadata are cached on our server for link sharing. Cards contain payout amounts and our domain, not the wallet address. Blockchain transactions remain public independently of these cards.

The application’s IP-based rate-limit counters are held in memory for short request windows and periodically cleaned up. Claim authorizations expire after 90 seconds. That expiry is not a deletion deadline for browser history, blockchain records or infrastructure logs.

Hosting and RPC providers may retain operational or security logs according to their settings and policies. Retention depends on the purpose, security and troubleshooting needs and applicable legal obligations. Contact us about a specific request rather than assuming a single retention period applies to every provider.

We use measures such as HTTPS, request limits and transaction-authorization checks. No system is completely secure. Keep your wallet software and device secure and review transactions before signing.

Your choices and rights

You can use public lookup without connecting a wallet, disconnect your wallet, clear browser storage, decline the optional follow invitation and choose whether to approve a transaction.

Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal information, object to processing based on legitimate interests, or withdraw consent where it is the basis for processing. You may also complain to the relevant data protection authority. We may need proportionate information to verify a request; we will not ask for your seed phrase or private key.

These rights do not give us control over the Solana blockchain or third-party records. Tell us which off-chain information or processing your request concerns so we can assess what we can address.

Policy updates

We may update this policy as the Service or its processing changes. The date at the top identifies the latest version. Where applicable law requires additional notice or consent, we will provide it.