> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/security-privacy-and-compliance/ai-security-and-governance.md). # AI Security & Governance This article provides a high level overview. For more detailed information, head to [Trust Center](https://trust.rhythms.ai/) Learn how Rhythms ensures secure AI use with zero data retention, protected model training, and real-time security controls. We prioritize the security and responsible use of AI technology, ensuring your data remains protected throughout all AI operations while maintaining the highest standards of governance. ## **Zero Data Retention** Guaranteed zero data retention across all AI operations with immediate data sanitization after processing. Your data is never stored or used for model training. ## **Protected Model Training** No customer data is ever used in AI model training, ensuring complete privacy and confidentiality of your business information. ## **Real-time Security Controls** Advanced security measures for all AI interactions including prompt shields, automated injection detection, and comprehensive input validation. ## **Security-First AI Design** Every AI feature is built with security and enterprise requirements as core principles, not afterthoughts. Our architecture ensures responsible AI deployment with enterprise-grade safeguards from the ground up. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/security-privacy-and-compliance/ai-security-and-governance.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 `build a script that syncs our docs to a CMS` 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.