隐私政策 (Privacy Policy)
核心承诺：UniPublisher 采用「本地优先（Local-First）」架构。您的文章草稿、正文、配图以及第三方平台登录凭证（Cookies）仅保存在您的本地设备上。我们的云端服务器不读取、不代存、也不以存储用户文章正文或平台密码为设计用途。
1. 软件定位与数据架构原则
UniPublisher（“本软件”或“我们”）是一款桌面内容排版与多平台发布辅助客户端。我们遵循极简数据收集原则：云端只做客户端无法单独完成的事情（如账户鉴权、额度流水与平台选择器热更新），所有发布动作均在用户本机运行的本地浏览器环境中完成。
2. 我们收集的信息
为了保障账号正常登录、额度计量与配置下发，我们仅收集以下必要的数据：
- 身份标识：通过 Google OAuth 登录时获取的邮箱地址及用户唯一身份标识（Provider Sub ID），用于识别您的账户与授权状态。
- 设备匿名标识：客户端本地生成的匿名设备标识，仅用于识别「这台机器」，以便您日后自行解绑；不做任何硬件指纹采集，也不包含任何可反向追踪到您个人的信息。
- 发布回执与额度流水：包含发布结果（成功 / 失败 / 没能确认）、目标平台标识（如 wechat、zhihu）、发布生成的外部文章 URL 或 ID，以及额度增减记录。除下述「自愿提交的反馈」外，我们不收集您的文章标题、正文及多媒体内容。
- 自愿提交的反馈：若您主动在客户端内提交问题反馈，我们仅接收您填写的反馈文本，以及您主动勾选后附带的本地错误日志。该日志可能包含您的稿件标题与已发布链接——客户端在勾选框旁已注明这一点，不勾选则不会上传任何日志。
3. 绝不收集与上传的数据
为保护您的内容版权与账号安全，以下数据永远保留在您的个人设备：
- 未发布草稿与文章内容：所有本地文档存储于用户操作系统的应用数据目录内，不会同步上传至云端服务器。
- 第三方平台凭证与会话：微信公众号、微博、知乎、币安等平台的登录 Cookie 与本地存储均保留在您本机的浏览器隔离环境中，服务器不代填、不代存、不上云。
- 文章图片与素材：文章配图由客户端直接在本地与目标平台之间交互上传，不经过我们的中转服务器。
4. 数据使用目的
我们收集的有限信息仅用于以下用途：
- 维护您的账户登录状态与可用发布额度（按渠道成功计量）。
- 向客户端动态下发最新的平台选择器与流程配置（保证平台改版后的持续可用性）。
- 为用户提供技术支持与故障排查。
5. 数据安全与第三方服务
我们采用行业标准的安全技术保护数据传输与存储：
- 所有网络通信均通过 HTTPS（TLS）加密传输。
- 用户会话令牌在数据库中仅存储不可逆的加密哈希（SHA-256），不存储明文令牌。
- 支付处理：涉及付费充值时，交易由经过严格合规认证的第三方平台（如 Paddle、Lemon Squeezy、爱发电等）处理。我们不接触、不处理也不存储任何信用卡号或银行卡详细信息。
6. 用户权利与数据删除
您对自己的数据拥有完全的控制权：
- 您可以随时在桌面客户端查看您的可用额度与邀请记录。
- 如需注销账户或导出与您账户关联的云端记录，请通过下方方式联系我们，我们将在 5 个工作日内处理。
⚠️ 需要说明的是：注销时我们会删除或匿名化可识别到您的信息（邮箱、身份标识、设备记录、反馈内容），但额度流水与发布回执会以匿名形式保留——这是一份只增不改的账本，用于对账与退款核查，改写它等同于没有账本。保留下来的记录不再关联到您本人。
7. 联系我们 (Contact Us)
如果您对本隐私政策有任何疑问、建议或合规咨询，请联系：
📧 官方支持邮箱：[email protected]
Core Commitment: UniPublisher employs a "Local-First" architecture. Your article drafts, full text, images, and third-party platform credentials (cookies) remain exclusively on your local device. Our cloud servers do not inspect, host, or store your article content or platform passwords.
1. Product Nature & Architecture Principles
UniPublisher ("the Software", "we", or "us") is a desktop application designed for local article formatting and multi-platform publishing. We adhere strictly to data minimization: cloud servers only handle tasks the client cannot perform alone (such as account authentication, credit ledger bookkeeping, and dynamic selector updates). All publishing dispatches are executed locally within your device's isolated browser environment.
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: Publishing outcomes (Success / Failed / Unconfirmed), target platform identifiers (e.g., wechat, zhihu), generated post URLs/IDs, and credit ledger transaction records. Except for voluntary user-submitted feedback described below, we never collect article titles, body content, or multimedia assets.
- 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. Data We Never Collect or Upload
To safeguard your intellectual property and platform security, the following data permanently stays on your local machine:
- 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 Login Cookies & Session Storage: Session cookies and local storage tokens for WeChat, Weibo, Zhihu, Binance, etc., reside exclusively inside your local isolated Chromium instance.
- Images & Media Attachments: Images are uploaded directly from your local filesystem to your destination platforms without routing through our proxy servers.
4. 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.
5. 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.
6. 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.
7. Contact Us
For questions, privacy inquiries, or compliance requests regarding this policy, please reach out to:
📧 Official Support Email: [email protected]