Privacy policy

You do not sign in, create an account, or connect a wallet to use Evidesa. We do not ask for your name, email, or any wallet signature to generate a report.

• Mint addresses you submit. A token mint address is used to fetch on-chain and market data and to build the report. It appears in the report URL, so it may be recorded in standard server and infrastructure logs. A mint address is a public on-chain identifier, not your personal identity.
• Server and infrastructure logs. Our hosting provider may automatically record technical request data such as IP address, user agent, timestamps, and requested paths. Evidesa uses a coarse, in-memory rate-limit signal derived from forwarded IP headers to protect the service; this is not stored durably or used to profile you.
• Privacy-conscious analytics (when enabled). If analytics is configured, Evidesa records a small set of aggregate product events (for example, a scan was submitted or a report opened) using a cookieless, privacy-focused provider. Event data is minimized by design — it does not include full mint addresses, wallet identity, report contents, secrets, or your full IP address added by the application.
• Feedback you choose to send. If you answer the optional “Was this useful?” prompt, we process your yes/no response and any short comment you write. Do not include personal or sensitive information in the comment. Feedback is not linked to a wallet or account.

• No accounts, passwords, or wallet signatures.
• No advertising trackers, fingerprinting, session replay, or keystroke capture.
• No non-essential cookies. Privacy-conscious analytics, when enabled, is cookieless.
• No selling or renting of data.

We cannot truthfully claim that no data at all is collected, because hosting and network providers may keep their own technical logs to operate and secure the service.

To generate a report, Evidesa sends the necessary requests to third parties, who process them under their own policies:

• The cloud hosting provider that runs the application and may log requests.
• A Solana RPC provider, to read on-chain mint, holder, and transaction data.
• DexScreener, for third-party market and liquidity data.
• IPFS and Arweave gateways, when a token's metadata URI must be fetched.
• A cookieless analytics provider, only if analytics is configured.

When your browser loads a token logo image, that request goes directly from your browser to the image host and may reveal your IP address and user agent to that host.

Evidesa does not maintain a user database in the beta. Reports are generated on demand and are not tied to your identity. Provider logs and any aggregate analytics are retained according to those providers’ policies. Local price snapshots, when enabled, contain token prices only — no personal data.

Evidesa relies on cloud and data providers that may process requests in countries other than yours. Using the service may involve transferring technical request data across borders.

Because we do not hold accounts or identify you, most requests reduce to general technical-log handling by our providers. Depending on where you live, you may have rights to access, correct, or delete personal data. To ask a question or make a request, contact us via the contact page.