> For the complete documentation index, see [llms.txt](https://docs.copin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copin.io/features/centralized-copy-trading-ccp/faqs-about-your-api-security.md).

# FAQs about your API security

### 1. Can Copin withdraw your assets via API?

* No, we only require API access to your "derivatives" wallet. We are not permitted to access any of your other wallets, including but not limited to: Spot, P2P, Funding, etc.
* Even CEX platforms do not allow withdrawing users' assets via API.

### 2. How does Copin store your API keys?

* We store them following the [OWASP](https://www.cloudflare.com/learning/security/threats/owasp-top-10/) security standards (similar to how user passwords are stored).
* All critical information about users' API keys, such as secret keys or passphrases, is encrypted when stored in our database.
* Therefore, even if our database is hacked, the hacker will not be able to access your API keys.

### 3. **How can I make my API keys more secure?**

* Never share your API key and secret with anyone.
* We recommend creating new and updating your API keys every 30 days.


---

# 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.copin.io/features/centralized-copy-trading-ccp/faqs-about-your-api-security.md?ask=<question>&goal=<endgoal>
```

`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.