> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/platform-controls/tenant-and-environment-isolation.md).

# Tenant & Environment Isolation

### Scope

This page covers tenant isolation and environment separation.

### Data ownership and storage

Taloflow maintains clear separation between different types of data:

**Taloflow Platform Data**:

* Evaluation configurations
* Methodology templates
* Vendor databases
* Rating criteria

**Client Data**:

* Evaluation results
* Custom configurations
* Reports and exports
* All data created within your evaluations

### Personal Information (PII)

* **No client personal data** is stored in Taloflow's database
* **All Personally Identifiable Information (PII)** is managed exclusively by Auth0
* **Zero proprietary client data** storage outside of evaluation-specific information

### Environment Separation

* **Development**: Isolated development environment
* **Staging**: Pre-production testing environment
* **Production**: Live customer environment

Each environment is separated with no cross-contamination of data or credentials.

No customer evaluation data is used in development or staging.

Secrets and credentials are not shared across environments.

### Network segmentation

Taloflow uses network segmentation to limit lateral movement.

Subnets are restricted by firewall and security rules.

Administrative access uses controlled entry points (for example, bastion-style access).

### Database Access Control

* **Server-level restrictions**: Database access is controlled at the server level
* **OPA authorization**: All user requests pass through Open Policy Agent evaluation
* **Functional table access**: Some tables require related access for functionality (e.g., evaluations require access to policies, status, and settings tables)
* **Resolver-level security**: Additional security controls at the application resolver level


---

# 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.taloflow.ai/security/platform-controls/tenant-and-environment-isolation.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.