AI书签墙隐私政策
生效日期：2026-11-02 适用范围：AI书签墙 Chrome 扩展（下称「本扩展」）。本政策说明本扩展处理哪些数据、这些数据去了哪里，以及你如何控制它们。 开发者：Hango Liang
一、简要说明
- 本扩展没有开发者服务器。开发者无法看到你的书签、设置或对话内容。
- 本扩展没有账号，不包含分析统计、广告或追踪代码。
- 只有在你使用 AI 整理功能时，才会向你自己配置的模型服务发送请求。
- 设置保存在你的浏览器本机。即将上线的同步功能会把部分设置（包括 API Key，可关闭）保存到你的 Chrome 账号中；撤销记录只保存在本机。
二、本扩展处理的数据
| 数据 | 内容 | 用途 | 保存位置 |
|---|---|---|---|
| 书签 | 标题、网址、文件夹结构 | 在书签墙中展示和搜索，计算待整理数量 | 直接读取 Chrome 书签；除撤销记录外不另存副本 |
| AI 服务设置 | 服务类型、Base URL、模型名、API Key | 连接你配置的模型服务 | 本机；即将上线后可同步（见第四节） |
| 排除与折叠设置 | 文件夹的内部编号、路径名称，以及由网址计算出的哈希摘要（不含网址明文） | 确定哪些文件夹不发送给 AI，哪些文件夹折叠显示 | 仅本机，不同步 |
| 撤销记录 | 每次整理中被移动书签的内部编号、完整网址、原位置与新位置，以及本次新建的文件夹 | 撤销整理 | 仅本机，不同步；只保留最近 10 次 |
| 显示设置 | 深色或浅色主题，待整理数量徽标是否显示 | 界面显示 | 本机；即将上线后可同步（见第四节） |
| 对话内容 | 你在对话面板输入的文字、AI 的回复与整理建议 | 与 AI 对话，生成整理建议 | 仅保存在书签墙页面的内存中；点「新对话」、关闭或刷新页面后清除 |
三、数据去了哪里
1. 你配置的模型服务（仅在使用 AI 时）
当你点击「一键整理」，或在对话面板中发送消息时，本扩展会向你配置的 Base URL 发送请求。请求只包含：
- 待整理书签的内部编号、标题、网址的域名（不含路径和查询参数），以及所在文件夹的内部编号与路径；
- 未被排除的文件夹的名称与路径（供模型选择目标文件夹）；
- 当前尚未应用的整理建议（已去除完整网址）；
- 最近几轮对话的文字；
- 你在对话框中输入的文字，原样发送。
若该服务需要，请求还会携带你填写的 API Key，用于向该服务证明身份。
以下内容不会发送：完整网址、书签的添加时间，以及你排除的文件夹中的书签和文件夹结构。
请注意：
- 书签标题是你保存时的文字。若标题本身包含网址或其他信息，它会按原样发送。
- 对话框中输入的内容会原样发送，请不要输入密码等敏感信息。
- 模型服务由你选择。它如何保存和使用这些数据，适用该服务提供方的隐私政策。
- 若 Base URL 指向本机（例如本机运行的 Ollama），请求不会离开你的电脑；若指向其他地址，请求会发往该地址。
2. 不发送给开发者或其他第三方
本扩展不向开发者或任何分析、广告服务发送数据。站点图标由 Chrome 自带的图标接口提供，本扩展不会自行请求这些网站的图标。
四、设置同步（即将上线）
【即将上线】
我们正在开发设置同步功能，让你登录同一个 Chrome
账号的设备之间共享部分设置，通过 Chrome 的
chrome.storage.sync 完成。上线后同步的内容包括：
- 服务类型、Base URL、模型名；
- API Key（默认同步，可关闭，见下）；
- 显示设置（深色或浅色主题，待整理数量徽标是否显示）。
API Key 同步开关：设置中有「在 Chrome 账号间同步 API Key」开关，默认开启。关闭后，API Key 只保存在本机，并会从同步数据中删除。
请注意：
- 开启该开关时，API Key 会保存在你的 Google 账号的 Chrome 同步数据中，并出现在登录同一账号的其他设备上。若不希望 Key 离开本机，请关闭该开关。
- Base URL 与文件夹路径名称可能包含你的私人信息，同步时也会一并保存。
- 同步由 Chrome 完成，数据受 Chrome 同步的相关规则与 Google 隐私政策约束。
不同步的内容：
- 排除文件夹设置。每台电脑各自确认；在另一台电脑上，首次使用 AI 前需要重新确认排除范围，确认前不会发起任何 AI 请求。
- 折叠区域设置，暂时只保存在本机。
- 撤销记录及其他本机状态。
五、数据安全
- 需要 API Key 的服务，只允许使用 HTTPS
地址，或本机地址（
localhost、127.0.0.1、[::1]）。 - Ollama 可以使用 HTTP。若地址不是本机，设置中会显示「该连接未加密」。
- 本扩展不额外加密本机保存的数据。这些数据与浏览器中的其他本地数据一样，受操作系统和浏览器账户的保护。请勿在与他人共用的电脑上保存 API Key。开启同步后，同步数据由 Chrome 保存，本扩展不另行加密。
- 本扩展只通过 Chrome 的书签接口读写书签，不读取或修改 Chrome 配置目录中的书签文件。
六、你的控制与删除
- 修改或清空配置：在设置中修改服务地址、模型名，或清空 API Key 字段。
- API Key 同步开关：关闭「在 Chrome 账号间同步 API Key」后，同步数据中的 Key 会被删除，Key 只保存在本机。
- 撤销记录：只保留最近 10 次，较早的记录会自动删除。
- 卸载：在 Chrome 的扩展管理页面移除本扩展后，Chrome 会删除本扩展保存在本机的数据。如果你开启过 API Key 同步，建议卸载前先在设置中关闭该开关，Key 会从同步数据中删除。
- 书签：书签始终保存在你的 Chrome 中，可通过 Chrome 书签管理器直接管理。除撤销记录外，本扩展不保存书签副本。
七、有限使用声明
本扩展对用户数据的使用遵守 Chrome Web Store 的《有限使用》（Limited Use）政策。我们只将用户数据用于提供本扩展的单一用途：在一个页面中浏览和搜索书签，并在你确认后整理书签。我们不将数据用于个性化广告，不出售给第三方，也不用于信用评估或贷款。
八、政策变更
如本政策有变更，我们会更新本页顶部的生效日期。若变更涉及新的数据处理方式，我们会在发布相应版本前更新本页。
九、联系我们
如对本政策有任何疑问，请联系：liang.hanguang93@gmail.com
AI Bookmark Wall Privacy Policy
Effective date: 2026-11-02 Scope: The AI Bookmark Wall Chrome extension (the "Extension"). This policy explains what data the Extension handles, where that data goes, and how you can control it. Developer: Hango Liang
1. Summary
- The Extension has no developer server. The developer cannot see your bookmarks, settings or conversations.
- The Extension has no account, and contains no analytics, advertising or tracking code.
- Data is sent only when you use the AI features, and only to the model service you configure yourself.
- Settings are stored on your device. The upcoming settings-sync feature will also save some settings, including the API key (which you can turn off), to your Chrome account. Undo history stays on your device.
2. Data the Extension handles
| Data | Contents | Purpose | Where it is stored |
|---|---|---|---|
| Bookmarks | Titles, URLs, folder structure | Show and search bookmarks on the wall; count items waiting to be organized | Read directly from Chrome's bookmarks; apart from undo history, no separate copy is kept |
| AI service settings | Service type, base URL, model name, API key | Connect to the model service you configured | On your device; sync planned, see Section 4 |
| Exclusion and collapsed-folder settings | Internal folder IDs, folder path labels, and hash digests computed from URLs (no plain-text URLs) | Decide which folders are never sent to the AI, and which folders are collapsed | On this device only; not synced |
| Undo history | For each change: internal bookmark IDs, the full URL, original and new positions, and folders created by the change | Undo a change | On this device only, not synced; only the last 10 changes are kept |
| Display settings | Light or dark theme; whether the pending-count badge is shown | Display | On your device; sync planned, see Section 4 |
| Conversation content | Text you type in the panel, the AI's replies and suggestions | Chat with the AI and generate suggestions | Kept only in memory on the wall page; cleared when you click "New conversation", close the page or reload it |
3. Where the data goes
3.1 The model service you configure (only when you use the AI features)
When you click "one-click tidy-up", or send a message in the panel, the Extension sends a request to the base URL you configured. The request contains only:
- For the bookmarks being organized: internal ID, title, the domain of the URL (without path or query string), and the internal ID and path of the folder they are in;
- The names and paths of folders that are not excluded (so the model can choose a target folder);
- Current suggestions that have not been applied yet (full URLs removed);
- The text of the most recent conversation turns;
- The text you type in the panel, sent exactly as you typed it.
If the service requires one, each request also carries the API key you entered, so the service can verify your access.
Not sent: full URLs, the date a bookmark was added, and bookmarks or folder structure inside folders you have excluded.
Please note:
- A bookmark title is the text you saved. If a title itself contains a URL or other information, it is sent as is.
- Text you type in the panel is sent exactly as typed. Do not type passwords or other sensitive information there.
- You choose the model service. How it stores and uses the data is governed by that provider's privacy policy.
- If the base URL points to your own machine (for example, Ollama running locally), requests do not leave your computer. If it points elsewhere, requests are sent to that address.
3.2 Nothing is sent to the developer or other third parties
The Extension does not send data to the developer or to any analytics or advertising service. Site icons are provided by Chrome's built-in icon service; the Extension does not itself request icons from those websites.
4. Settings sync (coming soon)
[Coming soon] We are developing a settings-sync
feature, so that some settings are shared across the devices signed in
to the same Chrome account. It uses Chrome's
chrome.storage.sync. Once released, the synced items will
be:
- service type, base URL and model name;
- the API key (on by default; can be turned off, see below);
- display settings (light or dark theme, and whether the pending-count badge is shown).
API key sync switch: Settings include a switch, "Sync API key across Chrome accounts", which is on by default. When it is off, the API key is stored only on your device and is removed from synced data.
Please note:
- With the switch on, the API key is stored in the Chrome sync data of your Google account and appears on other devices signed in to that account. If you do not want the key to leave this device, turn the switch off.
- Your base URL and folder path names may contain private information, and they are saved in the sync data too.
- Sync is performed by Chrome and is subject to Chrome's sync rules and Google's privacy policy.
Not synced:
- Excluded-folder settings. Each computer is confirmed separately. On another computer, the exclusion list must be confirmed again before the first AI request; no AI request is sent before that.
- Collapsed-folder settings, which stay on this device for now.
- Undo history and other device-local state.
5. Security
- A service that requires an API key must use an HTTPS address, or a
local address (
localhost,127.0.0.1,[::1]). - Ollama may use HTTP. If its address is not local, the settings page shows "This connection is not encrypted".
- The Extension does not add encryption to data stored on your device. That data is protected in the same way as other local browser data, by your operating system and browser account. Do not store an API key on a computer shared with others. With sync on, the synced data is kept by Chrome, and the Extension does not add encryption to it.
- The Extension reads and changes bookmarks only through Chrome's bookmarks interface. It does not read or modify the bookmark files in Chrome's profile directory.
6. Your controls and deletion
- Change or clear settings: edit the service address or model name in settings, or clear the API key field.
- API key sync switch: turning off "Sync API key across Chrome accounts" removes the key from synced data; it then stays only on this device.
- Undo history: only the last 10 changes are kept; older records are deleted automatically.
- Uninstall: removing the Extension from Chrome's extensions page causes Chrome to delete the data the Extension stored on your device. If you have turned on API key sync, turn the switch off in settings before uninstalling; the key is then removed from synced data.
- Bookmarks: bookmarks always remain in your Chrome and can be managed in Chrome's bookmark manager. Apart from undo history, the Extension does not keep a copy of them.
7. Limited Use statement
The Extension's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use user data only to provide the Extension's single purpose: browsing and searching bookmarks on one page, and organizing bookmarks after you confirm. We do not use data for personalized advertising, we do not sell it to third parties, and we do not use it to determine creditworthiness or for lending.
8. Changes to this policy
If this policy changes, we will update the effective date at the top of this page. If a change introduces a new way of handling data, we will update this page before releasing the version that includes it.
9. Contact
If you have any questions about this policy, please contact: liang.hanguang93@gmail.com