隐私说明

可能处理的数据

产品可能处理用户输入的提示词、上传的图片或视频、画布内容、项目名称、生成结果、错误信息以及维持项目状态所需的本地存储数据。产品能力与处理边界的背景说明见关于 ChatPod Studio。请避免在提示词或附件中提交密码、密钥、身份证号或其他敏感个人信息。

Depending on the deployment, ChatPod Studio may process prompts, uploaded media, canvas/project state, generation outputs, and diagnostic error text required to fulfill a user-initiated request.

使用目的

这些数据用于执行用户请求、调用已配置的生成服务、保存项目、恢复工作状态、展示生成历史以及诊断失败。产品不应在没有明确操作的情况下主动提交生成任务。运营方如需将数据用于改进模型或统计产品使用，应单独说明法律依据与退出方式。

第三方服务、子处理方（sub-processors）与 DPA

图库搜索、图片生成、视频生成、OCR 或其他能力可能由部署方配置的第三方服务提供。开源仓库本身不绑定唯一供应商。以下是当前产品代码会调用的数据子处理类别；正式上线必须配上运营主体名称、处理地区、保留期限、以及可下载的 data processing agreement（DPA）。

• 文本 / 图片 / 视频生成接口：用户提示词、参考图和生成结果会发往运营方配置的模型网关（常见为兼容 OpenAI 的云厂商），用于完成用户主动发起的生成请求。
• 灵感图库：灵感页可能向图库检索服务请求公开参考静帧（部署方可配置；常见为库存图 API）。检索词不含账户密码。
• 对象存储或本地落盘：项目快照、上传素材和生成文件按部署方存储策略保存，用于恢复画布。
• 账户与网关：登录、会话和访问控制由部署方的身份服务处理，不在画布前端内置独立身份供应商。

Sub-processor / DPA disclosure: ChatPod Studio does not ship a single global vendor list. Operators must publish the live sub-processor names, processing regions, retention, and data processing agreement (DPA) terms on this page or a linked DPA document, and update them whenever a provider is added or removed.

保留与安全

项目与生成结果的保留时长由部署方的存储策略决定。传输应使用部署环境提供的 HTTPS 与访问控制；本地开发环境可能使用 HTTP，不代表生产配置。密钥与服务凭证应存放在服务端环境变量中，不应写入前端包或公开仓库。

用户控制

用户应避免上传无权使用的内容和敏感信息，并可通过项目界面删除不再需要的项目。部署方还应提供访问、更正、导出和删除请求的正式渠道；需要提出请求时请使用联系与反馈入口。

Practical guidance for operators and users

Treat prompts and uploads as production data. Prefer the minimum assets needed for a task, remove projects you no longer need, and never paste API keys into the composer. Operators should keep vendor contracts, retention schedules, and incident contacts documented alongside this page, and should update the public subprocessor list whenever a provider is added or removed.

This notice describes what the product code can process; it is not a substitute for a jurisdiction-specific privacy policy. If you deploy ChatPod Studio for a company or school, add your legal entity name, contact email, DPA terms, and cross-border transfer notes before inviting end users. For product entry and account questions outside Studio, see chatpod.online.

Children should not submit personal data through generation workflows. Where local law requires parental consent or age gates, the operator must implement them at the account or gateway layer because this workbench alone does not provide age verification. When in doubt, store less, retain shorter, and document every outbound call that may include user content.

Logs used for debugging should avoid raw prompts when possible, or should be redacted and time-bounded. If you embed Studio inside another product shell, ensure the parent application’s privacy notice covers the same data flows and points users back to this page for workbench-specific details. Users can also ask the operator how long failed jobs and temporary uploads are kept before automatic cleanup.