> For the complete documentation index, see [llms.txt](https://docs.apacx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apacx.io/legal-compliance/privacy-policies.md). # Privacy Policies Thank you for choosing the relevant service(s) (the “Services”) and/or product(s) (the “Product”) provided by APACX LTD. (“PHT”) and its affiliates (hereinafter also referred to as “I”, “me”, “my”, “we”, “us” and “our” or the “Company”). By accessing or using our Services/Products, you CONSENT to the policies and practices set out in this privacy policy (the “Privacy Policy”) and represent and warrant that you have the valid consent and authority from the Relevant Person(s) (defined below) for us to collect, use, disclose and/or process your Personal Data as described herein. This Privacy Policy describes how we will collect, use and disclose your personal data when you access or use our Services/Products. You agree that PHT may update this Privacy Policy at any time by posting the amended version on our website and associated application program interface or mobile applications (the “Site”) or sending the latest Privacy Policy to you via email. Your use or continued use of any Services/Products after such amendment shall be deemed as your acceptance and agreement to the same. **PLEASE REFER TO** [**PRIVACY POLICY**](https://docsend.com/view/t4stbinqxcp4efb5) **AND READ TERMS CAREFULLY** --- # 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.apacx.io/legal-compliance/privacy-policies.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.