> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/security-and-compliance/data-security.md).
# Data Security
### Data Encrypted At-Rest
All data hosted by eva is encrypted. Eva uses industry-accepted encryption products to protect data at rest, with 256-bit AES encryption.
### Data Encrypted In-Transit
eva cloud uses the latest cypher suites to encrypt all the data during transfer between its client channels and server: TLS 1.2/1.3, and HTTPS are used to protect data in transit.
### **Encryption Key Management**
All eva databases and snapshot backups use strong volume (disk) encryption by default to protect data at rest. The use of self-managed keys can help customers achieve additional levels of confidentiality and data segmentation.
---
# 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-conversational-ai.syntphony.com/security-and-compliance/data-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.