> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/getting-started/security-and-wallet-safety.md).

# Security and wallet safety

Understand Proliquid account data, wallet and exchange access, local storage, and trading safety

Security and wallet safety explains what Proliquid stores, what your connected accounts authorize, and which controls protect sensitive trading information.

## Separate account layers

<table><thead><tr><th width="191.91015625">Layer</th><th>What it is for</th><th>Examples</th></tr></thead><tbody><tr><td>Proliquid account</td><td>Saves your app workspace and preferences.</td><td>Layouts, watchlists, settings, source preferences, sound alerts, compare presets.</td></tr><tr><td>Wallet connection</td><td>Connects a wallet and enables Hyperliquid and RISEx trading setup.</td><td>Builder-fee approval, local trading-key creation, and RISEx Enable TP/SL.</td></tr><tr><td>Trading account</td><td>Connects an exchange account for execution.</td><td>Binance, Bybit, and OKX API credentials and account settings.</td></tr><tr><td>Exchange state</td><td>Holds balances, positions, orders, fills, and margin state.</td><td>Account data returned by the connected venue.</td></tr></tbody></table>

Creating an account or connecting a wallet or exchange account does not place trades. Trading actions still require Terminal, News, or position-management controls.

## Wallet connection flow

Hyperliquid wallet setup has three main steps:

1. **Choose a wallet.** Connect a supported browser wallet.
2. **Approve builder fees.** Approve the maximum Proliquid builder-fee rate when required.
3. **Create a trading key.** Create the local Hyperliquid key used to submit orders.

RISEx wallet setup has four main steps:

1. **Connect a wallet.** Connect a supported browser wallet.
2. **Create a trading key.** Create the local RISEx key used to submit orders.
3. **Enable Fee.** After the trading key exists, approve the Proliquid builder fee. The trading key signs this approval. See [RISEx fees and builder fees](/getting-started/risex-trading-fees-and-proliquid-builder-fees.md).
4. **Enable TP/SL.** Allow RISEx to execute take-profit and stop-loss when the trigger hits.

The trading key is wallet-specific and stored in your browser. Clearing browser data, changing browsers, or using a new device may require setup again.

## Exchange API credentials

Binance, Bybit, and OKX credentials are stored in the browser used to connect the account. Use a trusted device and create keys with trading permission only. Withdrawal permission is not needed.

Do not paste API credentials into messages, screenshots, URLs, or support requests. Remove the account from the device when it is no longer trusted.

## QR handoff

[Link desktop to mobile](/getting-started/linking-desktop-to-mobile.md) uses a temporary QR code and an encrypted handoff. Verify the six-digit code on both screens before approving. Trading access cannot withdraw funds, and the QR payload is removed after a successful handoff.

## Disconnecting and removing access

Disconnecting a wallet or removing a trading account ends Proliquid's local connection. It does not:

* Close open positions.
* Cancel open orders.
* Stop exchange-level state from changing.
* Revoke every exchange permission by itself.

Review the account that will receive the order before submitting it. Terminal uses its active account; News quick trades use the account selected in [News settings](/settings/news.md). If you have multiple accounts, confirm the exchange icon and account label in the relevant control, then review [Balances](/terminal-sections/balances.md) and [Positions](/terminal-sections/positions.md) when available.

[Iceberg orders](/order-types/iceberg-orders.md), TWAPs, chases, and other Terminal-managed strategies can depend on local app state. Keep Proliquid open when the strategy requires it, and review active strategies before clearing browser data or switching devices.

## What Proliquid cannot do

Proliquid is an interface for market intelligence and execution on Hyperliquid, RISEx, Binance, Bybit, and OKX. It does not replace exchange-level review.

Proliquid cannot:

* Recover a wallet seed phrase or private key.
* Guarantee that browser-local data survives clearing browser storage.
* Change exchange rules for margin, liquidation, matching, or fees.
* Prevent market movement, slippage, or liquidation.
* Cancel orders or close positions unless you submit the relevant action.

Use the relevant exchange's official documentation for exchange mechanics, API permissions, and account security.

## Safe operating checklist

Before submitting orders from Proliquid:

1. Confirm the exchange and account that will receive the order. Use Terminal's active account for Terminal orders and the account shown in the News quick-trade menu for News orders.
2. Confirm the selected market belongs to that venue.
3. Review size, side, margin mode, leverage, reduce-only, TP / SL, and slippage.
4. Check [Account](/terminal-sections/account.md), [Orderbook](/terminal-sections/orderbook.md), and [Positions](/terminal-sections/positions.md).
5. Monitor [Open orders](/terminal-sections/open-orders.md), [Trade history](/terminal-sections/trade-history.md), and [Order history](/terminal-sections/order-history.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.proliquid.xyz/getting-started/security-and-wallet-safety.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.