UniPublisher Logo UniPublisher
← 返回首页
隐私与安全

隐私政策

生效日期:2026-10-31

核心承诺:UniPublisher 采用「本地优先(Local-First)」架构,本地文档、原图和平台 Cookie 不做云端备份。只有您主动确认启用的功能才发送必要数据:部分官方授权经过服务端交换;Threads 图片发布使用下述临时中转,不是永久图床。

1. 软件定位与数据架构原则

UniPublisher(“本软件”或“我们”)是一款桌面内容排版与多平台发布辅助客户端。云端仅处理必要的账户鉴权、额度记录、配置下发、官方 OAuth 交换及明确提示的临时图片中转。发布动作由本机客户端通过浏览器或官方 API 执行。

2. 我们收集的信息

为了保障账号正常登录、额度计量与配置下发,我们仅收集以下必要的数据:

  • 身份标识:通过 Google OAuth 登录时获取的邮箱地址及用户唯一身份标识(Provider Sub ID),用于识别您的账户与授权状态。
  • 设备匿名标识:客户端本地生成的匿名设备标识,仅用于识别「这台机器」,以便您日后自行解绑;不做任何硬件指纹采集,也不包含任何可反向追踪到您个人的信息。
  • 发布回执与额度流水:包含发布结果、目标平台标识、外部文章 URL 或 ID,以及额度记录。除您自愿提交的反馈和明确确认的临时图片中转外,服务端不收集您的文章标题、正文或多媒体内容。
  • 自愿提交的反馈:若您主动在客户端内提交问题反馈,我们仅接收您填写的反馈文本,以及您主动勾选后附带的本地错误日志。该日志可能包含您的稿件标题与已发布链接——客户端在勾选框旁已注明这一点,不勾选则不会上传任何日志。

3. 本地存储与必要的传输例外

文档与原始素材以本地存储为主,不提供内容云备份。主动发布会将内容送至您选择的平台:

  • 未发布草稿与文章内容:所有本地文档存储于用户操作系统的应用数据目录内,不会同步上传至云端服务器。
  • 第三方平台凭证与会话:平台 Cookie 保存在本机。Threads 等官方 OAuth 会将一次性授权码交给服务端交换令牌;令牌返回客户端后使用系统密钥库加密保存,服务端不将用户令牌写入业务数据库或日志。
  • 文章图片与素材:通常由本机直接传至目标平台。Threads 官方接口要求公网图片地址:只有您在发布确认框同意后,需要中转的所选图片才会临时存入 UniPublisher 的独立 Cloudflare R2 存储,供 Meta 抓取;可用公网直链无需中转,不会上传其他本地素材。临时链接不可枚举,15 分钟后不再提供图片。任务结束后立即尝试删除;失败或中断由小时清理及桶生命周期规则兜底,故障时实际删除可能延后。本地原图始终不变,已发布到 Meta 的副本按 Meta 的政策处理。

4. AI 辅助功能(自带密钥 / BYOK)

UniPublisher 的 AI 辅助功能采用「自带密钥」模式:由您自行配置第三方模型服务商的 API Key,请求由您的电脑直接发往该服务商,不经过 UniPublisher 的服务器。

API 密钥

密钥经操作系统密钥库加密后保存在本机(Windows 使用 DPAPI,macOS 使用 Keychain),不会上传至 UniPublisher 的任何服务器,也不会出现在应用的界面进程中(界面仅显示末尾几位的掩码)。您可以随时在「AI 设置」中删除任一渠道的密钥。

会发送哪些内容

只有您主动触发某个 AI 功能时才会发送内容,不同功能发送的范围不同:

功能 发送的内容
行内起草 仅您输入的提示词
行内续写 提示词 + 当前已生成的草稿
划词润色 / 改写 / 翻译 仅您选中的那段文字
全文翻译 整篇正文,以及标题、副标题、摘要(分批发送)
市场灵感起草 公开市场数据 + 提示词

图片、本地文件和您的平台登录会话不会发送给任何模型服务商。

对话记录

