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

# Wallet Safety

Wallet safety is the user’s responsibility.

Zerax AI will never ask for your seed phrase, private key or recovery phrase.

{% hint style="danger" %}
Anyone asking for your seed phrase or private key is trying to steal your wallet.
{% endhint %}

***

### Never Share

Do not share:

* Seed phrase
* Private key
* Recovery phrase
* Wallet password
* Verification codes

***

### Safe Wallet Habits

Before confirming a transaction:

* Check the website URL
* Check the connected wallet
* Check the network
* Read the wallet confirmation
* Confirm only if the details are correct

***

### Common Scam Signs

Be careful of:

* Fake support accounts
* Private messages offering help
* Fake airdrops
* Fake token import links
* Unknown contract addresses
* Requests for wallet recovery phrases

***

### Summary

Your wallet keys should always stay private.

Zerax AI does not need your private key to help you use the platform.


---

# 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.zeraxai.com/security/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.
