IMMERSIVE ASK · DATA & PRIVACY

隐私政策
Privacy Policy

生效及更新日期 / Effective and updated:

这份政策说明插件与官网如何处理阅读内容、设置、免费体验及使用统计。
How the extension and website handle reading content, settings, the free trial, and usage analytics.

沉浸式AI提问隐私政策

本政策适用于沉浸式AI提问(Immersive Ask)浏览器扩展、promptos.cn 官网及其免费体验服务,由本项目维护者负责。联系渠道为项目 GitHub Issues。

阅读内容与 AI 请求

在您发起解释或追问时,插件会处理选中的文字、附近的必要上下文、您的问题、相关会话记录及回答语言,用于生成和展示解释。

浏览器中保存的数据

扩展使用浏览器扩展存储保存语言、解释偏好、API Key、免费体验身份凭据及引导状态。设置和个人 API Key 使用浏览器的同步存储接口;如果您启用了浏览器同步,浏览器服务商可能将这些设置同步到您的其他设备。

解释缓存、追问记录、注释、原文片段和用于识别对应网页的地址或标识保存在扩展本地存储中,用于重用回答和恢复标注。网页访问权限也用于在页面及嵌入页面中显示划词入口、解释浮层和已有注释;统计事件不上传您访问网页的地址或阅读原文。

官网在浏览器本地保存您选择的界面语言。管理后台在管理员登录后使用会话 Cookie 验证登录状态;阅读本隐私政策无需登录。

免费体验、安全与用量记录

免费体验无需注册账号,但会使用随机安装标识、客户端标识及访问和刷新凭据。服务还会处理浏览器类型、系统平台、语言、时区、屏幕类别、扩展版本、安装来源和请求 IP 等信息,用于身份续期、发放额度、限流、防止重复领取及排查故障。

业务数据库使用带密钥的哈希保存 IP、安装标识或设备特征等部分信息。网关访问日志仍可能包含原始 IP、请求路径、时间、状态码和浏览器信息。随机标识和哈希可以关联同一客户端的记录,不代表完全匿名或无法关联。

使用统计

当前版本会自动发送使用统计,暂不提供独立的关闭开关。统计包括活跃、是否填写个人 API Key(只记录配置事件,不记录 Key 内容)、开源入口点击和支持入口点击,并关联客户端标识、时间、扩展版本与安装来源。服务也依据体验记录统计额度使用、耗尽和生成成本,用于了解功能使用情况、维护服务预算及改进阅读辅助功能。

统计事件不包含访问网页的地址、选中文本、问题、回答全文或个人 API Key 内容。使用个人 API Key 时,解释请求直接发送给 DeepSeek,但插件仍可能向本项目服务发送上述使用统计。停用或卸载扩展可停止扩展后续发起的请求,不会自动删除服务器已有记录。

第三方、分享与用途限制

本服务使用阿里云服务器托管。DeepSeek 接收生成回答所需的请求;如启用额外人机验证,验证页面可能使用 Cloudflare Turnstile,并由 Cloudflare 处理验证所需的网络及设备信息。浏览器同步、扩展商店和您主动访问的 GitHub、支持或支付服务依各自的隐私规则运作。

我们将用户数据的使用限制在提供、维护、安全保障和改进已披露的阅读辅助功能及相关服务用途,按照 Chrome Web Store 用户数据政策(包括 Limited Use 要求)限制数据使用与分享。我们不出售用户数据,不将其用于定向广告或数据经纪业务。除提供服务所需的上述处理外,仅在适用法律要求、安全事件处理或您明确请求支持等必要情形下处理或披露相关信息。

保存期限与安全

当前配置下,原始使用事件保存 30 天,安全日志及请求诊断保存 7 天,按日活跃及点击统计保存 90 天,并由定时清理任务删除到期记录。客户端、额度、请求成本及管理审计记录目前没有统一的自动到期删除时间,用于服务连续性、防刷和费用核对。网关日志及备份依运维配置保存,可能在业务记录清理后继续存在。

本地缓存和注释保留至您清理或浏览器移除对应数据。网络请求采用 HTTPS;个人 API Key 由浏览器扩展存储管理,我们不承诺其在您的设备上经过额外应用级加密。我们限制管理后台访问,并采取凭据校验等保护措施,但任何系统都不能保证绝对安全。

您的操作与联系渠道

您可以在插件设置中修改或删除个人 API Key、清理缓存与注释,也可以通过浏览器管理扩展的网页访问权限,或停用、卸载扩展。浏览器同步数据需要同时按照对应浏览器或账号的设置管理;清理本地缓存不会自动清除服务端数据。

