> For the complete documentation index, see [llms.txt](https://whitepaper.silencio.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.silencio.network/technical-overview/database-backups-and-encryption.md).

# Database Backups and Encryption

We understand the importance of keeping user data safe and accessible. That is why we have robust backup practices in place, including the following:

* **Daily Backups:** We perform daily database backups to protect against potential data loss. These backups are stored on a separate server, ensuring availability even if the central system encounters an issue.
* **Encrypted Backups:** To enhance security, all backups are encrypted. This ensures that the data remains secure and unreadable if unauthorized access occurs.
* **Disk Snapshots:** We also take disk snapshots, which capture the state of our data at specific moments. This allows us to quickly restore systems to a previous state in case of data corruption or accidental deletion.

With these backup and recovery practices in place, we aim to ensure that user data is secure and readily available when needed, providing peace of mind to those using our services.


---

# 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://whitepaper.silencio.network/technical-overview/database-backups-and-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.