Privacy Notice

Information handled

• Public market and trader information. Contracts, networks, prices, public profiles, avatars, handles, wallet activity, holdings, and performance are obtained from third-party services and public blockchain sources. Wallet activity may be linkable to a person; public does not necessarily mean anonymous.
• Search and lookup requests. Search text, handles, contracts, and selected networks are sent to our backend and relevant providers to return results. Do not put sensitive or private information into search fields.
• Advertising records. When relevant features are used, records can include submitted token details, bids, order IDs, provider references, payment currency and amount, confirmation status, and timestamps. Checkout is disabled; viewing a preview does not create a confirmed payment.
• Placement activity. Views and clicks can be counted using a browser-session identifier. The backend stores a hash of that identifier with the placement, event type, and day to avoid repeated counting. This is pseudonymous measurement, not guaranteed anonymity.
• Technical requests. Hosting and backend infrastructure can process IP addresses, request paths and search queries, browser information, timestamps, errors, and security logs to deliver and protect the site.

Browser storage

The application uses local storage and session storage for functionality. Recent searches are stored on your device, currently limited to ten selections. Other entries can include cached trader and token information, display state, an advertising-metrics session identifier, and checkout-recovery or order-access keys when those features are used.

Local storage can remain until cleared. Session storage normally lasts for a tab session, although browser restoration can retain it. Some cached data has application-level expiration checks. These mechanisms differ from cookies; hosting and external services may use their own cookies or similar technologies.

Placement measurement and site analytics are separate processes, described below. Neither the online count nor a placement metric identifies an individual visitor publicly.

Live presence and site analytics

To display the online count, visible site tabs send a heartbeat every five seconds with a random browser identifier. The identifier is shared between tabs using local storage and replaced after 30 minutes of inactivity when the site is next used. Our presence service keeps identifiers in memory, not a database, and excludes them from the count after 20 seconds without a heartbeat. Expired records are removed on the next heartbeat. The public response contains only the count and timestamp, not identifiers. Counts measure active browser sessions, not verified people. When storage is blocked, separate tabs may count separately.

DataFast separately collects site-usage analytics and supplies the all-time visitor total. Its script runs on our pages and its processing can lag behind the live presence count. The installed DataFast script uses cookies and processes IP addresses and usage information for analytics. See DataFast’s Privacy Policy. Infrastructure providers also process ordinary connection and device information. The presence identifier is not sent to DataFast or linked to advertising orders by our application.

Why information is used

Information supports feeds, token and trader lookup, recent selections, checkout recovery, payment verification if enabled, paid placements, placement measurement, live visitor counts, diagnostics, abuse prevention, and applicable legal obligations. Advertising placement is based on confirmed spend, not personalized behavioral targeting.

External services

Vercel hosts the public site. Backend infrastructure relays requests to external market-data services, trading platforms and blockchain sources. External image and CDN hosts receive normal connection information, including your IP address, when your browser loads their images.

Payments are not enabled. Before checkout launches, this notice will identify the payment and authentication providers and explain what information they receive. Transactions and addresses on public blockchains remain visible independently of this site. Trading and social links lead to services with separate data practices.

Providers may process data outside your country. Information may be disclosed where legally required or reasonably necessary to investigate abuse or protect the service and its users. See Vercel’s Privacy Notice for hosting-related practices.

Retention and security

Advertising orders, payment records, and event records remain in the service database until removed; automatic deletion is not currently configured. Infrastructure providers apply their own log-retention settings. We do not control independent providers’ records or public blockchain history.

Access controls and server-side credential handling help protect service data, but no system or transmission is guaranteed secure. Do not share recovery keys or wallet secrets. Clearing an order-access key may prevent recovering that order through the same browser.

Your choices and privacy rights

Use “Clear all” in search to remove recent selections, or clear this site’s data through browser settings. Clearing local data removes preferences and saved recovery keys; it does not automatically delete backend records, provider records, or blockchain transactions. Blocking storage may limit features. Visiting external links is optional.

Depending on your location and applicable law, rights may include access, correction, deletion, objection, and a complaint to a privacy authority. Scope depends on the information and context. A project privacy-request channel has not yet been published; clearing browser data is not presented as a way to exercise rights over server-held records.

Audience and updates

The site is intended for adults researching cryptoassets, not children. This notice will be updated when practices change, particularly before payment processing or new tracking features are enabled. The date above identifies this version.