Hawk ScanBeta terms

Early beta · Effective 22 July 2026

Privacy, without pretending the beta is finished.

This notice describes the current repository and beta service. It is not a claim that Hawk Scan has completed every jurisdiction-specific privacy requirement.

Operator status

Hawk Scan is an independent project. A legal operator name, registered address, and dedicated privacy contact have not yet been published. General public or commercial launch is blocked until those details and the applicable legal review are complete.

Project updates may appear at @hawkscanxyz. That account is not yet a formal privacy-rights channel or guaranteed support desk.

What is processed

  • Queries you submit, including wallet addresses, transaction hashes, token names, contract addresses, and natural-language questions.
  • Public blockchain and contract data retrieved to answer a query. Public onchain data can be permanent and cannot be erased by Hawk Scan.
  • Basic request and security metadata that hosting, CDN, network, and upstream providers may log, such as IP address, user agent, time, endpoint, latency, and error status.

Where data goes

A query may be sent to configured chain RPC, explorer/indexer, official stock-token data, hosting, storage, and monitoring providers. When the AI analyst is configured, query text and selected read-tool results may also be processed by the configured inference provider, currently routed through Surplus Intelligence in the Burner Lab, to produce a structured answer.

Provider identities, regions, contracts, subprocessors, transfer mechanisms, and retention terms must be finalized and published before a general public or commercial launch.

Cookies and tracking

The current beta interface does not intentionally use advertising cookies, behavioral advertising, or client-side analytics storage. Infrastructure providers may still use operational logs or essential delivery mechanisms under their own terms. This notice must be updated before analytics, accounts, marketing pixels, or non-essential cookies are introduced.

Retention

The current application code does not create a durable database of public-interface query text. Operational rate-limit and audit records may be retained by the configured platform store, while hosting and upstream providers may keep their own logs. A verified retention and deletion schedule is not yet published and remains a launch blocker.

Your choices

  • Do not submit personal, confidential, or sensitive information.
  • Never submit seed phrases, private keys, passwords, session cookies, access tokens, identity documents, or non-public wallet ownership.
  • Use public addresses and hashes only when you accept that blockchain activity can be linked and analyzed by third parties.
  • Do not use the beta if you require a completed rights-request, deletion, objection, portability, or appeal process today.

Before public launch

The operator must publish its identity and contact details, determine applicable legal bases, document retention, enable rights requests, complete processor and international-transfer terms, define children's use, and obtain jurisdiction-specific legal review. Until then this is an engineering beta notice, not a completed production privacy policy.