最后更新日期：2026 年 6 月 5 日
本隐私政策说明了 AI Helper 浏览器扩展（以下简称"本扩展"）如何访问、处理和存储用户数据。我们承诺对用户透明，本扩展的源代码完全公开，欢迎审查。
本扩展通过 Chrome webRequest API 和页面脚本拦截技术（猴子补丁 window.fetch 和 XMLHttpRequest）捕获网络请求信息，包括：
用途：用于在扩展面板中向用户展示网络请求详情，以及作为 AI 对话的页面上下文提供给用户配置的 LLM API。
存储位置：浏览器内存（Service Worker 的 Map 缓冲区），每个标签页最多保留 100 条记录，标签页关闭时自动清除。
本扩展通过 Chrome cookies API 读取用户当前浏览标签页域名下的 Cookie 信息。
用途：用于在扩展面板中统计展示 Cookie 数量，帮助用户了解当前页面的 Cookie 使用情况。
存储位置：浏览器内存，不持久化。
当用户使用 AI 对话功能时，本扩展可采集当前页面的以下内容：
用途：为 AI 对话提供页面上下文，使 AI 能够理解和分析当前页面。
存储位置：浏览器内存，对话结束后清除。认证令牌在展示前经过掩码处理（短令牌全掩码，长令牌仅保留首尾少量字符）。
用户主动配置以下信息时，数据存储在浏览器本地：
chrome.storage.local用途：扩展功能运行所必需。
存储位置：chrome.storage.local（Chrome 扩展本地存储）。
本扩展的核心功能是将用户对话和页面上下文发送给用户自己配置的 LLM API 服务。发送的数据包括：
数据接收方：用户自行配置的 API 服务商（由用户设置的 API Base URL 决定）。AI Helper 开发者不参与、不中转、无法访问此通信过程。
隐私责任：数据发送到哪个 API 服务商完全由用户自己决定和控制。用户在配置 API 服务时应自行查阅该服务商的隐私政策。
本扩展不向开发者发送任何数据。不存在遥测、崩溃报告、使用统计或任何形式的后台数据回传。开发者不运营任何接收用户数据的服务器。
| 存储位置 | 存储内容 |
|---|---|
| 浏览器内存 | 网络请求缓冲区、页面上下文采集数据（标签页关闭/扩展休眠时清除） |
chrome.storage.local | API 配置、对话会话列表、扩展设置、自定义请求头、Git 项目配置、技能配置 |
| IndexedDB | 对话文件缓存（源码文件、记忆文件、工作产物、用户上传附件） |
用户对存储数据的控制：用户可以随时在扩展中删除对话会话、清除文件缓存。卸载扩展将同时清除 chrome.storage.local 和 IndexedDB 中的所有数据。
chrome.storage.local 中。用户不应在不可信的计算机或共享环境中使用本扩展。本扩展在 manifest.json 中声明以下权限，各权限的用途如下：
| 权限 | 用途 |
|---|---|
sidePanel | 在 Chrome 侧边栏中显示扩展面板 |
webRequest | 监听网络请求以实时捕获和展示请求信息 |
declarativeNetRequest | 根据用户配置向网络请求注入自定义 HTTP 头 |
storage | 保存用户配置和对话历史 |
activeTab | 获取当前活跃标签页信息 |
cookies | 读取当前标签页域名的 Cookie 信息以供展示 |
tabs | 管理标签页以在页面切换时正确注入脚本 |
scripting | 向页面动态注入分析脚本以采集页面上下文 |
host_permissions | 在用户访问的所有网站上运行内容脚本（排除飞书域名） |
本扩展不面向 13 岁以下的儿童。我们不会故意收集儿童的个人信息。
我们可能会不时更新本隐私政策。更新后的政策将在本页面发布，并在扩展的 Chrome Web Store 列表页中更新链接。
如对本隐私政策有任何疑问，请通过以下方式联系：
Last Updated: June 5, 2026
This privacy policy describes how the AI Helper browser extension ("the Extension") accesses, processes, and stores user data. We are committed to transparency — the Extension's source code is fully public and open to inspection.
The Extension captures network request information via the Chrome webRequest API and page script interception (monkey-patching window.fetch and XMLHttpRequest), including:
Purpose: Display network request details to users in the extension panel, and provide page context to the user-configured LLM API during AI conversations.
Storage: Browser memory (Service Worker Map buffer), up to 100 records per tab, automatically cleared when the tab is closed.
The Extension reads cookie information from the current tab's domain via the Chrome cookies API.
Purpose: Display cookie count statistics in the extension panel to help users understand cookie usage on the current page.
Storage: Browser memory only, not persisted.
When the user uses the AI conversation feature, the Extension may collect the following from the current page:
Purpose: Provide page context for AI conversations, enabling the AI to understand and analyze the current page.
Storage: Browser memory, cleared after the conversation ends. Authentication tokens are masked before display (short tokens fully masked, long tokens show only a few characters at the beginning and end).
When users manually configure the following, data is stored locally in the browser:
chrome.storage.localPurpose: Required for the Extension's functionality.
Storage: chrome.storage.local (Chrome extension local storage).
The core functionality of the Extension involves sending user conversations and page context to the LLM API service configured by the user. Data sent includes:
Data Recipient: The API service provider configured by the user (determined by the user's API Base URL setting). The AI Helper developer does not participate in, relay, or have access to this communication.
Privacy Responsibility: Which API service provider data is sent to is entirely determined and controlled by the user. Users should review the privacy policy of their chosen API provider when configuring the service.
The Extension does not send any data to the developer. There is no telemetry, crash reporting, usage statistics, or any form of background data transmission. The developer does not operate any server that receives user data.
| Storage Location | Stored Content |
|---|---|
| Browser Memory | Network request buffers, page context collection data (cleared when tab is closed or extension goes idle) |
chrome.storage.local | API configuration, conversation session list, extension settings, custom request headers, Git project configuration, skill configuration |
| IndexedDB | Conversation file cache (source files, memory files, work artifacts, user-uploaded attachments) |
User Control Over Stored Data: Users can delete conversation sessions and clear file caches at any time within the extension. Uninstalling the extension will clear all data in chrome.storage.local and IndexedDB.
chrome.storage.local. Users should not use the Extension on untrusted computers or in shared environments.The Extension declares the following permissions in its manifest.json, each serving the purposes described below:
| Permission | Purpose |
|---|---|
sidePanel | Display the extension panel in Chrome's side panel |
webRequest | Listen to network requests for real-time capture and display |
declarativeNetRequest | Inject custom HTTP headers into network requests per user configuration |
storage | Save user configuration and conversation history |
activeTab | Access information about the currently active tab |
cookies | Read cookie information for the current tab's domain for display |
tabs | Manage tabs to correctly inject scripts when tabs switch |
scripting | Dynamically inject analysis scripts into pages to collect page context |
host_permissions | Run content scripts on all websites visited by the user (excluding feishu.cn) |
The Extension is not directed at children under 13. We do not knowingly collect personal information from children.
We may update this privacy policy from time to time. Updated policies will be posted on this page, and the link will be updated in the Chrome Web Store listing.
If you have any questions about this privacy policy, please contact us via: