> 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/enterprise-security.md). # Enterprise Security This article provides a high level overview. For more detailed information, head to [Trust Center](https://trust.rhythms.ai/) Learn how Rhythms ensures enterprise-grade security with multi-layered protection, encryption, strict data isolation, and comprehensive access controls. Our multi-layered security approach ensures comprehensive protection of your data and systems. We implement industry-leading security measures at every level of our infrastructure. ## **Enterprise-grade Security Infrastructure** Advanced Web Application Firewall (WAF) with real-time threat detection, DDoS protection, and comprehensive edge security measures to protect against emerging threats. ## **Advanced Encryption Framework** End-to-end encryption for all data with Bring Your Own Key (BYOK) support for customer control over encryption keys, securing sensitive information, credentials, and uploaded artifacts. ## **Complete Data Isolation** Strict tenant isolation with dedicated processing environments, ensuring complete separation of customer data. Each customer's data is processed in isolated environments with no cross-tenant data exposure. ## **Comprehensive Access Controls** Role-based access control (RBAC) with granular permissions, time-bound access limitations, and strict data isolation between customer environments. --- # 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/enterprise-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 `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.