> For the complete documentation index, see [llms.txt](https://holoscope-trade.gitbook.io/holoscope/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://holoscope-trade.gitbook.io/holoscope/trust/wallets-and-security.md).

# Wallets and Security

HoloScope uses Privy accounts and embedded Solana wallets for the trading terminal.

## Simple onboarding

Sign in with email, Google, or X, or with a wallet you already use. Privy creates the embedded wallet automatically.

The wallet holds:

* your **trading balance**, held as USDC;
* a little **SOL** for network fees;
* supported onchain collectibles.

Deposit SOL and it is converted to your trading balance, with enough kept for network fees. USDC deposits go straight to the trading balance. The same Solana address accepts both. Send only Solana SOL and USDC to it. See [Deposits, Gas, and Withdrawals](/holoscope/product/deposits-and-gas.md).

## Your keys

HoloScope does not store private keys or recovery material.

You can export your private key from your profile and import it into a wallet such as Phantom or Solflare. Back it up somewhere safe. Anyone who has it controls your funds and cards, so never share it with anyone, including someone claiming to be HoloScope support.

## How one-click trading works

Buys, sells, limit orders, and bids go through a delegated signer, so you don't get a wallet popup each time and automatic orders can run while you are away.

That permission is limited to the marketplaces and transaction types HoloScope trades, plus converting SOL to USDC and back. A conversion may only swap SOL for real Solana USDC through Jupiter; it is simulated first and refused if it would move any other token or hand control of your wallet to anyone. Before a marketplace trade is signed, HoloScope checks that the transaction matches your quote. Automatic buying stays off until you turn it on and set a limit.

## Withdrawals

Withdrawing needs two-factor, and you approve each transfer yourself in Privy's window. HoloScope's signer cannot send funds out of your wallet on its own.

## Staying safe

* Use only official links: [holoscope.trade](https://holoscope.trade/), [@holoscopetrade on X](https://x.com/holoscopetrade), the [HoloScope Discord](https://discord.gg/holoscope), and these docs.
* $HOLO is not live. Anyone offering it today is not HoloScope.
* The [Telegram bot](/holoscope/product/telegram-bot.md) can't trade, and it will never ask for your keys, password, or a signature.


---

# 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://holoscope-trade.gitbook.io/holoscope/trust/wallets-and-security.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.