悬停检测、设置和历史主要保存在浏览器中；账户、额度、订单与支付状态由 Supabase 云端服务处理。平台模型分析会经 Supabase Edge Function 转发到火山方舟。
PRIVACY POLICY · VERSION 1.4
每一次数据流向
都应该清楚可控
这份说明覆盖 EidoPrompt 浏览器扩展与官网。它解释扩展在本地读取什么、何时会联网、数据会发给谁，以及你如何停止、清除或撤回。
只有你点击分析、导入、粘贴或截图后，扩展才会准备图片并执行分析流程。
当前版本未接入广告、行为分析 SDK 或数据经纪；云端用于身份验证、额度、支付订单、安全审计与必要故障处理。
适用范围与核心承诺
本说明适用于 EidoPrompt 浏览器扩展、扩展内的弹窗与侧栏、网页悬浮分析界面，以及 EidoPrompt 官网。当前 Beta 由 EidoPrompt 项目维护者提供。
EidoPrompt 的单一核心目的，是把你主动选择的图片转换为可编辑的视觉分析结果与提示词。我们不会把经扩展处理的数据用于广告、跨站画像、数据经纪、信贷判断或与图片分析无关的目的。
请注意
“本地优先”不等于“从不处理或传输数据”。获取登录验证码时，邮箱会发送给 Supabase Auth 及其配置的邮件投递服务；使用平台模型时，准备后的图片和分析提示会经 Supabase Edge Function 转发给火山方舟，额度会在服务端预留、提交或退还；购买套餐时，订单与支付状态会发送给 Supabase、PaymentFM 与支付宝；使用自定义 API 时，图片、必要上下文、模型参数与认证信息会直接发送到你配置的服务，并且不扣 EidoPrompt 分析次数。各接收方适用自己的隐私政策和服务条款。
一次分析如何流动
- 本地识别入口
内容脚本在允许的网页中识别图片元素并显示分析入口。单纯浏览或悬停不会把图片发送给视觉模型。
- 由你主动触发
当你点击分析、使用图片右键菜单、导入文件、粘贴剪贴板图片、拖放图片或完成区域截图后，扩展才创建分析任务。
- 读取与准备图片
对于网页图片，扩展会从图片原地址读取文件，明确不附带页面 Cookie；随后在本地校验、缩放或压缩，并可能生成局部检查图。截图流程会先在内存取得当前可见标签页，再只裁出你框选的区域用于分析。
- 选择平台或自定义路径
默认使用 EidoPrompt 平台模型：准备后的图片和提示会先发送到 Supabase Edge Function，再转发给火山方舟，并在平台模型成功返回后扣除一次分析次数。只有自定义 Endpoint、模型和 API Key 通过视觉测试后，才会改为浏览器直连该服务且不扣平台次数；修改但未验证的配置只保留为临时草稿。
- 返回与保存
模型结果返回扩展后会被解析为提示词、关键词和画面信息。若“保存历史”开启，结果会写入浏览器本地历史；否则只在当前会话中显示。
处理的数据与保存位置
| 数据类别 | 包含内容 | 位置与用途 |
|---|---|---|
| 所选图片 | 网页图片、导入/拖放/粘贴的本地图片、区域截图、优化后的图片与局部检查图 | 先在本地内存处理；平台模式经 Supabase Edge Function 转发给火山方舟，自定义模式发送到你验证成功的视觉服务 |
| 图片与页面上下文 | 候选图片 URL、当前页面 URL、图片尺寸、alt、title、来源名、选区坐标；悬浮会话还可能暂存图片附近文字 | 用于定位、预览、恢复任务和辅助分析。当前生产 AI 请求可包含有限的 alt、title、尺寸与比例，不直接发送完整页面 URL 或附近正文 |
| 分析结果与历史 | 中英文提示词、关键词、结构化画面信息、缩略图/图片引用、来源名和时间 | “保存历史”默认开启，最多在 chrome.storage.local 保存 30 条 |
| 视觉服务配置 | Endpoint、模型 ID、API Key、语言和开关设置；未提交输入还可能包含会话草稿 | 已验证配置保存在 chrome.storage.local；未提交草稿保存在 chrome.storage.session，浏览器退出后清除。API Key 当前是浏览器本地明文字段，不是应用级加密 |
| 邮箱账户与登录会话 | 邮箱、Supabase 用户 ID、登录/过期时间、访问令牌与刷新令牌 | 邮箱和账户记录由 Supabase Auth 处理；公开会话摘要保存在 chrome.storage.local，访问与刷新令牌保存在扩展 IndexedDB |
| 云端额度与分析流水 | Supabase 用户 ID、剩余次数、套餐信息、分析请求 ID、预留/提交/退还状态及相关时间 | 由 Supabase 数据库与受鉴权 RPC 保存和处理，是当前额度与扣减结果的权威来源；本地仅缓存公开摘要用于界面显示 |
| 支付订单与审计 | 内部订单号、套餐 SKU、次数、标价与实际支付金额、支付渠道订单号、订单状态、创建/到账/关闭时间、异常原因、人工复核原因和必要回调元数据 | 由 Supabase Edge Function、数据库、PaymentFM 与支付宝处理，用于创建收银台、核对到账、增加额度、幂等保护、退款/争议与异常复核 |
| 临时会话与缓存 | 当前悬浮窗任务、图片/页面引用、分析结果、请求指纹、预览和性能时长 | 保存在 chrome.storage.session 或 Service Worker 内存，用于恢复界面、去重和加速 |
| 官网偏好 | 中英文界面选择 | 官网用浏览器 localStorage 记住语言；当前官网代码未接入广告 Cookie 或分析 SDK |
当前登录不收集或保存密码，而是通过一次性邮箱验证码完成。访问令牌与刷新令牌由扩展保存在浏览器隔离的 IndexedDB 中，但没有额外的应用级加密。购买套餐时，扩展会创建云端订单并在本地生成支付二维码；支付宝账户、银行卡等付款凭证由支付宝及相关支付服务处理，EidoPrompt 扩展不会读取或保存你的支付密码、银行卡号或支付宝登录凭证。
联网对象与第三方接收方
为读取你选中的网页图片，扩展可能向最多 8 个候选图片地址发送 GET 请求，并可能重试。请求不附带页面 Cookie，但图片站点仍可看到常规网络信息，例如 IP 地址和 User-Agent。
Supabase Auth 与其邮件服务处理邮箱验证码、用户 ID、会话信息和常规网络日志；Supabase 数据库、RPC 与 Edge Functions 还处理额度余额、分析扣减流水、套餐订单、支付状态、回调核验与异常复核资料。平台模式下，Edge Function 会短暂接收准备后的图片和提示并转发模型请求，不把平台 API Key 交给扩展。
购买套餐时接收完成收款所需的商户订单号、金额、商品说明、支付方式、回调地址与常规网络信息。支付宝及相关支付服务独立处理你的付款账户与凭证；EidoPrompt 接收签名后的订单结果和必要支付状态，不接收支付密码。
接收优化后的图片像素、可能的局部检查图、模型 ID、分析指令、尺寸/比例、有限 alt/title，以及放在 Authorization Header 中的 API Key。双语或质量复核可能产生多次模型请求。
平台模型服务接收由 Supabase Edge Function 转发的优化图片、分析提示和必要尺寸信息。平台 API Key、固定模型与 Endpoint 只保存在服务端 Secret；扩展不会读取或保存平台 Key。
Chrome、Microsoft Edge、扩展商店和官网托管服务可能按其自身政策处理安装、下载、安全检查或标准访问日志。EidoPrompt 当前未在官网代码中加入广告或行为分析 SDK。
第三方规则
视觉服务商可能保存请求日志、使用数据改进服务、在不同地区处理数据或提供独立删除机制。提交前请阅读你所选服务商的隐私政策，确认你有权上传图片，并避免提交机密、身份证件、医疗、金融或其他敏感内容。
为什么需要这些浏览器权限
使用、共享与 Limited Use 承诺
- 数据仅用于提供、维护和改善用户可见的图片分析与提示词功能，以及必要的安全和故障排查。
- 不出售用户数据，不用于广告投放、跨站画像、数据经纪、信贷或保险资格判断。
- 除法律强制、安全响应、支付争议、异常订单复核或你明确要求的支持外，不允许人员查看你的图片或提示词。平台模式的图片和提示会在 Supabase Edge Function 内短暂转发给火山方舟；自定义模式的图片和提示会发送给你选择的服务。
- 第三方传输限于账户与额度所需的 Supabase、平台模型所需的火山方舟、验证码邮件服务、购买套餐所需的 PaymentFM 与支付宝、你主动验证的自定义视觉服务、读取图片所需的源站，以及上述本机桥接场景。
- 如未来引入遥测、错误上报、开发者托管的图片代理或新的数据用途/接收方，我们会在处理前更新说明，并在扩展内提供显著披露和必要的明确同意。
我们按照 Chrome Web Store 的用户数据与 Limited Use 原则，以及 Microsoft Edge Add-ons 的隐私披露与最小权限原则设计本说明。隐私政策链接不会替代产品内应当提供的即时提示和用户选择。
保存期限、删除与撤回
本地历史最多 30 条。你可以在悬浮历史中“清空”，或在设置中关闭“保存历史”；关闭会立即把历史数组清空。
关闭悬浮窗会清除当前悬浮会话。分析、预览和准备图片缓存通常以 30 分钟为有效期，并会随浏览器/扩展进程结束而消失，但当前没有单独的缓存清除按钮。
默认使用平台模型。视觉测试成功后才启用自定义 API；修改中的 Endpoint、模型和 API Key 会先写入会话草稿，弹窗关闭后重开可恢复。清空三项并保存会切回平台模型；这不会撤回平台模式已经处理过的图片。
退出登录会清除本机访问令牌、刷新令牌和公开会话摘要，并尝试结束当前 Supabase 会话；不会自动删除云端账户、额度或订单。账户删除请求请通过下方联系方式提出。
额度余额、扣减流水、订单、到账、关闭、退款和审计记录会按提供服务、安全、对账、争议处理及适用法律所需期限保存。账户删除不代表依法或为支付审计必须保留的记录会立即清除；不再需要时应删除或去标识化。
卸载扩展会由浏览器移除其本地存储。重新安装前如需彻底重置，请同时确认浏览器没有保留该扩展的配置数据。
EidoPrompt 无法替你删除视觉服务商已经接收的请求、日志或备份。请按对应服务商的政策行使访问、撤回或删除权利。
安全措施与使用者责任
扩展把数据限制在浏览器本地、平台分析 Edge Function、火山方舟、自定义 Endpoint 与必要的图片源站之间，并在读取网页图片时省略 Cookie。我们建议只配置可信、使用 HTTPS 的视觉服务，并使用权限和额度受限的专用 API Key。
支付与额度接口要求登录或服务端凭据，支付回调会验证渠道签名；额度扣减、支付回调和订单入账使用请求标识与幂等保护，以降低重复扣减或重复到账风险。异常订单可能进入人工复核。
自定义配置仍允许 HTTP Endpoint；如果你主动使用 HTTP，图片和 API Key 的传输可能不受加密保护。平台路径固定使用 HTTPS。浏览器本地存储依赖操作系统账户与浏览器配置文件的安全性，API Key 没有额外应用级加密。任何系统都无法保证绝对安全。
请不要分析你无权上传的图片，也不要在共享电脑上保存生产级主密钥。发现密钥泄露时，应立即到对应服务商处撤销并重新生成。
未成年人、跨境与政策更新
EidoPrompt 不面向儿童设计，也不会有意要求未成年人提供个人信息。监护人如发现未成年人通过扩展处理了不适当内容，应先清除本地数据，并通过官方分发渠道联系维护者。
视觉服务的处理地点由你选择的 Endpoint 与服务商决定，可能涉及跨境传输。你应确认该服务的区域、保存和合规安排符合你的需要。
功能或数据做法发生实质变化时，我们会更新版本号和日期；涉及新的接收方、用途或敏感数据处理时，应在变更生效前于扩展界面显著说明，并在法律或商店政策要求时重新取得同意。
联系与问题处理
隐私问题、云端账户删除请求或投诉，请通过邮箱 478839209@qq.com 联系项目维护者。维护者无法远程读取或删除浏览器内的设置、历史和本地额度；这些数据需要由你在扩展中清除或通过卸载扩展移除。
也可以通过你获取 EidoPrompt Beta 的官方分发页面或扩展商店“联系开发者”入口反馈；公开商店页面列出的最新联系方式优先于本地 Beta 包中的历史信息。
PRIVACY POLICY · VERSION 1.4
Every data flow
should stay clear and controlled
This notice covers the EidoPrompt browser extension and website. It explains what the extension reads locally, when it connects to a network, who receives data, and how you can stop, clear, or withdraw processing.
Hover detection, settings, and history mainly stay in your browser; Supabase processes accounts, credits, orders, and payment status. Managed analysis passes through a Supabase Edge Function to Volcengine Ark.
The extension prepares an image only after you analyze, import, paste, drop, or capture it.
The current release has no ads, behavioral analytics SDK, or data brokerage. Cloud processing supports authentication, credits, payment orders, security auditing, and necessary troubleshooting.
Scope and core commitment
This notice applies to the EidoPrompt browser extension, its popup, side panel and in-page analysis overlay, and the EidoPrompt website. The current Beta is provided by the EidoPrompt project maintainer.
EidoPrompt has one core purpose: turning images you actively select into editable visual analysis and prompts. Data processed by the extension is not used for advertising, cross-site profiling, data brokerage, credit decisions, or unrelated purposes.
Important
“Local first” does not mean “no processing or transmission.” When you request a sign-in code, your email is sent to Supabase Auth and its configured email-delivery provider. In managed-model mode, the prepared image and analysis prompt pass through a Supabase Edge Function to Volcengine Ark, and the server reserves, commits, or refunds one credit. In custom-API mode, the image, necessary context, model parameters, and authentication information go directly to the service you verified, without using EidoPrompt credits. When you buy a package, order and payment status data flows through Supabase, PaymentFM, and Alipay. Each recipient applies its own privacy policy and terms.
How one analysis flows
- Local entry point
A content script identifies image elements on permitted pages and displays the analysis control. Merely browsing or hovering does not send an image to a vision model.
- You trigger the task
A task starts only after you click Analyze, use the image context menu, import a file, paste or drop an image, or finish a region capture.
- Read and prepare
For a web image, the extension fetches the source without page cookies, validates and optimizes it locally, and may create detail crops. Region capture first holds the visible tab in memory, then uses only your selected area for analysis.
- Managed or custom path
The managed model is the default: the prepared image and prompt pass through a Supabase Edge Function to Volcengine Ark and one credit is committed only after usable output succeeds. Only a custom Endpoint, model, and API Key that pass the vision test switch to a direct browser request without EidoPrompt credits; edits that are not verified remain a temporary draft.
- Return and save
The response is parsed into prompts, keywords, and visual facts. If Save History is enabled, the result is written to local browser history; otherwise it remains in the current session.
Data processed and where it stays
| Category | What it can include | Location and purpose |
|---|---|---|
| Selected image | Web images, imported/dropped/pasted files, region captures, optimized pixels, and detail inspection crops | Prepared in local memory; managed mode forwards it through Supabase Edge Functions to Volcengine Ark, while custom mode sends it to the verified vision service |
| Image and page context | Candidate image URLs, current page URL, dimensions, alt/title, source name, selection coordinates, and temporarily nearby text | Used to locate, preview, restore, and assist the task. The current production AI request may include limited alt/title and dimensions, but not the full page URL or nearby body text |
| Results and history | Chinese/English prompts, keywords, structured visual facts, thumbnail/image reference, source name, and time | Save History is on by default and keeps up to 30 entries in chrome.storage.local |
| Vision service settings | Endpoint, model ID, API Key, language, and feature toggles; unsubmitted input may be a session draft | Verified settings are stored in chrome.storage.local; unsubmitted drafts use chrome.storage.session and clear when the browser exits. The API Key is a plain local field, not application-level encrypted data |
| Email account and session | Email, Supabase user ID, sign-in/expiry times, access token, and refresh token | Supabase Auth processes the email and account record; a public session summary stays in chrome.storage.local, while access and refresh tokens stay in extension IndexedDB |
| Cloud credits and analysis ledger | Supabase user ID, remaining uses, package information, analysis request ID, reserve/commit/refund status, and related timestamps | Stored and processed by the Supabase database and authenticated RPCs as the authoritative source for credit balances and deductions; only a public summary is cached locally for display |
| Payment orders and audit data | Internal order number, package SKU, credits, listed and actual amount, provider order ID, status, created/credited/closed times, exception reason, manual-review reason, and necessary callback metadata | Processed by Supabase Edge Functions and database, PaymentFM, and Alipay to create checkout, verify payment, grant credits, enforce idempotency, resolve refunds or disputes, and review exceptions |
| Temporary session and cache | Current overlay task, image/page references, results, request fingerprints, previews, and performance timing | Held in chrome.storage.session or service-worker memory to restore UI state, deduplicate requests, and improve speed |
| Website preference | Chinese/English site language | The website uses localStorage to remember language. Its current code has no advertising cookies or analytics SDK |
The current sign-in flow neither collects nor stores a password; it uses a one-time email code. Access and refresh tokens are stored in browser-isolated extension IndexedDB without additional application-level encryption. Buying a package creates a cloud order and generates a payment QR code locally. Alipay and related payment services process payment credentials; the EidoPrompt extension does not read or store your payment password, bank-card number, or Alipay sign-in credentials.
Network recipients and third parties
To read a selected web image, the extension may try up to eight candidate URLs and retry a request. Page cookies are omitted, but the host can still receive ordinary network details such as IP address and User-Agent.
Supabase Auth and its email provider process one-time codes, user ID, session information, and ordinary network logs. Supabase database, RPCs, and Edge Functions also process credit balances, analysis deductions, package orders, payment status, callback verification, and exception-review records. In managed mode, the Edge Function briefly receives the prepared image and prompt to forward the model request; the platform API Key is never sent to the extension.
When you buy a package, they receive the merchant order number, amount, product description, payment method, callback address, and ordinary network information needed to collect payment. Alipay and related payment services independently process your payment account and credentials. EidoPrompt receives signed order results and necessary status, not your payment password.
Receives optimized image pixels, possible detail crops, model ID, analysis instructions, dimensions/ratio, limited alt/title text, and the API Key in an Authorization header. Bilingual output or quality review may make more than one model request.
Receives the optimized image, analysis prompt, and necessary dimensions forwarded by the Supabase Edge Function. The platform API Key, fixed model, and endpoint remain in server-side Secrets; the extension never reads or stores the platform key.
Chrome, Microsoft Edge, extension stores, and the website host may process installation, download, security, or standard access logs under their own policies. The current EidoPrompt website code has no advertising or behavioral analytics SDK.
Third-party rules apply
A vision provider may retain request logs, use data to improve its service, process data in another region, or offer separate deletion controls. Review the provider’s policy before submitting content, confirm you have upload rights, and avoid confidential, identity, medical, financial, or other sensitive images.
Why each browser permission is used
Use, sharing, and Limited Use commitment
- Data is used only to provide, maintain, and improve user-facing image analysis and prompt features, plus necessary security and troubleshooting.
- User data is not sold or used for advertising, cross-site profiling, data brokerage, credit, or insurance eligibility.
- People are not permitted to read your images or prompts except where required by law, security response, payment dispute, exceptional-order review, or support you explicitly request. Managed-mode images and prompts are transiently forwarded from Supabase Edge Functions to Volcengine Ark; custom-mode content goes to the service you select.
- Third-party transfer is limited to Supabase, Volcengine Ark for managed analysis, email delivery for accounts, PaymentFM and Alipay for package purchases, your verified custom vision service, the original image host, and the local bridge case described above.
- If telemetry, error reporting, a developer-hosted image proxy, or any new purpose or recipient is introduced, this notice will be updated before processing begins, with prominent in-product disclosure and affirmative consent where required.
This notice is designed around Chrome Web Store user-data and Limited Use principles and Microsoft Edge Add-ons privacy and minimum-permission requirements. A privacy-policy link does not replace just-in-time disclosure or user choice inside the product.
Retention, deletion, and withdrawal
Local history is limited to 30 entries. Use Clear in overlay history, or disable Save History in settings; disabling immediately writes an empty history array.
Closing the overlay clears the overlay session. Analysis, preview, and prepared-image caches generally use a 30-minute validity window and disappear with the browser/extension process, but there is no separate cache-clear control today.
The managed model is the default. A custom API activates only after the vision test succeeds; edits are held in a session draft and survive a popup close/reopen. Clear all three fields and save to return to the managed model.
Signing out clears local access and refresh tokens and the public session summary, and attempts to end the current Supabase session. It does not automatically delete the cloud account, credits, or orders. Request account deletion through the contact details below.
Credit balances, deductions, orders, payment, closure, refund, and audit records are retained as needed to provide the service, secure accounts, reconcile payments, resolve disputes, and meet applicable law. Account deletion does not require immediate removal of records that must be kept for payment or legal audit; records should be deleted or de-identified when no longer needed.
Uninstalling causes the browser to remove the extension’s local storage. Before reinstalling, verify that your browser has not retained extension configuration if you need a complete reset.
EidoPrompt cannot delete requests, logs, or backups already received by a vision provider. Use that provider’s access, withdrawal, or deletion process.
Security and user responsibility
The extension limits data flow to local browser storage, the managed-analysis Edge Function, Volcengine Ark, your custom Endpoint, and the image host needed to read a selected image. Web-image requests omit cookies. Use a trusted vision service over HTTPS and a dedicated API Key with limited permissions and quota.
Credit and payment interfaces require authentication or server credentials, and payment callbacks verify the provider signature. Analysis deductions, callbacks, and credit grants use request identifiers and idempotency controls to reduce duplicate deductions or credits. Exceptional orders may enter manual review.
Custom settings still allow HTTP Endpoints. If you choose HTTP, the image and API Key may travel without transport encryption. The managed path is HTTPS-only. Browser local storage depends on the security of your operating-system account and browser profile, and the API Key has no additional application-level encryption. No system can guarantee absolute security.
Do not analyze images you lack the right to upload, and do not keep production master keys on a shared computer. Revoke and rotate a key immediately if exposure is suspected.
Children, international processing, and updates
EidoPrompt is not designed for children and does not intentionally request personal information from minors. A guardian who discovers inappropriate processing should first clear local data and then contact the maintainer through the official distribution channel.
Processing location depends on the Endpoint and provider you choose and may involve international transfer. Confirm that the provider’s region, retention, and compliance arrangements meet your needs.
Material changes to features or data practices will update the version and date. A new recipient, purpose, or sensitive-data practice should be prominently disclosed inside the extension before it begins, with renewed consent where law or store policy requires it.
Contact and questions
For a privacy question, cloud-account deletion request, or complaint, contact the project maintainer at 478839209@qq.com. The maintainer cannot remotely inspect or delete browser-local settings, history, or credit profiles; clear them in the extension or remove them by uninstalling the extension.
You may also use the official page where you obtained the EidoPrompt Beta or the extension-store “Contact developer” control. The latest contact details on a public store listing take precedence over historical information bundled with a local Beta.