> For the complete documentation index, see [llms.txt](https://docs.stablejack.xyz/stablejack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stablejack.xyz/stablejack/security/wallet-and-exchange-connection-security.md).
# Wallet and Exchange Connection Security
Learn how wallet and exchange connections work in StableJack, what permissions to review, and how to keep your account secure.
StableJack may let users connect wallets, exchanges, or other trading integrations to support market analysis, position tracking, and trading workflows. These connections help StableJack provide a more useful trading experience, but users should always understand what they are connecting and what permissions they are approving.
### What happens when I connect a wallet or exchange?
When you connect a wallet or exchange account, StableJack can use the connection to display relevant information, support trading workflows, or help you manage positions, depending on the integration.
Your funds remain in your own wallet, exchange, or trading account. StableJack does not become the custodian of your assets.
### What permissions should I review?
Before approving any wallet or exchange connection, review the permissions carefully.
You should check whether the connection can only read account information, or whether it can also place trades, approve transactions, or perform other actions. Do not approve permissions you do not understand.
For exchange connections, review whether the API key or integration allows trading, withdrawals, or read-only access. When possible, use limited permissions and avoid enabling withdrawals unless there is a clear reason.
### Can StableJack access my private key or seed phrase?
No legitimate StableJack flow should ask for your private key or seed phrase.
Never share your seed phrase, private key, password, or recovery phrase with anyone. StableJack will never ask for this information through support, Telegram, X, email, or direct message.
If someone asks for your private key or seed phrase, treat it as a scam.
### How can I keep my connection secure?
Use only StableJack’s official website and official links. Be careful with fake websites, impersonator accounts, and unofficial support messages.
When connecting an exchange account, use strong passwords, enable two-factor authentication, and review API permissions regularly. If an API key is no longer needed, revoke it from your exchange account.
When using a wallet, review every transaction before signing. Check the asset, amount, network, contract, and action being requested.
### What should I do if something looks suspicious?
If you notice suspicious activity, disconnect your wallet or exchange account, revoke unnecessary permissions, rotate API keys, and contact StableJack support through official channels.
Do not respond to unofficial messages claiming to be support. Do not send funds to unknown addresses. Do not share sensitive account information.
### Summary
Wallet and exchange connections can make StableJack more useful for analysis, trading, and position management, but users should manage permissions carefully. Always use official links, review every approval, avoid sharing sensitive information, and revoke access if you no longer need a connection.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.stablejack.xyz/stablejack/security/wallet-and-exchange-connection-security.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.