> 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/soc-2.md). # SOC 2 BugSplat has implemented processes to support SOC 2 based on the Trust Services Criteria relevant to Security (applicable Trust Services Criteria) outlined in TSP section 100, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (AICPA, Trust Services Criteria). BugSplat has created a Systems Description (or Section 3), conducted an annual risk assessment, identified applicable risk mitigation strategies, completed and reviewed information security policies and procedures, and prepared an internal controls matrix. BugSplat has partnered with [SecureFrame](https://secureframe.com/) to implement our security framework. Additional supporting documents regarding the BugSplat SOC 2 program, results of BugSplat's SOC-2 audit, and other information are [available to customers and curious parties under NDA](/guides/production/security-privacy-and-compliance/bugsplat-security-program-inquirys.md). Please contact for follow-up questions. --- # 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/soc-2.md?ask=&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.