> For the complete documentation index, see [llms.txt](https://puregamma-ai.gitbook.io/puregamma-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://puregamma-ai.gitbook.io/puregamma-ai/zhang-hu-yu-an-quan.md).

# 账户与安全

## 账户信息

「账户」页展示:姓名、邮箱、套餐、Credits 余额。邮箱同时是登录凭证与通知渠道,请保持可用。

## 密码管理

* **修改密码**:已知当前密码 → 账户页直接修改。
* **忘记密码**:登录页「忘记密码」→ 邮件重置链接(一次性、24 小时有效)。
* **Google 注册的用户**:初始没有密码,可在账户页「设置密码」后直接获得邮箱登录能力。

## 安全机制(透明化说明)

* 密码 scrypt 哈希存储,会话 JWT 短期有效 + 版本号吊销。
* 登录/注册有频率限制(15 分钟窗口);敏感写操作有 CSRF Origin 校验。
* 会话过期后前端自动跳登录页,登录后回到原页面。
* iMessage 绑定必须经 6 位验证码确认(见 通知与 iMessage)。

## 隐私

* 会话 Cookie 为 HttpOnly,前端脚本不可读;API 使用 Bearer Token(移动端存于系统安全存储:iOS Keychain / Android Keystore)。
* 组合连接凭证服务端加密存储,断开即删除。
* 语音与转写调用第三方服务,密钥只在服务端。

## 注销账户

账户页底部可发起注销(需输入邮箱确认)。注销将**不可逆地**删除:

* 账户与全部会话
* Agent 对话、秘书记忆与消息
* 报告、组合连接与快照
* 通知偏好与推送设备
* Stripe 客户关联(订阅会先取消)

注销前建议导出需要保留的报告。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://puregamma-ai.gitbook.io/puregamma-ai/zhang-hu-yu-an-quan.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.