> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/getting-started/overview/security-privacy-and-compliance.md). # Security, privacy and compliance As a SaaS provider and security vendor, DoControl is committed to best practice protection of our customers’ data. To do so, we have invested in: * Compliance certifications (ISO 27001, SOC2 type II) * Publicly available self-assessments * Penetration testing * Data processing addendum * Information Security Policy Please review our Security, Privacy & Compliance program [here](https://www.docontrol.io/security). If you have any questions or suggestions, please reach out . ## LLM usage disclaimer DoControl uses large language models (LLMs) to enhance AI features such as: * Global search * Alerts * Dot AI assistant (beta) These technologies improve your experience by surfacing relevant insights whenever natural language questions are asked, enabling you to interact more intuitively with the DoControl platform. DoControl’s first priority is to protect your data. * **Internal processing only** - DoControl's LLM, model and processes are hosted within DoControl’s internal environment, without any access to the internet. All searches for specific data items are performed only within DoControl’s internal systems. * **No model training** - Customer data is not used to train or improve third-party models. Your sensitive data remains secure within our system. Customer data and search queries are never sent to, stored by, or used to train any external LLM or AI service. DoControl’s use of LLM is designed to increase productivity and intelligent insights, while keeping your data safe and secured at all times. --- # 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.docontrol.io/docontrol-user-guide/getting-started/overview/security-privacy-and-compliance.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.