> For the complete documentation index, see [llms.txt](https://docs.codewords.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codewords.ai/security.md). # Security Your security, safety, and privacy are our top priority. CodeWords takes a security-by-design approach to protecting your data. Our team is continuing to make investments so you can use CodeWords with confidence. We're currently in the process of getting our SOC 2 Type II compliance. These are the security measures and processes we've implemented: **Business continuity** * Ongoing internal education and compliance updates * Comprehensive recovery plans * Active communication procedures to our customers * Regular release notes and product updates **Data governance and privacy** * Privacy by design principles * Transparent data handling * Regular access reviews and monitoring * Data classification and retention policies You can access our full [Privacy Policy](https://codewords.ai/privacy-policy), [Terms and Conditions](https://www.codewords.ai/terms-conditions), [Data Processing Agreement](https://drive.google.com/file/d/1En8w4yStMyDWVoZWK9kbxOhHpIh4ff5A/view) to read more. **Security operations** * Regular testing and code reviews * Continuous integration of security measures in development pipelines * Documented response procedures * Automated alert systems for rapid response --- # 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.codewords.ai/security.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.