Privacy & data handling

Public token evidence and private account activity have different boundaries.

Public reports

Submitted token addresses and evidence snapshots are saved as public reports. Share links remain immutable. Qualifying real reports may appear on token pages and in search results. Public reports are retained for historical comparison; submitting a token is not a private research session.

Private access

Wallet sign-in verifies a message signature and creates a 12-hour session. We store session-token hashes, owned watches, Telegram links and subscription records to operate those features. Wallet sign-in requests no transfer approval. Payment recipients and receipt verification are separate from wallet authentication.

Providers and AI

Token and chain evidence requests go to the configured blockchain and market-data providers. AI is currently unavailable: displayed explanations use computed evidence. An enabled future AI provider would receive public signal evidence, not your wallet session or private watchlist. Provider-specific processing disclosures will be updated before activation.

Measurement

We count scan starts, completions, failures, guide visits and guide-to-scanner interactions in daily aggregate totals. We do not attach wallet addresses, token addresses, referrers, identifiers or private activity to those counters. No third-party analytics is used. Do Not Track and Global Privacy Control opt out of browser engagement events. Aggregate counters expire after 90 days.

Support and infrastructure

Support messages are stored privately for operator review for up to 30 days. Do not submit sensitive material. Web-server access logs may contain IP addresses and request paths and are subject to host log rotation; they are not the anonymous product counters. Backups can retain earlier data according to the operator's backup policy. No claim of legal certification is made.