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

# Security & Privacy

We take a lot of steps to secure your data. We'll explain how we store and secure your data below. <br>

**Note:** Some of the methods we use to protect your data are not included below as they would lose some of their effectiveness if we publicly disclosed them.

***

## Data Storage and Encryption

<figure><img src="/files/lw6tuipLQvrUur9wbjaL" alt=""><figcaption><p>This is an example for illustration purposes.</p></figcaption></figure>

TradeStream downloads your trading data from exchanges and we store in in our servers in order to display your trading analytics. \
\
All of your trading data is encrypted in our databases using symmetric AES256 encryption multiple times. So even if someone manages to get access to TradeStream's databases they still will not be able to read your personal data.

***

### Rotating encryption keys

The encryption keys used to encrypt your data are changed on an undisclosed schedule. This is so that even if someone figures out our encryption key, by the time they've figured it out we will already be using a new set of encryption keys to secure your data. Which would mean your data stays safe.

***

### API Key Security and Encryption

To see more information on how API Keys are secured please refer to the page on API Key Security and Encryption.

{% content-ref url="/pages/xTwI3yTx1EjBuI1lcZEl" %}
[API Key Security](/misc/api-key-security.md)
{% endcontent-ref %}

***

### Backups

We take frequent backups of your data so that in case of some catastrophic technical failure we should be able to continue services as normal with at most the past few hours of data lost.

\ <br>


---

# 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.tradestream.xyz/misc/security-and-privacy.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.