> For the complete documentation index, see [llms.txt](https://safew-1.gitbook.io/safew-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safew-1.gitbook.io/safew-docs/safew.md). # SafeW [SafeW](https://safew-zhcn.com/) 是一款专注于安全加密通讯的即时聊天应用，面向个人用户、企业团队及高隐私需求场景打造。SafeW支持私有化部署，并基于先进的端到端加密技术，确保消息、文件与通话内容在传输过程中全程加密，有效保护用户数据与沟通隐私。SafeW 同时支持 Windows、macOS、Android 与 iOS 多平台同步，为用户提供安全、稳定、高效的全球通讯体验。\ keyword: [SafeW](https://safew-zhcn.com/)\ Website:\ \ \ \ \ \ \ \ --- # 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://safew-1.gitbook.io/safew-docs/safew.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.