如需了解、访问、更正或申请删除与您有关的服务端记录,请通过GitHub Issues 联系维护者。我们会核实请求与记录的关联,并在适用要求及必要的安全、费用记录保留范围内处理。Issues 为公开渠道,请勿发布 API Key、访问令牌、密码或敏感原文;涉及私密信息时,请先提出需要私下沟通。

本政策更新后会在本页标注日期。涉及数据处理方式的重要变化时,我们会通过官网或插件内说明告知。

Immersive Ask Privacy Policy

This policy covers the Immersive Ask browser extension, the promptos.cn website, and its free trial relay. The project maintainer is responsible for these services. Contact the maintainer through GitHub Issues.

Reading content and AI requests

When you request an explanation or ask a follow-up question, the extension processes selected text, necessary surrounding context, your question, relevant conversation history, and the response language to generate and display an answer.

Data stored by your browser

Extension storage holds language and explanation preferences, your API key, trial identity credentials, and onboarding state. Preferences and your personal API key use the browser's sync storage API. If browser sync is enabled, your browser provider may synchronize these settings to your other devices.

Cached explanations, follow-up conversations, annotations, original text excerpts, and page addresses or identifiers used to match annotations are kept in extension-local storage. Website access also supports selection controls, explanation overlays, and restoring annotations in pages and embedded frames. Analytics events do not upload the addresses of pages you read or their original text.

The website stores your selected interface language locally in your browser. The administration area uses a session cookie after an administrator logs in. No login is required to read this privacy policy.

Trial identities, security, and usage records

The trial does not require an account, but uses random installation and client identifiers plus access and refresh credentials. The service also processes browser type, platform, language, time zone, screen category, extension version, installation source, and request IP addresses for credentials, quotas, rate limits, abuse prevention, and troubleshooting.

The application database stores keyed hashes for some identifiers, IP information, and device characteristics. Gateway access logs may still contain raw IP addresses, request paths, times, status codes, and browser information. Random identifiers and hashes can link records to the same client; they do not make all records fully anonymous or unlinkable.

Usage analytics

The current version sends usage analytics automatically and does not provide a separate analytics off switch. Events include activity, configuring a personal API key (the event, not the key), and clicks on source-code and support links. Events are associated with a client identifier, time, extension version, and installation source. Trial records also support quota, exhaustion, and generation-cost statistics, to understand feature use, manage the service budget, and improve reading assistance.

Analytics events do not contain visited page addresses, selected text, questions, full answers, or your personal API key. Even when AI requests go directly to DeepSeek using your key, the extension may send the listed analytics to this project's service. Disabling or uninstalling the extension stops its future requests; it does not automatically delete existing server records.

Third parties, sharing, and limited use

The service is hosted on Alibaba Cloud. DeepSeek receives the content needed to generate answers. If additional human verification is enabled, the verification page may use Cloudflare Turnstile, which processes network and device information needed for verification. Browser sync, extension stores, and GitHub, support, or payment services that you choose to visit operate under their own privacy terms.

We limit user-data use to providing, maintaining, securing, and improving the disclosed reading-assistance features and related service operations. We restrict use and sharing in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell user data or use it for targeted advertising or data-broker services. Apart from the service processing described above, information is handled or disclosed only as needed for applicable legal requirements, security incidents, or support you explicitly request.

Retention and security

Under the current configuration, raw usage events are retained for 30 days, security logs and request diagnostics for 7 days, and daily activity and click records for 90 days. Scheduled cleanup removes expired records. Client, quota, request-cost, and administrative audit records currently have no uniform automatic expiration, supporting service continuity, abuse prevention, and cost reconciliation. Gateway logs and backups follow operational settings and may remain after application records are cleaned up.

Local caches and annotations remain until you clear them or the browser removes the relevant data. Network requests use HTTPS. Your personal API key is managed by browser extension storage; we do not promise additional application-level encryption on your device. We restrict administrative access and validate credentials, but no system can guarantee absolute security.

Your controls and contact

You can change or remove your API key and clear caches and annotations in extension settings. You can also manage website access, disable, or uninstall the extension through your browser. Manage synchronized data through the relevant browser or account settings. Clearing local data does not automatically delete server data.

To ask about, access, correct, or request deletion of server records relating to you, contact the maintainer through GitHub Issues. We will verify the connection between the request and the records, and handle it subject to applicable requirements and necessary security or cost-record retention. Issues are public: do not post API keys, access tokens, passwords, or sensitive reading content. Ask for a private contact method before sharing private information.

Updates will be dated on this page. Material changes to data practices will be communicated through the website or the extension.