Privacy Policy

Data we process

To provide account and trading features, SignalHub processes wallet addresses and related records. Its database can store trade records (market, side, size, price, order ID, status, note, fees, and time), points events, deposit addresses and deposit/forwarding records, invite redemptions and referral relationships, watched trader addresses, and user-created aliases.

After wallet connection, the session cookie contains the wallet address and an expiration time. The signed session token is not backed by a separate database session record. Public blockchain or Hyperliquid data can also contain wallet addresses and public position information.

Trade records

Orders filled through SignalHub are recorded with the wallet address, order ID, market, size, traded value, and fees to calculate points, rankings, and statistics.

Cookies and browser storage

The sh_session cookie lasts 30 days and is HttpOnly, SameSite=Lax, and Secure in production; it contains a signed wallet address and expiration time. The locale cookie stores the interface language and lasts one year.

Browser local storage may contain a locally generated Hyperliquid trading-agent private key, authorization state, referral code, risk acknowledgment, and withdrawal status or destination. Session storage may contain an unsubmitted order draft. This data stays in your browser on your device. The browser also caches your most recent portfolio snapshot and market list to speed up loading, for up to 24 hours. Protect your device and browser profile, and clear local data after using a shared device.

Login and identity

SignalHub uses Privy for email, Google, wallet, and Twitter login options. Privy handles login and authentication information under its own privacy policy; SignalHub's application code does not write email or social-account profile data to its own application database.

Regional information and network requests

The service reads Cloudflare's cf-ipcountry request header to apply regional restrictions; /api/geo also returns that country code. To measure visits and conversion, SignalHub records in its own database an anonymous browser ID, country code, device type, language, referring site or campaign parameters, and events such as page views and order actions; after you connect a wallet these records are linked to the wallet address. SignalHub does not store IP addresses and keeps raw events for 180 days. Cloudflare or hosting providers may process ordinary request and network logs under their own policies.

When you request account information, your browser queries Hyperliquid for the wallet's public account, position, and trade data. Deposit features may involve Circle; authentication is provided by Privy.

News processing and first-party analytics

For news selection, SignalHub sends xAI public candidate sources, publication times, titles, and summaries, along with a list of tradable assets. For news translation it sends public article titles and bodies; for Polymarket translation it sends public market questions or event text. The current application code does not send wallet, account, position, trade, or deposit data to xAI.

The service also depends on Hyperliquid, Circle, Privy, Polymarket, RSS sources, and xAI. SignalHub uses only the first-party analytics described above and does not integrate third-party web-analytics or advertising-tracking SDKs.