> For the complete documentation index, see [llms.txt](https://docs.appsurify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appsurify.com/security-and-compliance/security-and-compliance.md). # Security & Compliance Security & Compliance Appsurify’s commitment is to provide the latest security procedures to every enterprise subscriber. Here, we will detail our approach to security so that our subscribers and users can better understand how their data is protected. ## **TERMS OF SERVICE** Appsurify, Inc. Terms and Service found [Here](https://appsurify.com/saas-terms-of-service/). ## **PRIVACY POLICY** Appsurify, Inc. (“Appsurify”, “we”, “us”, or the like) provides this Privacy Policy to inform users of our policies and procedures regarding the collection, use and disclosure of personally identifying information (or “PII”) received from users of our website and our software-as-a-service platform (the “Service” or “Website”). Full Privacy Policy found [Here](https://appsurify.com/privacy-policy/). ## Appsurify Trust Cloud We actively monitor over 83 controls in our securely hosted Azure Infrastructure to ensure all best practices are up to date. Request Access to our [Trust Cloud Here](https://appsurify-trust-cloud.trustshare.com/home) for relevant security and compliance documentation. --- # 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.appsurify.com/security-and-compliance/security-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.