> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/privacy-and-security/iso-certification.md).

# ISO certification

Learn about Mailtrap's ISO/IEC 27001:2022 certification and information security standards

Mailtrap is proud to be ISO/IEC 27001:2022 certified, demonstrating our commitment to the highest standards of information security.

In April 2024, we have successfully completed the ISO certification process, meeting all requirements for ISO/IEC 27001:2022 and officially achieving certification.

In March 2025, we have underwent a surveillance audit that confirmed our ongoing compliance, allowing us to maintain our certification without interruption.

<a href="https://drive.google.com/file/d/1JbJwCw6ALwMxCAGo_gaK-TihYoxYtwqB/view?usp=drive_link" class="button primary">ISO/IEC 27001:2022 certificate</a>

This certification demonstrates that Mailtrap adheres to rigorous security practices for managing information security risks, safeguarding data, and continually enhancing our security controls.


---

# 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.mailtrap.io/account-and-organization/privacy-and-security/iso-certification.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.
