Privacy
aguait is a non-custodial client interface. We do not run user accounts and do not collect names, emails, or addresses. This page lists every piece of state we touch in your browser, every third-party endpoint we contact, and how to control each one.
What we store on your device
Records which wallet you connected so the app reconnects on refresh. Strictly necessary; without it the wallet picker re-opens on every page load.
Records your choice on the cookie banner (granted or denied) for one year so we don't ask again.
Records that you dismissed the "install app" prompt. Set only if you click "Not now". One year.
Records that you acknowledged the alpha-risk modal so it doesn't reappear on every visit. 30 days; bumped if the risk language changes.
Your per-trade slippage preference (1, 3, 5, or 8%). Persists across sessions so you don't reset it on every order.
Local cache of settled-market metadata (questions, side names, expiry) so trade history for finalized markets paints without re-fetching.
In-progress buy intent (stake, side, slippage, mode). Tab-scoped: clears the moment you close the tab or after the buy fires.
Local-only record of fills you triggered. Never leaves your browser. Clear it via your browser's site-data controls.
Your wallet-ownership signature and the builder-fee scope you approved, so a refresh doesn't ask you to re-sign both. Never contains the agent private key — that stays in RAM only and dies with the tab.
24-hour cache of public Hyperliquid data (outcome catalog, recent fills, balance lines) so the terminal paints from the last known good state on a cold load or feed hiccup.
Reown AppKit (the wallet picker) stores its relay session locally. Required by the wallet protocol.
What leaves your browser
Every order, balance read, and signature is sent directly to api.hyperliquid.xyz. aguait does not proxy or log these requests.
When you use a mobile wallet, your wallet and our app exchange messages through *.walletconnect.com / *.reown.com. Standard wallet plumbing: no aguait analytics ride along.
Aggregate page-view counts. No cookies in the strict sense, but a daily-rotating visitor hash. In the EU/EEA/Switzerland this is gated by the consent banner: disabled until you click Accept. Outside those regions it is on by default.
Production error reports only: no performance traces, no session replay, no console capture, no click tracking. Outgoing events have wallet addresses redacted to 0x<redacted>. Wallet-cancellation noise (user-rejected signatures, dismissed connect prompts) is filtered out. Same consent gate as analytics: in the EU/EEA/Switzerland the SDK never loads until you click Accept.
To disable both analytics and crash reporting anywhere, run localStorage.setItem('aguait-telemetry-disabled', '1') in your browser console. The setting persists across sessions.
Geo block
Change your mind
Clear the aguait_consent cookie in your browser settings to see the banner again. Browser DevTools → Application → Cookies works on every major browser.
Contact
Questions or requests: @EliecerChicott.