隐私政策 / Privacy policy
更新日期 / Updated: 2026-10-11 · 运营者 / Operator: Anonono 运营团队
1. 公开匿名与账号关联 / Public anonymity
投稿、评论及公开编号会显示在网站，并可能被搜索引擎收录或由他人分享。邮箱和账号内部标识不会随公开内容输出。登录后发布的内容会在内部关联账号；「匿名」不表示我们完全没有账号或平台日志。
Posts, comments and public references are public and may be indexed or shared. Email addresses and internal account identifiers are not included in public content. Signed-in content is linked internally to your account; anonymity does not mean that no account or infrastructure records exist.
2. 我们处理什么 / Information we process
可选账号使用邮箱、用户名、头像和登录记录。密码由 Supabase Auth 管理，不保存在 Anonono 业务表。浏览器使用随机匿名令牌；服务端保存令牌和 IP 的 HMAC 标识，用于去重、限流及发布额度，不在业务表保存原始 IP。举报保存原因及说明，联系留言保存回复邮箱、主题和正文，仅供运营团队处理。
Optional accounts use email, usernames, avatars and login records. Supabase Auth manages passwords. Random browser tokens and HMAC identifiers support voting, limits and quotas. Our business tables do not store raw IP addresses. Reports and private contact messages are available to administrators for support and moderation.
3. Cookie、浏览器存储和日志 / Storage and logs
登录使用 HttpOnly Cookie；语言、匿名令牌及投票状态使用本地存储；草稿和浏览进度使用当前标签页的 sessionStorage。服务故障记录状态、时间和错误编号，我们的诊断代码不发送密码、邮箱、正文或重置凭证。Cloudflare 等基础设施仍可能产生网络日志。
HttpOnly cookies maintain sessions. Local storage keeps language and anonymous activity; session storage keeps per-tab drafts and browsing progress. Diagnostic events use status, time and error references, not passwords, emails, post bodies or recovery tokens. Infrastructure providers may process network logs.
4. 服务供应商和用途 / Providers and purposes
Cloudflare 托管网站与故障日志；启用 Turnstile 后，提交操作还会使用其安全验证，Cloudflare 会处理验证所需的浏览器及网络信息。Supabase 提供数据库与账号服务，Resend 发送验证、重置和账号通知邮件。数据用于提供功能、防刷、审核、账号恢复与支持，可能由供应商在其他地区处理。广告目前默认关闭；开启 AppLixir 时将展示广告相关说明和平台提供的隐私选择。
Cloudflare hosts the site. When Turnstile is enabled, Cloudflare also processes browser and network information for submission security checks. Supabase provides data and authentication, and Resend sends account emails. Providers may process data in other regions. We use data for site features, abuse prevention, moderation, account recovery and support. Reward ads are disabled by default; enabling AppLixir introduces the disclosed ad-provider data processing.
5. 保留、删除与申请 / Retention and requests
登录用户可在个人中心输入当前密码，确认永久删除账号。删除登录记录、会话、收藏、提醒和发布额度后，已发表内容保留并解除账号关联；正文中自行填写的个人资料不会自动改写。为防止删除前已在途的登录重新建立账号，系统保留不含邮箱的私有已删除账号编号。联系申请、审核记录、日志及备份按实际保留政策处理。屏蔽功能在服务器内部匹配作者，作者账号或匿名标识不会对外公开。
Signed-in users can permanently delete their account from their private space after confirming their current password. Credentials, sessions, bookmarks, notifications and publishing balances are removed. Published content remains without an account link; personal details in its text are not automatically rewritten. A private deleted-account identifier without an email address prevents in-flight logins from recreating the account. Contact requests, moderation records, logs and backups follow applicable retention policies. Blocking matches authors internally without exposing their account or anonymous identifiers.
账号、公开内容、审核及联系记录会保留以提供服务及处理争议，直到被删除或不再需要。过期会话及限流记录在后续相关操作时清理；隐藏内容仍保存在数据库以便审核和恢复。备份及供应商日志可能在各自保留期内继续存在。你可申请查询、更正或删除数据，运营团队需核实账号归属及申请范围。以前的游客投稿不会因提供公开编号而自动归属某个账号。
Accounts, content, moderation and contact records are retained for service and dispute handling until deleted or no longer needed. Expired session and rate-limit records are cleaned during subsequent operations. Hidden content remains for moderation and restoration. Backups and provider logs follow their retention periods. Access, correction and deletion requests require ownership and scope verification. A public post reference does not establish ownership of a guest post.
6. 联系与更新 / Contact and updates
请勿在投稿或留言中填写密码、验证码或他人的敏感资料。政策更新会在本页标注日期。隐私和删除申请请前往 联系我们 / Contact us。