Privacy policy
Effective date: January 8, 2026
This Policy explains how Hypothesis (“Hypothesis”, “we”) handles information when you use the Service.
1) Information we collect
A. Account data (if you register or connect a wallet)
If you use account features, we may collect:
- Email (optional; when used for account recovery)
- Username and optional display name / bio / avatar / cover
- Wallet address when you authenticate with Sign-In with Ethereum (SIWE)
- Session cookie (
qt_session) and related auth identifiers - Password (hashed; never stored in plain text) when password login is used
- Language preference: browser cookie
db_localefor guests, and an accountpreferredLocalewhen signed in
B. Browser personal layer
Portfolio, watchlist, levels, and “since your last visit” cursors are stored mainly in your browser’s localStorage. That content is not cloud-synced by default and is not sent to Hypothesis servers except via explicit APIs that only receive asset IDs / public event cursors (no portfolio amounts).
C. Community and public profile content
If you publish content, we may store posts, comments, theses, and related metadata. A publicly claimed wallet profile (name, avatar, cover, bio, public posts) remains visible at the wallet URL and social routes even if you later disconnect the wallet from a browser session. Private fields (email, drafts, DMs, owner-only capital tools) are not inferred from a searched address alone.
D. On-chain and market data
Public blockchain balances and protocol positions for an address may be fetched from indexed providers (for example Alchemy Portfolio) and shown on public wallet views. This is public-chain data, not a private bank statement. Hypothesis does not custody assets.
E. Basic technical usage
- IP address (server logs)
- User agent / device
- Requested routes or actions and timestamps
2) How we use information
- Operate and improve the Service
- Authenticate sessions (when an account exists)
- Moderate and prevent abuse
- Show market intelligence and public indices
- Transactional communications (e.g. password reset)
3) Storage and security
We apply reasonable technical and organizational measures.
- Database: MongoDB (when the shared store is configured)
- Hosting: Vercel (or another declared operator)
No system is 100% secure.
4) Cookies and sessions
We use cookies mainly for authentication (qt_session) and language preference (db_locale). Disabling them may break sign-in or reset language to English.
5) Third parties
- CoinGecko and other public market-data providers
- DeFi Llama for protocol metrics
- Indexed wallet portfolio providers (e.g. Alchemy) when configured
- Transactional email (e.g. SMTP) when configured
- Hosting (Vercel) and MongoDB when the shared store is configured
- Optional machine-translation providers — only if separately enabled and billed; not invoked on every page view
We do not sell personal data.
6) Your rights
Depending on your jurisdiction, you may request access, correction, or deletion of personal data associated with an account. Contact: support@hypsis.xyz.
Data that lives only in your browser can be cleared by you by clearing the site’s storage.
7) Retention
We retain data as long as needed to operate the Service, for security, and for legal obligations.
8) Updates
We may update this Policy. Material changes will be reflected in the effective date.
Contact
Privacy: support@hypsis.xyz