Security & Privacy

Browser-held keys, not zero risk

The agent key is stored in your browser’s localStorage under hypurr_onboard. It can trade and cancel orders but cannot withdraw. Orders are signed in the browser, not by a server-held trading key. A compromised browser, device or website script can still steal or abuse the key and place harmful trades. No withdrawal authority does not prevent trading losses.

Wallet connection and signature approvals require explicit clicks. Setup approvals do not themselves enable Live. Viewing Paper or choosing a workspace does not enable Live; Paper is simulation. Live must be explicitly enabled in Auto-Pilot and still depends on the existing approval and execution checks. The execution engine requires a running browser tab; suspension, closure and network failures can interrupt automation.

Device links are secrets

The one-time device link contains a trade-capable key in its URL fragment. The fragment is not sent in the HTTP request, but anyone who receives the full link may gain trading access. Share it only through a trusted private channel, never publicly or in a group.

Never send support your device links, keys or recovery phrases. If exposed, revoke the agent approval on Hyperliquid immediately; closing a tab or deleting local browser data is not a substitute for revocation.

Data handling and its limits

Anonymous click counts are live for a fixed list of buttons. Only the event type, page area, target and time are stored: no wallet, IP address, visitor ID or page URL. Totals are not unique users. The table is readable only by the server.

If installed later, the application sink retains only allowlisted event type, surface and target tuples, an event-row UUID and a server timestamp. The row UUID is not a visitor identity. There are no user/session IDs, IP, referrer, user-agent, URL/query, wallet, signature, key or per-user P&L fields in that sink. Counts are aggregate events, not unique users or user-level conversion rates; they are not verified adoption evidence.

This description covers the event sink, not all product data. Existing account/settings, Telegram linking and research features have their own data handling. Browser storage retains setup and preferences. Hosting infrastructure still processes request metadata; host log retention is not attested. We do not claim that no data is collected or promise unverified deletion or retention terms.

Vulnerability reporting

The existing public security repository is a possible vulnerability-reporting destination. Its availability and incident response are not attested; no response-time promise or SLA is made. Do not post secrets or sensitive exploit details publicly. Never include device links, keys or recovery phrases in a report.

Payout UI is review-only and settlement is disabled. Historical ledger constraints and proposed treasury/signature architecture do not establish hosted privilege protection, an independent audit or a verified public ledger. Hosted Phase 6 remains blocked.

1. If a trading key or device link is exposed, revoke the agent approval on Hyperliquid first; do not rely on closing a tab.
2. Keep a private record of the UTC time, affected page and steps to reproduce. Remove wallet identities, keys, device-link fragments and request credentials from screenshots or logs.
3. Use a repository’s private reporting option only if available. Otherwise send a minimal public contact request without exploit details or sensitive attachments. No private intake availability or response time is attested.