> For the complete documentation index, see [llms.txt](https://docs.cerrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cerrix.com/about-cerrix/trust-and-compliance.md).

# Trust & Compliance

Trust, security, privacy, and service transparency are central to CERRIX. Use this page to find our policies, assurance reports, certifications, and service commitments.

### Security and assurance

{% content-ref url="/pages/CBh1oad94NZOzC16pnfS" %}
[Strategic Information Security Policy](/about-cerrix/trust-and-compliance/strategic-information-security-policy.md)
{% endcontent-ref %}

{% content-ref url="/pages/9EUtmcfcx9LgZV780UUM" %}
[ISO 27001](/about-cerrix/trust-and-compliance/iso-27001.md)
{% endcontent-ref %}

{% content-ref url="/pages/l5ucHxTQBh2H6g2Z5Z6u" %}
[ISAE 3402 Type II](/about-cerrix/trust-and-compliance/isae-3402-type-ii.md)
{% endcontent-ref %}

{% content-ref url="/pages/Jiib8tbM0AF7JeSIYS7E" %}
[Security Statement](/about-cerrix/trust-and-compliance/security-statement.md)
{% endcontent-ref %}

{% content-ref url="/pages/BzlSelo3kEkmBiUeTYtZ" %}
[FSQS Certificate](/about-cerrix/trust-and-compliance/fsqs-certificate.md)
{% endcontent-ref %}

{% content-ref url="/pages/rMH6yZiOAVlPw7lhcvDt" %}
[Security FAQ](/about-cerrix/trust-and-compliance/security-faq.md)
{% endcontent-ref %}

### Privacy and responsible business

{% content-ref url="/pages/zcH5cT5ELHLdN86w8CKH" %}
[Privacy / GDPR](/about-cerrix/trust-and-compliance/privacy-gdpr.md)
{% endcontent-ref %}

{% content-ref url="/pages/5RktmS6Ir1CNj3x3vfHo" %}
[Subprocessors](/about-cerrix/trust-and-compliance/subprocessors.md)
{% endcontent-ref %}

{% content-ref url="/pages/l4kcCRvUfpElgI1mzACC" %}
[Corporate Social Responsibility](/about-cerrix/trust-and-compliance/corporate-social-responsibility.md)
{% endcontent-ref %}

{% content-ref url="/pages/Vr40HEFzYukNCjIVPlRr" %}
[CERRIX AI](/about-cerrix/trust-and-compliance/cerrix-ai.md)
{% endcontent-ref %}

### Service commitments

{% content-ref url="/pages/ceQBzPqmmsuUHSkPBqgN" %}
[SLA Dashboard](/about-cerrix/trust-and-compliance/sla-dashboard.md)
{% endcontent-ref %}

{% content-ref url="/pages/LSKAUJnewrwAxx8C2s6s" %}
[Service Level Agreement (SLA)](/about-cerrix/trust-and-compliance/service-level-agreement-sla.md)
{% endcontent-ref %}


---

# 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.cerrix.com/about-cerrix/trust-and-compliance.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.