The single most important thing to know
Your funds never leave your exchange account. Hyperoru is a trading brain. It signs orders on your behalf using a key you provision with trading-only permissions. USDC, USDT, HYPE, BTC, and every other asset always live at the exchange (Hyperliquid, Binance), in your own account, under your own custody. You can withdraw them at any time without Hyperoru’s cooperation.How keys are stored
Exchange keys: encrypted at rest
Exchange keys: encrypted at rest
The API keys you connect to your AI traders (Hyperliquid API wallet private key, Binance API key and secret) are encrypted before they touch the database using envelope encryption with a key that lives in a dedicated secrets manager — never in source code, never in environment files shipped with a build.When a trader runs, the platform decrypts the key just long enough to sign an exchange request, then discards it from memory.
Session tokens: opaque and revocable
Session tokens: opaque and revocable
Your API session token is a long random string. It expires after 180 days and can be rotated at any time by logging in again. Old tokens become invalid the moment you revoke them. See Authentication.
Passwords: one-way hashed
Passwords: one-way hashed
Your Hyperoru password is stored as a modern slow hash (Argon2). Even a full database compromise cannot be reversed into passwords. We do not ship secrets via email; password resets go through a signed reset link.
LLM provider keys: encrypted per trader
LLM provider keys: encrypted per trader
Your OpenAI, Anthropic, Google, or DeepSeek keys are scoped to the specific AI trader you attached them to, encrypted the same way as exchange keys, and never exposed back to the browser.
What Hyperoru can and cannot do on your behalf
| Action | Can Hyperoru do it? |
|---|---|
| Place orders on Hyperliquid and Binance Futures | Yes — that is the point. |
| Modify or cancel orders you opened through the platform | Yes |
| Read your positions, balances, and order history | Yes |
| Withdraw funds to a wallet | No — never. Withdrawal permissions should not be enabled on your exchange keys. |
| Transfer funds between your own sub-accounts | No — never. |
| Trade on an exchange account you did not explicitly connect | No — keys are scoped per trader. |
| Read or send messages on your behalf (Telegram, Discord, email) | Only on the bot channels you explicitly wire up. |
| Share your data with other users | No — your strategies, traders, and trade history are private to your account. |
What the platform enforces automatically
- Per-trader isolation. Each AI trader has its own exchange credentials, its own LLM credentials, and its own on-off switch. A bug or mistake in one trader cannot reach into another.
- Sandboxed program strategies. Python programs run in a sandbox with no network access, no filesystem access, and a strict CPU/memory budget. The only thing a program can do is return a decision.
- Decision validation. Before an order leaves the platform, Hyperoru validates it against per-trader limits: maximum leverage, maximum notional, maximum open positions, and allowed symbols.
- Rate limits everywhere. The API rate-limits each session token and IP. The WebSocket rate-limits each connection. These protect you from a runaway script blowing through your exchange rate limits.
What you should do on your side
Use a strong password
Long, unique, stored in a password manager. Re-used passwords are the biggest cause of compromised crypto accounts.
Enable 2FA on your exchange account
Hyperoru never needs your 2FA secret. It only holds an API key. Keep 2FA on your exchange login so a compromised password alone cannot drain your funds.
Create keys with minimum permissions
On Binance: enable Futures, disable Withdrawals. On Hyperliquid: use an API Wallet (not your master seed) and set a reasonable daily limit if available.
Restrict by IP where you can
If your integration runs from a fixed server, lock the exchange API key to that IP. Keeps an attacker from using the key even if it leaks.
Rotate session tokens and API keys periodically
Every 30-90 days is a reasonable cadence, and immediately if a device or machine is lost.
Start on testnet
Every exchange offers a testnet. Run your first trader there for at least a few days and confirm it behaves the way you expect before funding mainnet.
Cap notional and leverage
Configure conservative maximums on each trader — low leverage, small notional per trade. You can raise them later. You cannot un-liquidate a position.
Operational security at the platform level
- HTTPS everywhere. All API traffic goes over TLS. Never send credentials over plain HTTP.
- Centralized logging and monitoring. Every request is logged with a request id, without sensitive payloads, so support can trace an issue without learning your secrets.
- Deployment isolation. Production runs separately from any development or staging environment. There is no path from a test environment into your live account.
- Principle of least privilege. Internal services only have access to the resources they need. The LLM runner, for example, cannot reach exchange credentials — it only sees redacted prompts and receives back structured decisions.
- Incident playbooks. If a provider experiences downtime or a credential leak is suspected, published runbooks describe the response. Status updates go to status.hyperoru.com.
Data handling
| Data | Where it lives | How long |
|---|---|---|
| Your account and email | Hyperoru database | As long as your account exists |
| Exchange credentials | Encrypted at rest in Hyperoru database | Until you delete the trader |
| Prompts and decisions | Hyperoru database | Retained for analytics and audit |
| LLM provider logs | At your LLM provider, under their policy | Controlled by your provider settings |
| Trade history | Hyperoru database and at the exchange | Indefinitely |
| Support emails | Your email provider and Hyperoru’s ticketing system | Per standard business retention |
Responsible disclosure
If you believe you have found a security issue:- Email security@hyperoru.com with details.
- Do not test against other users’ accounts.
- Do not post the issue publicly until we have responded.
What to do if something feels wrong
If you notice trades you did not expect, decisions that make no sense, or a position size that seems off, do this in order:- Go to the AI trader’s settings in the app and toggle Stop Trading. This halts new orders immediately.
- On the exchange, close any open positions manually if you are uncomfortable.
- Rotate your Hyperoru session token (log in again) and your exchange API key.
- Contact support@hyperoru.com with the trader id and approximate UTC timestamp. Include the
request_idfrom any error body if you have one.
Next
FAQ
The most common questions new users ask.
How the platform works
What happens between a signal firing and an order reaching the exchange.