> For the complete documentation index, see [llms.txt](https://trustcenter.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustcenter.syntphony.com/products/syntphony-business-transformation/intelligent-automation/privacy/data-encryption.md).

# Data Encryption

All backup data is automatically encrypted when stored in the cloud using Azure Storage Encryption, supporting compliance and security commitments. Data at rest is protected with 256-bit AES encryption, one of the most secure block cipher methods available, compliant with FIPS 140-2.\
\
Furthermore, all backup data in transit is securely transmitted over HTTPS, ensuring it remains within the Azure backbone network. For database storage, Transparent Data Encryption (TDE) is enabled by default in Azure, safeguarding sensitive information from unauthorized access—even at rest.\
\
This comprehensive encryption strategy ensures data security while facilitating compliance with data protection regulations and building trust in cloud-based information management.\
\
For detailed information on the types of encryption used by Microsoft Azure, visit the official Microsoft page:<br>

{% embed url="<https://docs.microsoft.com/es-es/azure/security/fundamentals/encryption-overview>" %}


---

# 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://trustcenter.syntphony.com/products/syntphony-business-transformation/intelligent-automation/privacy/data-encryption.md?ask=<question>&goal=<user_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.