> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/strategic-approach/strengthening-privacy-and-security.md).
# Strengthening Privacy & Security
*We prioritize the protection of user data and assets by implementing advanced cryptographic solutions and multi-level security protocols. Our flexible privacy controls allow users to adjust their level of anonymity while maintaining compliance with legal standards.*
## **Implement advanced cryptographic solutions**
* Protect user data and assets with multi-level security protocols.
* Utilize cutting-edge encryption methods to secure transactions and personal information.
## **Develop a multi-level security system**
* Safeguard assets from unauthorized access through features like multi-signature requirements and time-locked transactions.
* Incorporate session-based trading to improve security during user sessions.
## **Provide Flexible Privacy Controls**
* Allow users to control their level of anonymity while complying to legal and ethical standards.
* Maintain a commitment to regulatory compliance and ethical fund verification operations.
---
# 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.evedex.com/strategic-approach/strengthening-privacy-and-security.md?ask=&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.