中文隐私政策
图话匣 AI Image Relay（以下简称“本扩展”）是一款用于在 Chrome 侧边栏中调用用户自行配置的第三方兼容图片生成接口的工具。本扩展不是 OpenAI 官方产品，也不提供公共图片生成服务；它主要作为本地工作台，帮助用户管理接口配置、提示词、参考图、生成结果和会话历史。
1. 我们处理哪些信息
1.1 用户主动输入的信息
包括接口名称、API Base URL、API Key、模型名称、默认尺寸、默认质量、默认输出格式、提示词、字体合规选项以及其他与生成任务相关的参数。
1.2 用户主动添加的文件
包括参考图、蒙版图以及生成得到的图片结果。这些文件会被本扩展保存到浏览器本地，以便后续查看、删除、下载或再次生成。
1.3 本地会话与历史记录
包括会话标题、消息内容、时间戳、图片关联信息、接口连通状态缓存、版本信息缓存等，用于在本地恢复与管理使用历史。
1.4 临时页面状态
当用户使用“全屏显示”功能时，扩展会将当前提示词和部分参数临时写入浏览器本地 localStorage 以便新标签页读取；该临时数据在读取后会被删除。
2. 这些信息保存在哪里
- 大多数数据默认保存在浏览器本地
IndexedDB 中，包括接口配置、会话记录、消息、图片附件和生成结果。
- “全屏显示”功能的临时草稿会短暂保存在浏览器本地
localStorage 中，用于页面切换，不作为长期存储。
- 预览大图时使用的对象 URL 仅存在于当前浏览器运行内存中，关闭预览后会释放。
3. 何时会向网络发送数据
本扩展不会默认把你的本地会话、提示词、图片或 API Key 自动上传到开发者服务器。只有在用户主动触发特定功能时，才会向对应的远程地址发起请求。
3.1 接口连通测试
当用户点击“测试连通”或执行异步自检时，本扩展会向用户自行配置的第三方接口地址请求 /v1/models，并在请求头中带上用户保存的 API Key，以判断该接口是否可用。
3.2 图片生成或编辑
当用户点击“生成图片”时，本扩展会向用户自行配置的第三方接口地址请求 /v1/images/generations 或 /v1/images/edits。此时，提示词、用户临时选择的生成参数以及用户主动上传或粘贴的参考图/蒙版图会发送给该第三方接口。
3.3 版本检查
本扩展会从固定地址 https://www.ijihe.com/chrome/ai-image/updates/latest.json 获取最新版本信息，用于展示版本状态、更新说明和试用链接。该请求通常只会携带浏览器进行普通 HTTP 请求时产生的基础网络信息，例如 IP 地址和 User-Agent。
3.4 可选远程图片资源
当用户将鼠标移入或聚焦“抖音教程”链接时，扩展会尝试异步加载一张远程二维码图片：https://www.ijihe.com/chrome/app_images/douyin-qingge.png。如果用户未触发该交互，则不会加载该图片。
3.5 用户主动点击的外部链接
当用户点击帮助页、试用注册链接、抖音主页或项目仓库等外部链接时，会在浏览器中新开页面访问第三方站点；这些页面访问行为受对应站点自身隐私政策约束。
4. 第三方接口与第三方服务
- 本扩展允许用户自定义第三方兼容接口地址。你填写的接口地址、API Key、提示词和参考图一旦用于连通测试或生成请求，就会发送到你选择的第三方服务提供方。
- 这些第三方服务并不由本扩展开发者控制，其数据处理方式、日志保留规则、地域位置和安全措施由相应服务提供方自行决定。
- 在向任何第三方接口发送数据前，请你自行确认对方的服务条款和隐私政策是否符合你的使用要求。
5. 我们不会做什么
- 不会在未触发生成或测试的情况下，主动把你的提示词、图片或 API Key 批量上传到开发者服务器。
- 不会出售你的个人信息。
- 不会将本地会话记录用于广告投放或跨站跟踪。
- 不会读取与本扩展功能无关的网页内容。
6. 权限与对应目的
6.1 sidePanel
用于在 Chrome 侧边栏中提供本扩展的主工作界面，方便用户在当前浏览环境下持续进行提示词输入、接口切换、图片生成与历史查看。
6.2 unlimitedStorage
用于在本地长期保存接口配置、会话记录、生成结果以及图片附件，避免因默认存储配额不足而导致历史或图片保存失败。
6.3 主机权限
用于访问用户自行填写的第三方接口地址，以及访问固定的版本检查地址和可选远程二维码资源地址。该权限不用于采集网页浏览数据。
7. 数据安全
我们尽力通过 Chrome 扩展机制和本地存储方式减少不必要的数据传输。但请理解，任何保存在本地设备上的信息都可能受到设备安全状态、浏览器环境、恶意软件或第三方接口服务本身的影响。请妥善保管你的设备和 API Key，并优先使用你信任的第三方接口服务。
8. 你的控制权
- 你可以在扩展界面中逐条删除消息记录、删除整个会话、清空全部历史，或删除不再使用的接口配置。
- 你可以随时修改或移除 API Key、接口地址和默认模型。
- 如需尽量减少本地残留数据，建议在卸载扩展前先在扩展内手动清空历史与接口配置。浏览器通常会在扩展卸载后移除对应本地存储，但具体行为仍取决于浏览器实现。
9. 未成年人
本扩展面向一般用户提供工具能力，不针对未成年人设计，也不会主动识别用户年龄。如果你是监护人，并认为未成年人通过本扩展输入了不应处理的信息，请停止继续使用相关第三方服务并尽快清理本地数据。
10. 隐私政策更新
如果本扩展的功能、权限或数据处理方式发生重大变化，我们可能会更新本隐私政策。更新后的版本会发布在本页面，并以页面中的“最近更新”日期为准。
11. 联系与反馈
如果你对本隐私政策或本扩展的数据处理方式有疑问，可通过以下入口反馈：
English Privacy Policy
Tuhuaxia AI Image Relay ("the Extension") is a Chrome side panel tool that lets users call their own third-party compatible image generation endpoints. The Extension is not an official OpenAI product and does not provide a public image generation service. Its primary role is to act as a local workspace for managing endpoint settings, prompts, reference images, generated results, and conversation history.
1. Information We Process
1.1 Information you enter
This includes interface names, API Base URLs, API Keys, model IDs, default size, default quality, default output format, prompts, font-compliance preferences, and other generation-related parameters.
1.2 Files you add
This includes reference images, mask images, and generated output images. These files are stored locally by the Extension so that you can view, delete, download, or regenerate them later.
1.3 Local conversations and history
This includes conversation titles, message content, timestamps, image associations, interface health cache, and update information cache used to restore and manage local history.
1.4 Temporary page state
When you use the full-page view feature, the Extension temporarily stores the current prompt and selected parameters in browser localStorage so that the new tab can restore them. That temporary data is removed after it is read.
2. Where Information Is Stored
- Most data is stored locally in browser
IndexedDB, including interface settings, conversations, messages, image attachments, and generated results.
- Temporary draft data for the full-page feature may be stored briefly in browser
localStorage for page-to-page handoff.
- Object URLs used for image preview exist only in current browser memory and are released when preview is closed.
3. When Data Is Sent Over the Network
The Extension does not automatically upload your local conversations, prompts, images, or API Keys to the developer's server by default. Network requests occur only when you actively trigger certain features.
3.1 Connection checks
When you click connection test or when an async health check runs, the Extension requests /v1/models from the third-party endpoint you configured and includes your saved API Key in the request header.
3.2 Image generation and editing
When you click generate, the Extension requests /v1/images/generations or /v1/images/edits from the third-party endpoint you configured. At that time, your prompt, selected generation parameters, and any reference or mask images you explicitly provide are sent to that third-party service.
3.3 Update checks
The Extension fetches version metadata from https://www.ijihe.com/chrome/ai-image/updates/latest.json to display version status, release notes, and trial links. Like any normal HTTP request, this may expose basic network-level information such as IP address and User-Agent to that server.
3.4 Optional remote image resource
When you hover or focus the tutorial link, the Extension may lazily load a remote QR image from https://www.ijihe.com/chrome/app_images/douyin-qingge.png. If you never trigger that interaction, the image is not loaded.
3.5 External links you click
If you click the help page, trial registration page, Douyin page, or project repository link, your browser opens those external websites in a new tab. Those visits are governed by the privacy practices of the corresponding websites.
4. Third-Party Endpoints and Services
- The Extension lets you define third-party compatible API endpoints. Once you use connection testing or image generation, your endpoint URL, API Key, prompt, and selected input images may be sent to the service you chose.
- Those third-party services are not controlled by the Extension developer. Their logging, retention, security, and regional processing practices are determined by their own operators.
- Please review the terms and privacy policy of any third-party endpoint before sending data to it.
5. What We Do Not Do
- We do not proactively upload your prompts, images, or API Keys to the developer's server unless you trigger a feature that requires a network request.
- We do not sell personal information.
- We do not use your local conversations for advertising or cross-site tracking.
- We do not read unrelated web page content for the Extension's core functionality.
6. Permissions and Why They Are Needed
6.1 sidePanel
Used to provide the Extension's primary workspace in the Chrome side panel so users can enter prompts, switch interfaces, generate images, and review history without leaving the current browsing context.
6.2 unlimitedStorage
Used to preserve interface settings, local conversations, generated results, and image attachments on the device without quickly running into default storage limits.
6.3 Host permissions
Used to connect to user-configured third-party API endpoints, the fixed update feed URL, and the optional remote QR image URL. These permissions are not used to collect unrelated browsing data.
7. Security
We try to minimize unnecessary data transmission by relying primarily on browser-local storage and Chrome extension mechanisms. However, any data stored on a device may still be affected by device security, browser environment, malware, or the practices of the third-party APIs you choose. Please protect your device and API Keys, and use only trusted third-party endpoints.
8. Your Choices
- You can delete individual records, remove entire conversations, clear local history, and delete saved interface settings from within the Extension.
- You can modify or remove your API Key, endpoint URL, and default model at any time.
- To reduce local remnants before uninstalling, you may manually clear history and interface settings first. Browsers commonly remove extension storage upon uninstall, but exact behavior depends on browser implementation.
9. Children's Privacy
The Extension is a general-purpose tool and is not specifically designed for children. We do not intentionally identify the age of users. If you are a guardian and believe a minor entered information that should not be processed, please stop using the related third-party service and clear the local data as soon as possible.
10. Policy Updates
We may update this Privacy Policy if the Extension's features, permissions, or data handling practices change materially. The latest version will be published on this page, and the "Last updated" date above will indicate the effective revision date.
11. Contact
If you have questions about this Privacy Policy or the Extension's data handling, you may contact us through: