1. 扩展处理哪些信息
Lectiophile 帮助你在授权的网站上划线、添加评论，并将内容整理到本地 Markdown 阅读笔记。为实现这些功能，扩展可能处理：
- 网页内容：你选中的文字、周围段落、章节标题、页面标题与网址，以及由你输入的评论和划线颜色所代表的标签。
- 本地笔记信息：你授权的文件夹中的 Markdown 笔记、文件名、笔记标题、元数据和章节标题，用于寻找合适的保存位置与更新笔记、看板。
- 聊天页面上下文：在支持的 AI 聊天网站上首次为某段对话匹配阅读笔记时，可能读取对话开头的若干轮消息；此数量可在设置中调整为 0。
默认只在你添加并授权的网站白名单内运行；如果你主动切换为「黑名单」或「所有网站」模式并授予相应权限，扩展的适用范围也会随之扩大。
2. 保存在本机的信息
- 浏览器本地存储（
chrome.storage.local）：Jev API Key、网站规则、界面和保存设置、模板及元数据配置、笔记索引、划线记录、尚未完成的保存任务和笔记关联等。
- 浏览器 IndexedDB：你通过 Chrome 文件夹选择器授予的文件夹句柄，用于再次访问已经选定的本地目录；Chrome 可能要求重新授权。
- 你选定的磁盘文件夹：划线引用、评论、阅读笔记与可选的 Dataview 看板以 Markdown 文件形式保存在该目录（或你另外选择的看板目录）中。
- 手动备份：你主动导出的设置备份保存在你选择的位置，并由你自行管理。
这些信息不上传至开发者的服务器。本地笔记文件与手动导出的备份不会因卸载扩展而自动删除。
3. 什么时候向第三方发送信息
可选的 Jev 服务：当你保存划线并使用 Jev 辅助判断笔记或章节时，扩展通过 HTTPS 直接请求 TypeSafe AI（Jev） 的 api.typesafe.ai 接口。根据本次归类任务，发送的内容可能包括：
- 划线文字、你的评论、周围段落、划线用途、来源标题或章节信息；
- 为了匹配笔记而使用的页面标题、网页网址，以及候选笔记的名称、标题和候选章节名称；
- 在 AI 聊天网站首次匹配笔记时，根据设置读取的对话开头消息（默认前 2 轮，可改为 0）；
- 你的 Jev API Key，通过请求的 Authorization 标头进行身份验证。
Jev 在给定候选项之间进行判断，不会接收整个 Obsidian 笔记库或完整笔记正文用于归类。请求中的网页文字、评论和聊天消息可能包含个人或敏感内容，请在使用前自行确认。发送至 TypeSafe AI 的数据受该服务提供商的隐私与保留政策约束；开发者无法代为删除其服务器上可能保留的数据。
如果没有填写 Jev Key，或者 Jev 服务不可用，仍可通过手动选择笔记及章节保存划线，而无需调用 Jev。设置页的「测试连接」会发送内置示例文本以检验接口。
4. 网站及文件访问权限
storage：保存扩展本地设置、任务状态和索引。scripting、activeTab：在你授权的网站上启用划线及评论界面、处理当前页面交互。https://api.typesafe.ai/*：在你配置并使用 Jev 时访问其 API。- 可选网站权限：为白名单网站逐一授权，或在你选择更宽的运行模式时请求访问所有网站；可以通过扩展设置或 Chrome 的扩展权限界面调整。
- 本地文件夹访问：只有在你主动选择文件夹并授予文件读写权限后，才会读取、创建或修改该文件夹内的文件。
5. 数据使用、分享与安全
Lectiophile 没有开发者运营的同步或分析服务器，不植入广告或第三方跟踪工具，不出售用户数据，也不会将用户数据用于与阅读批注和笔记归类无关的用途。除实现你启用的 Jev 功能所必需的上述传输外，扩展不会主动向第三方发送你的笔记内容。Jev API 请求使用 HTTPS；API Key 保存在浏览器本地，并在请求时用于身份验证。
我们遵守 Chrome Web Store 用户数据政策及其 Limited Use 要求。使用从 Google API 获取的信息时，也将遵守该政策，包括 Limited Use 要求。
6. 你的选择与数据删除
- 可以移除 Jev Key，以停止后续的 Jev 请求；也可以将聊天上下文轮数设为 0。
- 可以修改网站白名单、切换模式、撤销网站或文件夹访问权限。
- 可以从扩展中调整或清理已保存记录、待处理任务和设置；也可以卸载扩展以删除其浏览器本地数据。
- 保存在 Obsidian 文件夹中的 Markdown 文件，以及你导出的备份，需要自行在相应位置管理和删除。
- 如需查询 TypeSafe AI 对已收到请求数据的处理、保留或删除方式，请联系该服务提供商。
7. 政策更新与联系
如果 Lectiophile 的数据处理方式改变，本页面会同步更新并调整生效日期；必要时也会在扩展界面中提示。关于隐私政策的问题，请联系 me@hyahui.com。
1. Information the extension processes
Lectiophile lets you highlight and comment on web pages and organize those annotations into local Markdown reading notes. To provide these features, it may process:
- Web page data: selected passages, surrounding paragraphs, section headings, page titles and URLs, plus comments you type and labels associated with highlight colors.
- Local note data: Markdown notes within the folder you authorize, including file names, note titles, metadata and headings, to determine where to save annotations and update your notes or dashboard.
- Conversation context: on supported AI chat websites, the opening messages of a conversation may be read the first time that conversation is matched to a note. You can set the number of rounds to zero.
By default, Lectiophile runs only on websites you explicitly add to your allowlist and authorize. If you choose blocklist mode or all-sites mode and grant broader permissions, its operating scope expands accordingly.
2. Information stored locally
- Chrome local storage (
chrome.storage.local): Jev API key, website rules, interface and saving preferences, templates and metadata profiles, note indexes, annotation records, pending jobs and note associations.
- Browser IndexedDB: handles for folders you select through Chrome's file picker; Chrome may ask you to grant access again.
- Your chosen local folder: highlighted quotes, comments, reading notes and an optional Dataview dashboard are written as Markdown files in the selected folder (or in another dashboard folder that you select).
- Manual backups: configuration exports you initiate are saved wherever you choose and remain under your control.
This information is not uploaded to a server operated by the developer. Uninstalling the extension does not automatically delete your Markdown files or manually exported backups.
3. Information shared with a third party
Optional Jev service: when you use Jev to choose a note or section for an annotation, the extension makes a direct HTTPS request to TypeSafe AI (Jev) at api.typesafe.ai. Depending on the classification task, that request may contain:
- The highlighted passage, your comment, surrounding paragraph, highlight purpose, source title or page section;
- The page title and URL, and the names, titles or section headings of candidate notes when matching notes;
- On supported AI chat websites, opening conversation messages when a conversation is first matched to a note (two rounds by default; configurable to zero);
- Your Jev API key in the Authorization header for authentication.
Jev selects among supplied choices; the extension does not send the entire Obsidian vault or complete note bodies for classification. The content of selected text, comments or chat messages may be personal or sensitive. Information sent to TypeSafe AI is governed by that provider's own privacy and retention practices; the extension developer cannot delete data that the provider may retain.
Without a Jev key, or if Jev is unavailable, you can still save highlights by choosing a note and section manually. The “Test connection” button sends built-in sample text to test the API.
4. Website and file permissions
storage: stores local preferences, job state and indexes.scripting and activeTab: provide highlighting and commenting on authorized sites and interact with the active page.https://api.typesafe.ai/*: connects to Jev when you configure and use that feature.- Optional website access: granted site by site for your allowlist, or more broadly if you explicitly enable blocklist or all-sites mode; you can change permissions in Chrome.
- Local file access: requires you to select a folder and grant read/write access before the extension reads, creates or changes files in that folder.
5. Use, disclosure and security
Lectiophile has no developer-operated sync or analytics backend, contains no ads or third-party tracking tools, does not sell user data and does not use it for purposes unrelated to reading annotations and note organization. Apart from the optional Jev transfer described above, it does not proactively send note content to third parties. Jev requests use HTTPS. The API key is stored locally in your browser and used to authenticate requests.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Lectiophile's use of user data likewise follows the Chrome Web Store Limited Use restrictions.
6. Your choices and deletion
- Remove your Jev key to stop future Jev requests, or set conversation rounds to zero.
- Manage your allowlist, site mode, and website or local-folder permissions.
- Manage locally saved records, pending jobs and settings in the extension, or uninstall it to remove extension-owned browser data.
- Delete Markdown notes and exported backups yourself in their respective local folders; uninstalling does not remove them.
- For questions about retention or deletion of information already received by TypeSafe AI, contact that provider.
7. Updates and contact
If Lectiophile's data practices change, this page and its effective date will be updated, with in-extension notice where required. For privacy-related questions, contact me@hyahui.com.