> 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/trust-and-governance/compliance-and-certifications.md).

# Compliance & Certifications

Current audit status, certifications, and materials for customer reviews.

### SOC 2 Type II

Taloflow has retained **Prescient Assurance** to conduct a SOC 2 Type II audit.

We will update this page when the report is available. If you need the latest status for a vendor review, contact us via the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).

### Industry Partnerships

Taloflow is an **AWS Advanced Technology Partner**.

This status requires a technical and architectural review. It also requires meeting AWS partner program requirements.

### What we share during compliance reviews

We commonly provide the following, as applicable:

* High-level security architecture and data flow details
* A list of security controls relevant to customer due diligence
* Confirmation of current audit and certification status

Send requests through the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).


---

# 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.taloflow.ai/security/trust-and-governance/compliance-and-certifications.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.
