Brevess Privacy Policy / 隐私政策

Effective / 生效：2026-08-03 · Microsoft Edge extension

Brevess helps users read and analyze scientific article pages in Microsoft Edge. It provides local article navigation, abbreviation extraction, rule-based and manual highlighting, Figure/Panel organization, optional model-assisted analysis, full-text Q&A, and local article workspaces.

Brevess 用于在 Microsoft Edge 中阅读和分析科研论文网页，提供本地论文导航、缩写提取、正则与手动高亮、Figure/Panel 整理、可选的模型辅助分析、全文问答及本地论文工作区。

1. Data handled / 处理的数据

Current article page / 当前论文网页：URL, title, DOI when available, headings, text, captions, Figure images or image URLs, and page structure. Extraction starts only after the user activates Brevess for the current tab; Brevess does not continuously monitor browsing. 包括网址、标题、DOI、标题层级、正文、图注、Figure 图片或地址及页面结构；仅在用户激活当前标签页后提取。
User-created content / 用户内容：analysis modes, category rules, highlights, notes, questions, chat history, Panel follow-ups, feedback examples, and export preferences. 包括分析模式、规则、高亮、备注、问题、问答历史、Panel 追问和导出偏好。
Configuration and authentication / 配置与鉴权：provider settings and API keys entered by the user. Keys remain in local extension storage by default; when portable backup is enabled, they are also written only to the authenticated ciphertext files described below. They are sent only to the endpoint selected by the user for authentication. Brevess has no developer server that receives these keys. API Key 默认保存在扩展本地存储；启用便携备份时也只写入下述认证密文文件，并且只发往用户选择的服务地址。
Local usage records / 本地使用记录：per-article model, feature and token totals, task state, cache metadata and diagnostic errors. They stay on the user's device unless exported. 按论文、功能和模型统计的 Token、任务状态、缓存和诊断信息默认留在本机。
Optional local integrations / 可选本地集成：a user-selected folder, loopback Zotero Connector, and separately installed Windows Local Codex bridge.

2. Storage and retention / 存储与保留

Settings and article workspaces are stored locally using Microsoft Edge extension storage, IndexedDB, and—only when selected by the user—the local folder chosen through the File System Access API. Brevess does not upload a copy to a developer-operated cloud service.

设置和论文工作区保存在 Edge 扩展本地存储、IndexedDB 和用户主动选择的本地文件夹中，不会上传至开发者运营的云端。数据保留到用户删除工作区、清除扩展数据、删除目录文件或卸载扩展为止。明确导出的文件可能在卸载后继续存在；可选桥接数据位于 %LOCALAPPDATA%\BrevessCodexBridge，会保留到用户自行删除。

If the user enables portable configuration backup, Brevess writes model/API settings (including API credentials) and the global abbreviation table to the primary file Brevess/settings/portable-config.enc.json. After a successful update, it retains at most one rolling encrypted previous copy at Brevess/backups/settings/portable-config.enc.previous.json. Both files contain only AES-GCM authenticated ciphertext. Their key is derived from the user's backup password with PBKDF2. The password is never written to the folder or included in an export. The derived key is cached only on the local device and can be cleared with Forget backup unlock / 忘记备份解锁. A forgotten password makes the encrypted copies unrecoverable. Normal article exports, diagnostics, logs and token reports continue to exclude API credentials.

用户启用便携配置备份后，模型/API 设置（包括 API 凭据）和全局缩略词表会以 AES-GCM 认证密文写入所选目录的主文件 Brevess/settings/portable-config.enc.json；成功更新后，最多保留一个同样加密的滚动旧版副本 Brevess/backups/settings/portable-config.enc.previous.json。两个文件都只含认证密文；密钥由 PBKDF2 从备份口令派生。口令不写入目录或任何导出文件，派生密钥仅缓存在本机并可用“忘记备份解锁”清除。忘记口令后无法恢复密文；普通论文导出、诊断、日志和 Token 报告仍排除 API 凭据。

3. Data transmission and third parties / 数据传输与第三方

Model-assisted features remain disabled until the user configures a provider and grants the in-extension permission to send article content. Depending on the task, Brevess may send necessary article excerpts, captions, compressed Figure images, questions and limited conversation context directly to the provider or compatible endpoint selected by the user. Provider availability, retention, billing and processing are governed by that provider's terms and privacy policy.

只有在用户配置模型并勾选“正文发送许可”后，Brevess 才会把任务所需的论文片段、图注、压缩 Figure、问题和有限对话上下文直接发送给用户选择的服务。可选路由包括 OpenAI、Anthropic、Google Gemini、DeepSeek、用户配置的 OpenAI-compatible 服务或本机 Codex 桥。远程自定义地址必须使用 HTTPS；HTTP 仅允许用户明确配置的 localhost 或 127.0.0.1。

The Local Codex bridge is an optional Windows companion. It exchanges messages only with approved extension IDs on the same device and uses the user's extension-specific Codex sign-in. Codex processing is subject to the terms applicable to the user's account.

4. User controls / 用户控制

Local navigation, abbreviations, regex highlighting, manual annotations and workspaces can be used without enabling an external model. 本地功能无需启用外部模型。
Users can revoke model sharing by clearing Permission to send article text / 正文发送许可 and saving settings.
Users can edit or remove provider profiles; delete workspaces, highlights or chats; export data; clear extension storage; and avoid optional integrations.

5. No sale, advertising, or developer analytics / 不出售、无广告、无开发者遥测

Brevess does not sell, license, broker, or use user data for advertising, creditworthiness, or unrelated profiling. It contains no advertising SDK and does not send product analytics or browsing telemetry to the developer.

6. Security / 安全

Remote model requests use HTTPS except explicit loopback services on the user's device. API keys are stored locally, masked after saving, and excluded from normal article exports and token reports. Users should protect their Edge profile, credentials, exported files and selected folders.

7. Sensitive information and intended use / 敏感信息与用途

Brevess is a research reading aid, not a medical device and not a substitute for clinical, legal or professional advice. Users should not submit private, identifiable patient data or confidential information to third-party models unless authorized and the provider is appropriate for that use.

Brevess 是科研阅读辅助工具，不是医疗器械，不能替代临床、法律或其他专业判断。未经授权，不应向第三方模型提交可识别患者身份的数据或其他机密信息。

8. Children / 儿童

Brevess is intended for researchers, students and professional readers. It is not directed to children under 13 and does not knowingly collect children's personal information.

9. Changes / 政策变更

Material changes will be published at this URL with a new effective date and, when appropriate, noted in release notes. 重大变更会在本页面更新生效日期，并在适当情况下写入版本说明。