> 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/soc-2-type-ii-report.md).

# SOC 2 Type II Report

Learn about Mailtrap's SOC 2 Type II report and information security standards.

Mailtrap is proud to have completed a SOC 2 Type II audit, demonstrating that our information security controls are not only designed appropriately but operating effectively over time.

Our current SOC 2 Type II report covers the period from **September 1, 2025 to November 30, 2025**. During this period, an independent third-party auditor evaluated Mailtrap's controls related to the Trust Services Criteria, confirming that they were suitably designed and operating effectively to meet our commitments around security.

Our next audit period is already underway and will cover **December 1, 2025 to November 30, 2026**, continuing our commitment to ongoing, independent verification of our security controls rather than a one-time assessment.

**Requesting the report**: Because SOC 2 reports contain detailed information about internal security controls, Mailtrap's SOC 2 Type II report is available upon request under a mutual NDA. You can request it through our [Trust Center](https://trust.mailtrap.io/).

This report demonstrates that Mailtrap not only implements strong security practices but sustains them consistently over time, giving customers independent assurance around how we manage and protect their data.


---

# 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/soc-2-type-ii-report.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.
