> 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/business-continuity.md).

# Business Continuity

### Business Continuity Plan <a href="#business-continuity-plan" id="business-continuity-plan"></a>

NTT DATA eva® maintains a written Business Continuity Plan that documents the organization’s processes for triaging, remediating, and recovering from catastrophic incidents or disasters that may affect critical business processes.

### Data Backups <a href="#data-backups" id="data-backups"></a>

eva services are deployed into multiple physically redundant zones within Google Cloud Platform (GCP) and Microsoft Azure regions. Data is replicated in near real-time across multiple zones. Any zone can fail, and the service continues to operate normally.

In addition, critical settings and customer subscription configurations are backed up on at least a daily basis. Backup system settings are secured, encrypted, reviewed and monitored on a weekly basis to ensure this is operating effectively. In addition, access to backup media is highly restricted, ensuring that customer data remains secure and confidential.

### Disaster Recovery Plan <a href="#disaster-recovery-plan" id="disaster-recovery-plan"></a>

Eva implements a disaster recovery plan that outlines its response to unplanned disruptions such as natural disasters, power outages, and cyber-attacks.


---

# 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-conversational-ai.syntphony.com/security-and-compliance/business-continuity.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.
