Overview

Doc Copilot does not sell user data and does not use user data for advertising, profiling, credit evaluation, or analytics unrelated to extension functionality. User data is shared only when needed to provide user-requested AI features, browser features, or support.

Service Description

Doc Copilot helps users write, rewrite, polish, translate, review, discuss, reference, and export content in supported web document editors, publishing pages, read-only pages, and article pages.

Doc Copilot can connect to HeyToken. HeyToken provides an OpenAI-compatible service endpoint. Users can create an API key in the HeyToken console and configure the Base URL, API key, and model ID in the extension.

Data We Process

Depending on the features you enable and use, Doc Copilot may process the following data:

• Visible text, titles, structured content, and editor content from the current page or document.
• Selected text, nearby cursor text, page URL, document title, and page context needed to generate a response.
• Text that you enter into Doc Copilot chat, prompt, rewrite, review, reference, or settings fields.
• Images, image references, or related descriptions that you explicitly add to an AI chat or generation workflow.
• Extension configuration, including API Base URL, API key, model ID, feature toggles, prompt settings, and interface preferences.
• Local chat history, pinned references, draft state, and token usage counters.
• PDF data and download file names generated locally by Chrome when you use export or save features.
• Technical information related to service requests, such as request time, model name, token usage, response status, and error information.

How Data Is Used

Doc Copilot processes data only to provide extension features requested by the user, including:

• Generating autocomplete suggestions, continuation text, and ghost text.
• Rewriting, polishing, translating, shortening, expanding, or fixing selected text.
• Analyzing the current document and generating review suggestions, summaries, checklists, or editing suggestions.
• Answering user questions about the current page, document, or pinned reference content.
• Saving extension settings, model configuration, local sessions, pinned references, and user preferences.
• Counting local token usage so users can understand request consumption.
• Generating and downloading PDF files when requested by the user.
• Troubleshooting issues, preventing abuse, maintaining service reliability, and completing usage or billing records where applicable.

AI Services

Before using AI features, users configure an OpenAI-compatible API Base URL, API key, and model ID in the extension. When an AI feature is used, the extension sends the prompt, document context, selected text, chat messages, and optional images needed for the current task to that configured endpoint.

If the user configures HeyToken as the endpoint, related requests are sent to HeyToken. HeyToken may process API keys, account information, request metadata, model names, token usage, response status, and error information to provide request routing, model calls, authentication, quota deduction, billing, abuse prevention, troubleshooting, and service reliability.

HeyToken may forward user requests to upstream model providers. Upstream model providers may process request content under their own terms and privacy policies. Users should avoid submitting content they are not allowed to share or highly sensitive content to untrusted endpoints.

Local Storage

Doc Copilot stores extension settings in Chrome extension storage on the user's device. Chat history, pinned references, drafts, page indexes, and related feature data may be stored in browser local storage, IndexedDB, or other browser-managed local storage.

API keys are stored in browser extension storage so the extension can send requests to the configured endpoint. Users should protect their browser profile and device access to prevent unauthorized access to or misuse of API keys.

The developer does not directly receive local storage records from the user's device unless the user voluntarily provides them for support or debugging.

Data Sharing

Doc Copilot may share or transmit data in the following situations:

• When users use AI features, data needed for the current task is sent to the configured endpoint, such as HeyToken or another compatible service.
• When HeyToken is used, HeyToken may forward requests to upstream model providers to complete model responses.
• Chrome and the browser platform process necessary data for extension storage, context menus, page access, downloads, and PDF export.
• When users contact support and provide logs, screenshots, configuration, or issue context, the developer uses that information to handle support requests.

Doc Copilot does not sell user data and does not share user data for advertising, ad attribution, cross-site tracking, or data broker purposes.

Chrome Permissions

Doc Copilot uses Chrome extension permissions to provide user-visible features:

User Controls

Users can control their data in the following ways:

• Edit or remove API Base URL, API key, and model configuration in extension settings.
• Disable optional features, clear local chat history, and delete pinned references or drafts.
• Clear extension storage in Chrome settings, or uninstall the extension to remove extension-controlled local data.
• Delete or reset API keys in the HeyToken console to stop the extension from continuing to use those keys.
• Contact support for questions related to HeyToken accounts, orders, API keys, or service logs.

Security

Doc Copilot sends requests to the API address configured by the user. Users should use HTTPS endpoints, protect API keys, and avoid saving sensitive credentials on shared devices or untrusted browser environments.

HeyToken uses reasonable technical and administrative measures to protect data processed by its service. However, no local storage, browser extension environment, or network transmission can be guaranteed to be completely secure. Users should choose endpoints and model providers based on the sensitivity of their documents.

Children's Privacy

Doc Copilot is designed for productivity and document workflows and is not directed to children. Minors should use the extension only with consent and guidance from a parent, guardian, school, or organization administrator.

Changes to This Policy

This policy may be updated when Doc Copilot features, data processing practices, service integrations, or legal requirements change. The effective date at the top of the page will be updated when material changes are made.

Contact

For privacy, data processing, or service integration questions related to Doc Copilot, contact the developer through the support contact shown on the Doc Copilot Chrome Web Store listing or the contact channel provided by HeyToken.

概要

Doc Copilot 不出售用户数据，不将用户数据用于广告、用户画像、信用评估或与扩展功能无关的分析。除非为了提供用户主动使用的 AI 功能、浏览器功能或支持服务所必需，Doc Copilot 不会共享用户数据。

服务说明

Doc Copilot 用于在支持的网页文档编辑器、发布页面、只读页面和文章页面中辅助用户进行自动补全、改写、润色、翻译、审稿、问答、引用和导出。

