> 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/compliance-and-certifications.md). # Compliance & Certifications This article provides a high level overview. For more detailed information, head to [Trust Center](https://trust.rhythms.ai/) Learn how Rhythms ensures compliance with industry standards, privacy regulations, and security best practices through certifications and audits. We maintain rigorous compliance with industry standards and regulations, continuously evolving our practices to meet the highest levels of security and privacy requirements. ## **Industry-Standard Certifications** SOC 2 Type II certified and NIST compliant, with at-least-annual penetration testing and regular third-party security assessments to maintain highest security standards. ## **Global Privacy Compliance** Full GDPR and CCPA compliance with implemented data privacy measures including data minimization, purpose limitation, and user rights management. Backed by comprehensive company-wide security training and enhanced protocols for production access employees. ## **Comprehensive Audit System** Detailed audit logging and reporting capabilities with configurable retention policies, providing complete visibility into system access and data operations. ## **Continuous Compliance Innovation** Continuous evolution of our security, privacy, and AI governance practices to meet and exceed emerging industry standards and regulatory requirements. --- # 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/compliance-and-certifications.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.