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

# Private-key export and safety

Keep your copy wallet credentials private and understand the key export process.

Your wallet's **private key** provides full control over its funds. Anyone who obtains it can move your tokens. We will never ask you to send your key to support.

## Export your key

1. Open **Balance** or **Copytrade → Wallet**.
2. Select the private-key export option.
3. Read the warning shown in Telegram and confirm only if you understand the risk.
4. If the key is revealed, store it securely and follow the bot's deletion instructions. The reveal may be time-limited or subject to export limits.

{% hint style="danger" %}
**Never share or forward a private key.** Do not post screenshots of the key, paste it into untrusted websites or send it to someone claiming to be Callouts support.
{% endhint %}

## If you suspect exposure

Stop using the exposed wallet. Move funds to a new secure wallet where possible, then update your trading setup to use a safe wallet.

[Return to Wallet management](/callgraph-docs/wallet-and-security/wallet-management.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://callgraph.gitbook.io/callgraph-docs/wallet-and-security/key-export-and-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.