// DATA & PRIVACY
Privacy
Last updated: 9 November 2026
This page describes the data handled by the current AZIMUTH beta.
1. Account and saved work
AZIMUTH links your account to your public wallet address and stores your display name, wallet authentication challenges, and server-side session records. Wallet sign-in does not require an email address or password. Existing email accounts, where enabled, store an email address and salted password hash. Saved data includes your manual holdings, tracked public addresses, research questions and results, saved backtests and their price snapshots, and followed strategies. Contact form submissions are stored in the feedback queue.
2. Public content
Publishing a playbook makes its title, methodology, risk label, display name, and follower count publicly visible. Saved research is private to your account. On-chain and HyperCore positions and balances queried by public address are public information.
3. Connected services
Market metadata, quotes, candles, books and public account snapshots are fetched from Hyperliquid. Public addresses you enter in Account risk are sent to Hyperliquid to retrieve positions and spot balances; wallet sign-in alone does not trigger a balance lookup. Optional external derivatives data receives requested asset symbols, not your address, question or saved work. Historical Arc address records retain their original network and are not reinterpreted as Hyperliquid accounts. When AZIMUTH AI is enabled, your research question and public market evidence are sent to Anthropic; your private portfolio is not automatically included. Stripe processes checkout and billing when paid subscriptions are enabled. Resend processes verification and password recovery emails for existing email accounts when account email is configured.
4. Sessions and security
An essential HttpOnly session cookie keeps you signed in for up to seven days. Your browser remembers your chosen wallet provider so it can check that the same wallet is still connected. Signing out invalidates that session. Wallet authentication uses a signed message to verify address ownership; it does not send a transaction or grant trading access. Developer API keys are shown once and stored as hashes with their name, prefix, creation time, last-use time and revocation status. These keys access public data and calculations, not your saved workspace or trading account. You can revoke them in API & MCP; account deletion removes the key records. Request rate limits use hashed network identifiers. The application does not accept exchange trading keys, seed phrases, or wallet private keys. Production hosting must provide HTTPS.
5. Retention and requests
Saved work remains in the application database until removed. You can unfollow playbooks in the terminal. Historical holdings and address records remain in your account export until account deletion. Account offers a JSON export, session controls, and deletion for free accounts without billing records. Wallet accounts confirm deletion with a fresh signed message; existing email accounts use their password. Accounts linked to billing require a request through Contact so subscriptions and retained billing records can be handled correctly. Verified operators can moderate public strategies and manage contact requests; account security and moderation actions are recorded in an audit log. Hosting backups may retain earlier database copies according to the operator’s backup policy.
Questions about this document? Submit a request through the contact page.