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

# BugSplat Security Program Inquirys

BugSplat is committed to maintaining the highest standards of security for our products and services. To achieve this, we partner with SecureFrame, a leader in security compliance, to implement a robust security framework that aligns with industry best practices.

**Interested in Our Security Details?**

For those keen to delve deeper into the specifics of our security measures, including the BugSplat SOC 2 program, findings from our SOC-2 audit, or to request additional supporting documents, we've streamlined the process for your convenience.

**How to Request Information:**

* **Email Contact:** Simply reach out to us at **<sales@bugsplat.com>**. Whether you're a current customer or just exploring, we welcome your interest and are here to provide the information you need.

**Confidentiality Assurance:**

We understand the importance of confidentiality in security matters. Therefore, access to detailed information about BugSplat's security program, including audit results and certifications, is provided under a Non-Disclosure Agreement (NDA). This ensures that sensitive information remains protected while allowing us to share our commitment to security with you.

**We're Here to Help:**

At BugSplat, your security concerns are our top priority. We're dedicated to providing transparent and detailed information to support your decision-making process. Should you have any questions or require further assistance, please don't hesitate to get in touch.

Thank you for your interest in BugSplat's security initiatives. We look forward to partnering with you to meet your security needs.


---

# 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.bugsplat.com/guides/production/security-privacy-and-compliance/bugsplat-security-program-inquirys.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.