UniPublisher 不保存任何 AI 对话记录——无论在您的电脑上还是在我们的服务器上。本机仅保存一份不含任何内容的配置文件(服务商、模型、接口地址、温度参数)。AI 功能不具备跨会话记忆:关闭或清空当前草稿后,下一次请求即为全新开始。

第三方留存

内容送达您所选择的服务商后,其保存期限与使用方式由该服务商的条款决定。UniPublisher 无法访问、导出或删除这些记录,如需处理请直接联系该服务商。

随时停用

「纯本地模式」会关闭全部 AI 功能与相关网络请求。您也可以将接口地址指向本机运行的模型(如 Ollama),此时内容完全不离开您的电脑。AI 功能与发布、草稿、本地文档等核心功能相互独立,关闭 AI 不影响任何其他功能。

5. 数据使用目的

我们收集的有限信息仅用于以下用途:

  • 维护您的账户登录状态与可用发布额度(按渠道成功计量)。
  • 向客户端动态下发最新的平台选择器与流程配置(保证平台改版后的持续可用性)。
  • 为用户提供技术支持与故障排查。

6. 数据安全与第三方服务

我们采用行业标准的安全技术保护数据传输与存储:

  • 所有网络通信均通过 HTTPS(TLS)加密传输。
  • 用户会话令牌在数据库中仅存储不可逆的加密哈希(SHA-256),不存储明文令牌。
  • 支付处理:涉及付费充值时,交易由经过严格合规认证的第三方平台(如 Paddle、Lemon Squeezy、爱发电等)处理。我们不接触、不处理也不存储任何信用卡号或银行卡详细信息。

7. 用户权利与数据删除

您对自己的数据拥有完全的控制权:

  • 您可以随时在桌面客户端查看您的可用额度与邀请记录。
  • 如需注销账户或导出与您账户关联的云端记录,请通过下方方式联系我们,我们将在 5 个工作日内处理。

    ⚠️ 需要说明的是:注销时我们会删除或匿名化可识别到您的信息(邮箱、身份标识、设备记录、反馈内容),但额度流水与发布回执会以匿名形式保留——这是一份只增不改的账本,用于对账与退款核查,改写它等同于没有账本。保留下来的记录不再关联到您本人。

8. 联系我们

如果您对本隐私政策有任何疑问、建议或合规咨询,请联系:

📧 官方支持邮箱:[email protected]

本政策以中文版为准;英文版仅供参考。

Core Commitment: UniPublisher is local-first. Documents, original images and platform cookies are not backed up to our servers. Features you explicitly approve may transmit necessary data: some official authorization flows use a server-side exchange, and Threads image publishing uses the temporary transfer described below, not permanent image hosting.

1. Product Nature & Architecture Principles

UniPublisher is a desktop formatting and publishing client. Our servers handle necessary account authentication, credit records, configuration, official OAuth exchanges and explicitly disclosed temporary image transfers. Your desktop client performs publishing through browsers or official APIs.

2. Information We Collect

To ensure account security, accurate credit tracking, and service reliability, we collect only minimal, necessary information:

  • Identity & Account: Email address and unique provider subject ID obtained via Google OAuth, used solely to authenticate your account and active balance.
  • Anonymous Device Identifier: A randomly generated UUID created locally on your machine to identify the active device instance for self-service unbinding; no hardware fingerprinting is conducted, and no personally identifiable tracking is attached.
  • Dispatch Receipts & Credit Ledger: Outcomes, target platforms, post URLs/IDs and credit records. Except for voluntary feedback and temporary image transfers you explicitly approve, our servers do not collect article titles, body text or media.
  • Voluntary User Feedback: If you submit in-app feedback or bug reports, we receive your written text and, only if explicitly checked by you, local error logs. These logs may contain article titles and published URLs to assist troubleshooting. If unchecked, no logs are uploaded.

3. Local Storage and Necessary Transfers

