> For the complete documentation index, see [llms.txt](https://ray-evolv.gitbook.io/ray_evolv-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ray-evolv.gitbook.io/ray_evolv-docs/help/privacy.md).

# 数据与隐私边界

理解本地保存、远程模型、公开材料与设备同步分别涉及什么。

## 本地优先意味着什么

账本、研究、知识和会话主要保存在本机工作区。手动记账不是连接交易平台下单，也没有新增 Evolv 用户注册登录流程。

使用远程 AI 服务时，任务需要的输入会发送给你配置的服务。持仓分析会使用相关份额、成本、交易、计划等业务背景；不能把“本地优先”解释为资料永不离开电脑。

## 三种“保存”

| 内容   | 保存用途               |
| ---- | ------------------ |
| 业务记录 | 账户、资金、交易和计划等真实业务资料 |
| 知识   | 有来源和适用范围、可再次使用的认识  |
| 个人记忆 | 经确认的协作偏好与长期关注      |

公共知识不表示发布到公共网站。通过报告补料提交公开材料，是声明材料可按相应流程处理；不要混入私人账单、密码或受限正文。

## 图片、视觉与会话

主动添加的图片是聊天材料，可能随会话附件保留。按任务临时截取画面与上传图片有不同处理方式。无记忆会话不读取或写入长期画像，不等于完全没有本地消息和任务记录。

视觉权限分别控制 Evolv 窗口和鼠标所在显示器。开启桌面陪伴不会自动开启查看画面，也不代表有操作其他软件的权限。

## 同步与数据

同步使用自己的网盘目录，同步内容是账本、报告、知识、记忆及附件等业务数据；模型与搜索服务的凭据和连接配置不参与正常同步。Evolv 不要求注册软件登录账号，也不提供集中托管账本的自营云服务；启用同步后，业务资料会保存在你选择的网盘服务中。

不要把密钥或密码写进聊天、备注、知识正文或附件。这些普通内容可能参与模型调用或同步，不能因为配置字段排除了密钥，就假定任意正文中的密钥也会被自动排除。

网盘中的同步内容不额外加密，不要公开分享同步目录。接入方式见[多设备同步](/ray_evolv-docs/help/sync.md)。请保管好自己的数据备份、网盘凭据和应用密码。

***

返回[配置与帮助](/ray_evolv-docs/help.md) · [认识 Evolv](/ray_evolv-docs/home.md)


---

# 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://ray-evolv.gitbook.io/ray_evolv-docs/help/privacy.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.