The practical boundary: what stays in your browser, what reaches analytics, and what a public-data lookup must transmit.
Public pages can be read without entering personal information. HypeBasis uses privacy-bounded analytics to learn whether its tools are useful, and it stores a random identifier plus session markers in this browser. Sensitive research inputs are excluded from custom analytics events. You can disable analytics for this browser below.
This setting controls HypeBasis custom events and the configured Umami tracker in this browser. It does not clear watchlists, alert rules, or other local tool preferences.
Checking browser
The choice is stored only in this browser and can be changed here at any time.
HypeBasis uses local storage for a random analytics identifier, first-seen date, daily visit marker, short browser-session marker, and bounded activation state. The random identifier links product events from the same browser so return behavior can be compared; it is not a name, email address, or wallet address. Some tools also store watchlists, alert rules, or preferences locally. Clearing this site's browser data removes those local values.
As reviewed on August 25, 2026, production loads Umami Cloud. Default page analytics can include the page path and title, referrer URL, browser language, screen size, browser, operating system, device type, and approximate location. HypeBasis removes query strings and hashes before the payload is sent. Umami says an IP address can be used to derive location and session metrics but is not stored. Custom acquisition events classify known search, social, and AI sources instead of sending arbitrary campaign or search text.
HypeBasis custom events exclude query strings, URL hashes, wallet addresses, transaction hashes, explorer lookup values, calculator inputs, and account values. Dynamic explorer and vault paths are redacted before event payloads are sent. Umami analytics does not use cookies, and no session-replay feature is enabled by this site.
A public address, transaction hash, or token entered into a read-only tool must be transmitted to HypeBasis and the relevant public-data provider so the request can be answered. These identifiers are public-chain data, but they can still reveal research interests. Do not enter a value you do not want transmitted to those services.
This page describes implemented HypeBasis data behavior and visitor controls. It is not legal advice and does not replace rights or obligations that may apply in the reader's jurisdiction.