> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v27-zh-cn/parallels-desktop-for-mac-27-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows/bao-hu-nin-de-shu-ju.md).

# 保护您的数据

您的 Mac 上可能会有非常重要的文档、照片等。在 Mac 上运行 Windows 时，请务必保护您的数据免遭病毒入侵，并防止发生未经授权使用的行为。有关具体操作，请阅读本部分。


---

# 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.parallels.com/landing/pdfm-ug/v27-zh-cn/parallels-desktop-for-mac-27-yong-hu-zhi-nan/zai-mac-shang-shi-yong-windows/bao-hu-nin-de-shu-ju.md?ask=<question>&goal=<user_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.