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

# Certifications

Our platform's data security certifications provide peace of mind that your information is protected.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>🧾 SOC 1 Type II</strong></td><td>impact.com prioritizes data security with SOC 1 type II certification. This independent verification assures clients of the effectiveness of our internal controls over financial reporting.</td></tr><tr><td><strong>🌐 ISO/IEC 27001:2022</strong></td><td>Your data is secure at impact.com. We maintain ISO/IEC 27001:2022 certification, an internationally recognized standard for information security management. This means we have robust security practices in place to protect your data when you use our SaaS subscriptions.</td></tr><tr><td><strong>💳 PCI-DSS Level 4</strong></td><td>impact.com is a PCI-DSS Level 4 Merchant and maintains its certifications through annual SAQ completion. This standard is designed to protect payment card information from unauthorized access, use, or disclosure.</td></tr></tbody></table>


---

# 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://trust.impact.com/data-security-and-privacy/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.