Doc Copilot 可以接入 HeyToken。HeyToken 提供 OpenAI-compatible 服务端点，用户可在 HeyToken 控制台创建 API Key，并在扩展中配置 Base URL、API Key 和模型 ID。

处理的数据

根据用户启用和使用的功能，Doc Copilot 可能处理以下数据：

• 当前页面或文档中的可见文本、标题、结构化内容和编辑器内容。
• 用户选中的文本、光标附近文本、页面 URL、文档标题和生成回复所需的页面上下文。
• 用户在 Doc Copilot 聊天、提示词、改写、审稿、引用或设置输入框中输入的文本。
• 用户明确添加到 AI 对话或生成流程中的图片、图片引用或相关说明。
• 扩展配置，包括 API Base URL、API Key、模型 ID、功能开关、提示词配置和界面偏好。
• 本地聊天历史、固定引用内容、草稿状态和 Token 用量计数。
• 用户使用导出或保存功能时，由 Chrome 在本地生成的 PDF 数据和下载文件名。
• 与服务请求相关的技术信息，例如请求时间、模型名称、Token 用量、响应状态和错误信息。

数据用途

Doc Copilot 仅为提供用户请求的扩展功能而处理数据，包括：

• 生成自动补全建议、续写内容和 ghost text。
• 改写、润色、翻译、缩短、扩展或修正选中文本。
• 分析当前文档并生成审稿建议、摘要、检查项或编辑建议。
• 回答用户关于当前页面、文档或固定引用内容的问题。
• 保存扩展设置、模型配置、本地会话、固定引用和用户偏好。
• 统计本地 Token 用量，帮助用户了解请求消耗。
• 在用户请求时生成和下载 PDF 文件。
• 排查故障、防止滥用、保障服务稳定性和完成用量或计费记录。

AI 服务

使用 AI 功能前，用户需要在扩展中配置 OpenAI-compatible API Base URL、API Key 和模型 ID。用户使用 AI 功能时，扩展会把当前任务所需的提示词、文档上下文、选中文本、聊天消息和可选图片发送到该配置的服务端点。

如果用户将 HeyToken 配置为服务端点，相关请求会发送到 HeyToken。HeyToken 可能为了提供请求转发、模型调用、身份验证、额度扣减、计费、风控、日志排查和服务稳定性处理 API Key、账户信息、请求元数据、模型名称、Token 用量、响应状态和错误信息。

HeyToken 可能会将用户请求转发给上游模型服务商。上游模型服务商可能根据其服务条款和隐私政策处理请求内容。用户应避免提交无权共享的内容，或向不可信服务端点发送高度敏感信息。

本地存储

Doc Copilot 会把扩展设置保存在用户设备上的 Chrome extension storage 中。聊天历史、固定引用、草稿和页面索引等功能数据可能保存在浏览器本地存储、IndexedDB 或其他浏览器管理的本地存储中。

API Key 会保存在浏览器扩展存储中，用于后续向用户配置的服务端点发起请求。用户应保护自己的浏览器配置文件和设备访问权限，避免他人读取或滥用 API Key。

除非用户主动将本地数据提供给开发者用于支持或调试，否则开发者不会直接接收用户设备上的本地存储记录。

数据共享

Doc Copilot 可能在以下场景共享或传输数据：

• 用户使用 AI 功能时，将当前任务所需数据发送到用户配置的服务端点，例如 HeyToken 或其他兼容服务。
• 使用 HeyToken 时，HeyToken 可能将请求转发给上游模型服务商以完成模型响应。
• Chrome 和浏览器平台会为扩展存储、右键菜单、页面访问、下载和 PDF 导出等功能处理必要数据。
• 用户主动联系支持并提供日志、截图、配置或问题上下文时，开发者会使用这些信息处理支持请求。

Doc Copilot 不出售用户数据，也不会为了广告投放、广告归因、跨站追踪或数据经纪目的共享用户数据。

Chrome 权限

Doc Copilot 使用 Chrome 扩展权限实现用户可见功能：

用户控制

用户可以通过以下方式控制自己的数据：

• 在扩展设置中修改或删除 API Base URL、API Key 和模型配置。
• 关闭可选功能、清除本地聊天历史、删除固定引用和草稿内容。
• 通过 Chrome 扩展设置清除扩展存储，或卸载扩展以移除扩展控制的本地数据。
• 在 HeyToken 控制台删除或重置 API Key，停止扩展继续使用该 Key。
• 联系支持方请求处理与 HeyToken 账户、订单、API Key 或服务日志相关的问题。

安全

Doc Copilot 会按用户配置的 API 地址发送请求。建议用户使用 HTTPS 服务端点，妥善保管 API Key，并避免在共享设备或不可信浏览器环境中保存敏感凭据。

HeyToken 会采取合理的技术和管理措施保护其服务中处理的数据。但任何本地存储、浏览器扩展环境或网络传输都无法保证绝对安全，用户应根据文档内容敏感程度选择合适的服务端点和模型供应商。

儿童隐私

Doc Copilot 面向生产力和文档工作流场景，不面向儿童设计。如未成年人使用本扩展，应在监护人或学校、组织管理员同意和指导下使用。

政策变更

当 Doc Copilot 的功能、数据处理方式、服务接入方式或相关法律要求发生变化时，本政策可能更新。发生重要变更时，页面顶部的生效日期会同步更新。

联系方式

如有与 Doc Copilot 隐私、数据处理或服务接入相关的问题，请通过 Doc Copilot Chrome Web Store 页面展示的支持联系方式，或 HeyToken 站点提供的联系方式联系开发者。