Documents and original media remain local without cloud backup. Publishing sends content to the platforms you select:

  • Unpublished Drafts & Content: All local Markdown and rich-text files are saved strictly in your local operating system directory and are never uploaded to our servers.
  • Platform Credentials: Cookies remain local. Official OAuth flows such as Threads send a one-time code to our server for token exchange. The returned user token is encrypted with the local OS key store; our server does not store it in business databases or application logs.
  • Images & Media: Images normally go directly from your device to the platform. Threads requires a public image URL: only after your publishing confirmation are selected images that need transfer temporarily stored in a dedicated UniPublisher Cloudflare R2 bucket for Meta to fetch. Usable public links need no transfer. No other local media is uploaded. Unpredictable temporary links stop serving images after 15 minutes. Deletion is attempted when the task ends; hourly cleanup and bucket lifecycle rules cover interruptions, although outages may delay physical deletion. Local originals remain unchanged. Meta's copy is governed by Meta's policies.

4. AI Assistance (Bring Your Own Key)

UniPublisher's AI features use a bring-your-own-key model: you configure your own third-party model provider API key, and requests go directly from your computer to that provider — they do not pass through UniPublisher's servers.

API Keys

Keys are encrypted at rest by your operating system's credential store (DPAPI on Windows, Keychain on macOS) and stored only on your machine. They are never uploaded to any UniPublisher server and are never exposed to the application's interface process, which only ever receives a masked suffix. You can delete any provider's key at any time in AI Settings.

What Is Sent

Content is sent only when you actively invoke an AI feature, and the scope differs by feature:

Feature What is sent
Inline drafting Your prompt only
Inline continuation Your prompt plus the draft generated so far
Selection polish / rewrite / translate Only the text you selected
Full-article translation The entire article body, plus title, subtitle and summary (sent in batches)
Market-inspiration drafting Public market data plus your prompt

Images, local files and your publishing-platform login sessions are never sent to any model provider.

Conversation History

UniPublisher stores no AI conversation history — neither on your computer nor on our servers. The only thing saved locally is a settings file containing no content (provider, model, endpoint, temperature). The AI has no memory across sessions: once the current draft is cleared or closed, the next request starts fresh.

Third-Party Retention

Once content reaches the provider you selected, its retention and use are governed by that provider's terms. UniPublisher cannot access, export or delete those records; please contact the provider directly.

Turning It Off

"Pure Local Mode" disables all AI features and their network requests. You may also point the endpoint at a model running on your own machine (e.g. Ollama), in which case nothing leaves your computer at all. AI is independent of publishing, drafts and local documents — turning it off affects nothing else.

5. Purpose of Data Processing

The limited data collected is processed strictly for the following purposes:

  • Managing account authentication and tracking valid publishing credits (billed per successful channel).
  • Delivering remote platform selector and workflow hotfixes to ensure continuous publishing capability when third-party platforms update their UI.
  • Providing technical support and diagnosing reported issues.

6. Data Security & Third-Party Processors

We utilize industry-standard security practices to protect all data transmissions and stored records:

  • All network communication is strictly encrypted via HTTPS (TLS).
  • User session tokens are stored in our database using one-way cryptographic hashes (SHA-256).
  • Payment Processing: Transactions are handled by compliant, PCI-certified global payment merchants (such as Paddle, Lemon Squeezy, Afdian). We never store or handle credit card numbers or financial account details.

7. User Rights & Data Deletion

You retain full authority and control over your data:

  • You can review your credit balance and transaction history directly within the desktop application at any time.
  • To request account termination or data export, contact our support team. We will process your request within 5 business days.

    ⚠️ Note on deletion: Upon account closure, we permanently delete or anonymize all personally identifiable information (email, identity tokens, device bindings, feedback submissions). However, credit ledger entries and dispatch receipts are retained in anonymized form—this is an append-only accounting ledger required for auditing and chargeback verification. Retained entries can no longer be linked to your identity.

8. Contact Us

For questions, privacy inquiries, or compliance requests regarding this policy, please reach out to:

📧 Official Support Email: [email protected]

The Chinese version prevails in case of any discrepancy.
© 2026 unipublisher.app. All rights reserved.
定价方案 法律与支持 隐私政策 服务条款 退款政策 返回首页 Windows (.exe) Microsoft Store macOS (.dmg)