> 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/organizational-security.md).

# Organizational Security

### Confidentiality Agreements <a href="#confidentiality-agreements" id="confidentiality-agreements"></a>

All personnel are required to sign a confidentiality agreement prior to onboarding on eva product team.

### Employee Background Checks <a href="#employee-background-checks" id="employee-background-checks"></a>

Members of the eva team that may have access to data that customers submit to eva's services (e.g., operations engineers) are background checked as permitted by applicable law and sign confidentiality agreements.

### Employee Security Training <a href="#employee-security-training" id="employee-security-training"></a>

eva employees receive training in data privacy concepts and responsibilities, as well as eva commitments on privacy and refresher training on an annual basis.

### IT Security <a href="#it-security" id="it-security"></a>

NTT Data corporate IT policies are applied for all physical and logical security, access control, network, and devices. A summary of the Eva Access Control policy can be provided under NDA. It includes:

* Employee Workstations are Automatically Locked
* Employee Workstations Encrypted
* Limited Employee Access (Principle of Least Privilege)
* Personnel Screening
* Physical Access Control

Access to eva’s office location is monitored by a receptionist during business hours. Doors are locked outside business hours and when a receptionist is not present. Visitors to eva’s office location are required to sign in and are provided with a temporary identification badge. Physical keys and card access to areas where critical equipment is located are restricted to authorized individuals.


---

# 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/organizational-security.md?ask=<question>&goal=<endgoal>
```

`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.