Privacy and website data

This is a factual summary of data handling observed in the current website and server routes. It is not an owner-approved comprehensive legal privacy policy and makes no promise about jurisdiction, retention or deletion.

What this summary covers

This page covers the website behavior visible in the current code: browser preferences, public wallet queries, optional sign-in sessions and limited interaction analytics. Third-party destinations have their own practices and terms.

Browser storage

The website can store interface choices locally, including language, light or dark theme and odds format. It can also store dismissed interface prompts and local reaction state. A temporary session-storage identifier is created when tracked product interactions occur.

Public wallet lookups

When you search a public wallet address or open a wallet profile, that address is included in requests used to retrieve public market, trade, balance or transfer data. Those requests can rely on WagerUp server routes and third-party public blockchain or market-data services. A wallet address is a public identifier and can be linked to public activity.

Optional sign-in sessions

Where sign-in is enabled, verified EVM, Solana or Telegram identity data can be associated with an account. The server uses an HTTP-only session cookie after successful sign-in. Signing a sign-in challenge is not a blockchain transaction. Private admin analytics uses a separate HTTP-only session cookie.

Limited product analytics

The website records page views for valid wallet-profile addresses. Pick and bot clicks can send the market or workflow context with a browser-session identifier. The analytics route also records the request user agent and referrer. The current website does not provide a consent manager or self-service data request form, so this summary does not claim that it does.