Privacy Policy

Daily market editions store public coin identifiers, market observations, source times, scores, and explanations in the shared site database. They are not user portfolios. Editions are retained as the public archive while the archive service operates. Research browsing does not require a wallet address.

Coin search and strength/coverage filters operate in your browser on the selected edition and are not saved as a personal research profile by the application. Date selection is sent to the server and may appear in hosting request logs. Market data requests are made server-side to CoinGecko or CoinPaprika; the daily updater does not send a visitor’s wallet or email to either provider. If you follow a source link, that provider receives your visit under its own policy.

If you email a correction, we receive your email address, message, and any information you include to respond and investigate. Do not include wallet secrets. Correspondence is retained as needed to handle the issue and related operational records; contact us to request deletion where applicable. Public archive data contains no subscription contacts.

When you use the scanner, you may enter a public contract address, a public wallet address, a token address or mint, a network, or a token search term. If you connect a compatible browser wallet, the site receives its public address for a read-only check. We do not ask for a seed phrase or private key, and the site does not request a transaction signature.

Wallet addresses and blockchain activity are public and can sometimes be linked to a person. Avoid entering an address you do not want associated with your use of this service.

We use the information you enter to show contract details, look for claim-style functions, call read-only blockchain methods, search Solana tokens, and display wallet and token balances. Public contract discoveries, scores, and scan history are saved in a shared site database so visitors can see recent results. The application does not add wallet balance checks or your saved-contract list to that database.

ClaimScanHQ has no user account registration or payment checkout. Access is free regardless of whether you support the site.

If you choose to send ETH, SOL, or BTC to a public receiving address shown on the Support page, you initiate that transfer in your own wallet. We do not collect card details, seed phrases, or private keys for support. The site does not match contributions to a user account or use them to change your access or results.

Blockchain transfers are public. The sending address, receiving address, amount, and transaction details may be visible to others through blockchain explorers, even if you do not share your name with us.

Your saved-contract list and light/dark setting are stored in your browser’s local storage. They stay on that device unless you remove them or clear the browser’s site data. You can export your saved list as a CSV file. ClaimScanHQ does not sync this browser list to an account.

To answer searches, checks, and market chart requests, requests may go to public data providers such as Blockscout, Sourcify, DexScreener, GeckoTerminal, PublicNode, and Solana RPC services. A Solana balance check can also go directly from your browser to Solana’s public RPC if the site’s server request is unavailable. Those providers may receive the relevant public address or search and technical request data, and handle it under their own policies.

The site’s hosting and security services may process technical records such as IP address, browser information, request time, and requested URL to deliver and protect the site. A URL for a lookup can contain the public address or search you submitted. Such records are handled by the relevant service providers; ClaimScanHQ does not use them to build an account profile.

If you request alerts, we store your email address or phone number, selected networks, consent time, verification status, and message status. These details are used to verify your contact and deliver future High-confidence discovery signals. They are not tied to a wallet address or used for advertising. Email delivery uses Resend; text delivery uses Twilio and mobile carriers when those channels are enabled.

You must verify the contact before alerts begin. Verification codes expire in ten minutes. Messages include an unsubscribe link; text recipients may also reply STOP. Unsubscribing through the site removes the contact information from that subscription. Providers may retain their own delivery records under their policies. Active contact details remain while you subscribe; expired pending contacts are removed on subsequent registration requests. Alert timing depends on discovery scans and provider availability.

Google AdSense code is limited to selected explanatory content pages, currently How ClaimScanHQ Works. The scanner, daily feed, archives, and subscription/verification screens do not load that advertising code. Ads can appear after Google approves the site and the operator enables them in AdSense. Google and other third-party advertising vendors may place or read cookies, use web beacons or IP addresses, and process visits to this or other sites to serve and measure ads, including personalized ads where allowed.

Google’s advertising cookies enable Google and its partners to show ads based on your visits here and elsewhere. You can opt out of personalized ads in Google Ads Settings and opt out of some other vendors through AdChoices. See Google’s advertising privacy information and its ad technology partners for more detail.

If an advertising consent message appears, you can use it to manage its choices. Your saved-contract list and light/dark setting are stored in your browser for those site features, not for ad targeting by ClaimScanHQ.

You can use a manually entered public wallet address instead of connecting a wallet, remove saved contracts, clear this site’s browser data, or stop using a lookup. Blockchain information already public on a network is outside ClaimScanHQ’s control.

We may revise this policy as the site changes. The updated date on this page will show when its description was last revised.