← 返回官网首页隐私政策服务条款English

隐私政策 / Privacy Policy

适用仓库:codecloud-dev/mox-site(MoX 系列官网,部署于 Cloudflare Pages) 生效日期 / Effective date:2026-11-15 责任主体:codecloud-dev —— 一个 GitHub 个人账号,由个人开发者运营,不是公司、不是法人实体,没有公司名称、注册号、注册地址或客服电话。本文所称「我们」仅指该账号及其维护的这些公开仓库。

读法:中文在前,英文在后,同属一份文件。两份文字口径一致;若理解有歧义,以中文为准。 本政策只描述这个仓库当前代码里真实存在的行为。凡代码里没有实现的能力,一律写明「当前版本未实现 / 未收集」,不写成已有功能。 本政策按「最小必要、目的限定、公开透明」的口径撰写(参考 GDPR 与《个人信息保护法》的原则精神,不引用、不复制任何条文原文)。


一、这个网站是什么,会联网做什么

mox-site 是静态官网(HTML/CSS/JS)+ Cloudflare Pages Functions。它会发起或转发这些网络行为:

  1. 访客环境上报:每个页面经同源脚本 prefs.js 向 POST /site/presence 上报一组粗粒度枚举字段,供管理后台看「用什么设备、什么语言、什么主题访问」。
  2. 登录与账号:官网把 /auth/*、/me、/membership/*、/marketplace/*、/afdian/*、/account/*、/devices/*、/products/*、/fan/*、/contact/* 等同域请求反向代理到统一身份后端 mox-id(Cloudflare Workers)。登录走 GitHub OAuth / Gitee OAuth,会话用 mox_sid Cookie。
  3. 兑换与赞助:个人中心可用兑换码或爱发电订单号兑换商品授权;赞助入口链到爱发电。
  4. 留言 / 举报 / 投诉:/submit/message(需登录)与 /submit/report(可匿名)把内容转交 mox-id 存入工单台账;/submit/progress 凭一次性票据查进度。
  5. 人机验证:Cloudflare Turnstile,或服务端签发的 PoW 兜底挑战。
  6. 静态资源与镜像:国内网络时把 GitHub 主仓链接改写为 Gitee 只读镜像;赞助域可用性探测(/api/afdian-probe)。

二、我们收集什么(逐项与代码对齐)

2.1 访客环境上报 POST /site/presence

前端 prefs.js 构造的 payload 与后端 mox-id/src/site_presence.ts 的白名单逐字段一致;后端对任何多余字段一律 400 拒绝。

字段 取值 / 来源 为什么收集
anon_id 浏览器本地随机生成的 33 位十六进制串(以 a 开头),存于 localStorage 的 mox-presence-anon,可重置 统计「独立访客数」,不与任何账号关联
page 规范化页面路径(去掉 ?query 与 #hash,pretty URL 补回 .html) 统计各页面访问量
lang zh / en 语言分布
lang_source user / url / ip / browser / default 判断语言切换是否生效
country 两位国家码,来自 Cloudflare 边缘 CF-IPCountry 国内外分流与地区分布(只到国家,不到城市/坐标)
theme light / dark 主题偏好分布
theme_source user / system 判断深色模式是用户选的还是跟随系统
platform android / ios / windows / macos / linux / other,由平台名粗分 设备形态分布
form_factor mobile / tablet / desktop,由窗口宽度与 pointer: coarse 粗分 屏幕形态分布(不是精确尺寸)
client 固定 mox-site 标识上报来源
client_version 前端版本串,如 2026.11.12 区分版本
created_at 服务端时间(后端写入,不接受客户端时间) 统计时间线

明确不读取、更不上传(prefs.js 头部注释与 0024_site_presence.sql 均写明):IP 地址、User-Agent 原文、屏幕精确尺寸、时区、字体/画布指纹、referrer、URL query(可能带 code / token)、任何账号标识。IP 只在内存中参与限流,绝不落库;限流按 anon_id(30 条/分钟)与全局(2000 条/分钟)计数。管理后台展示时 anon_id 只显示前 8 位。

2.2 浏览器本地存储(留在你自己的设备上,不是上传给我们)

键 位置 内容
mox-lang、mox-lang-source、mox-country、mox-presence-anon localStorage 语言偏好、语言来源、国家码、匿名 ID
mox-theme localStorage 主题偏好
mox-presence-sent:* sessionStorage 「本页本次已上报」标记,防重复统计
mox_lang Cookie 用户显式选择的语言,Max-Age=31536000(1 年)、SameSite=Lax; Secure;自动判定不种 Cookie
mox_token localStorage 登录会话凭证(sid),与 mox_sid 同生命周期(30 天)
mox_sid sessionStorage(旧版兼容键) 旧兑换/绑定页的会话凭证,读到即迁移到 mox_token

mox_sid 会话 Cookie 由 mox-id 签发:HttpOnly; Secure; SameSite=Lax; Max-Age=2592000(30 天)。

2.3 登录与账号数据(由 mox-id 处理,官网只做同域反代)

  • GitHub OAuth:/auth/github/start → /auth/github/callback,scope read:user user:email;读取 api.github.com/user 与 /user/emails,取得 login、数字 id、name、avatar_url、主邮箱(primary+verified)。
  • Gitee OAuth:/auth/gitee/start → 回调,读取 gitee.com/api/v5/user 的 id / login / name / avatar_url / email。
  • Token 登录:POST /auth/token 用 GitHub access token 校验身份后建会话。
  • 一个账号可绑定 GitHub + Gitee 两个身份(/auth/<provider>/start?bind=1)。
  • 会话记录在 sessions 表:token_hash、device_id、创建/过期时间、last_active,以及「登录设备管理」页要展示的 ip、ua、device_label(ip 取 cf-connecting-ip,device_label 由后端从 UA 归一化,不信任前端传入)。

请注意这个区分:/site/presence 访客上报绝不收集 IP/UA 原文;但已登录用户的会话管理按 0017_account_center.sql 确实会在服务端会话行里记录 IP 与 UA,用于「我的登录设备」列表和踢出设备。这是两条不同的数据流,本文不混为一谈。

2.4 兑换、订单与设备

  • GET /devices:设备单选列表(device_token、name、platform、last_seen)。
  • POST /products/redeem:兑换码或爱发电订单号 out_trade_no 二选一 + device_token;后端校验订单真实已付且未被兑换过,写入 product_entitlements(user_id、product_id、device_token、source、out_trade_no、code、exp、status、rebinds)。
  • GET /products/entitlements、POST /products/rebind:我的授权、每月一次换绑。
  • GET /me/orders:订单流水 / 兑换记录 / 商品权益 / 已购插件。
  • GET /me/sessions、DELETE /me/sessions、POST /me/sessions/revoke-all:登录设备管理与退出。
  • DELETE /me:注销账号(硬删身份与私有数据、财务流水匿名化、写身份墓碑使同一 OAuth 身份无法再登录),不可恢复;钱包有余额时拒绝注销。

2.5 留言 / 举报 / 投诉(/submit/*)

边缘网关只放行白名单业务字段,人机凭证与其它夹带一律剥离:

字段 说明
subject 标题
body 正文(你主动填写的内容,请勿在其中粘贴密码等敏感信息)
lang zh / en
kind(仅举报) security(安全漏洞)/ conduct(行为准则投诉)
contact(仅举报,可选) 匿名提交者自愿留的联系方式,可空

mox-id 的 contact_messages 表存:ticket_hash(一次性票据的 SHA-256,明文票据只回给提交者一次)、user_id(0 = 匿名)、kind、subject、body、contact、lang、status、创建/更新时间、lookup_count。系统不自动采集 IP / UA / 设备信息,也不设独立邮箱字段;IP 只做哈希后参与分钟桶限流,不落库。例外:匿名举报时 contact 是可选自由文本,提交者可自愿填入任意联系方式(可能含邮箱),这段内容由提交者自己决定并存进该行;登录留言的 contact 固定写空串(见 2.5)。

2.6 人机验证与边缘限流

  • Turnstile 主通道:前端拿 /turnstile.js 下发的 sitekey 渲染,服务端用 TURNSTILE_SECRET 调 challenges.cloudflare.com/turnstile/v0/siteverify,请求里带 remoteip(客户端 IP)。即:验证令牌与 IP 会提交给 Cloudflare。
  • PoW 兜底通道:GET /contact 签发 2 分钟有效的挑战,nonce + 时间戳 + 客户端 IP 参与 HMAC-SHA256 签名;前端算 SHA-256 工作量证明,服务端重算校验。IP 只进签名与内存中的滑动窗口计数,不落库。
  • 边缘按 IP 内存计数限流:留言 8 次/分钟、匿名举报 5 次/分钟、进度查询 30 次/分钟。

2.7 其它

  • 赞助域探测 /api/afdian-probe:服务端依次 GET afdian.com / afdian.net / ifdian.net 的固定路径,带固定探针 UA,结果进 Cache API 缓存 2 分钟。不携带任何访客数据。
  • 国内外分流与语言切换:读 CF-IPCountry、Accept-Language、爬虫 UA 特征(仅用于跳过自动跳转,不用于画像或安全判定);/region.js 只下发两位国家码与语言枚举,绝不输出 IP 本身。

三、存多久、存哪、与谁共享

数据 存储位置 留存
site_presence 上报 mox-id 的 Cloudflare D1 数据库 90 天(site_presence.ts 的 RETENTION_MS,低概率触发清理);后台聚合查询最多回看 90 天
账号 / 会话 / 设备 / 订单 / 授权 mox-id Cloudflare D1;云同步大对象在 Durable Objects / KV 账号数据至你注销为止;会话 Cookie 30 天;注销后财务流水匿名化保留用于对账
留言 / 举报工单 mox-id Cloudflare D1 当前版本未实现自动过期删除,由管理员处理;可凭一次性票据查进度
语言 / 主题 / 匿名 ID / 会话 sid 你的浏览器本地(localStorage / sessionStorage / Cookie) 语言 Cookie 1 年;会话 30 天;匿名 ID 清除 localStorage 即重置
兑换码、订单号 提交给 mox-id 校验并入账 按订单/授权台账保留

共享方(均按各自条款独立处理,见第八节):

  • Cloudflare:Pages(静态托管 + Functions + _middleware)、Workers、D1、Durable Objects、KV、Cache API、Turnstile、边缘 CF-IPCountry。数据可能经其全球边缘网络处理。
  • GitHub:OAuth 登录、Token 校验、/user、/user/emails;主仓库与 Issues。
  • Gitee:OAuth 平行登录入口、国内只读镜像(gitee.com/codecloud-dev/...)。
  • 爱发电(afdian.com / afdian.net / ifdian.net):赞助入口、订单号查询与核销;我们不接收你的支付卡号、密码或支付账户凭据,只处理订单号。
  • mox-id:同属 codecloud-dev 的统一身份后端,是上述数据的实际处理者;本政策与其口径一致。

我们不出售、不出租、不用于广告画像、不向数据经纪人提供任何数据;当前版本未接入任何广告 SDK、统计 SDK 或第三方埋点。


四、我们明确不收集什么(当前版本)

  • 不读取或落库:IP 原文(仅 /site/presence;会话管理见 2.3 例外)、User-Agent 原文(同上)、屏幕精确尺寸、时区、字体/画布指纹、referrer、URL query 中的 code/token、任何账号标识(针对访客上报)。
  • 不收集:真实姓名、身份证号、手机号、精确地理位置、通讯录、短信、通话记录、相册、生物特征、广告标识符。
  • 不收集:你的终端命令内容、容器内文件内容、剪贴板内容、浏览历史(本官网不读取这些)。
  • 不收集:支付卡号、支付密码、邮箱 SMTP 授权码。
  • 当前版本未实现:用户画像、跨站追踪、行为广告、自动化决策、人脸识别、实名认证、年龄核验。
  • 本仓库无自有数据库;除上述反代到 mox-id 的字段外,官网前端不把数据发往任何我方服务器。

五、你能怎么查看、重置、删除

  • 重置匿名 ID 与偏好:清除本站 localStorage / Cookie,或在控制台调用 MoxPrefs.resetAnon();之后 anon_id 会重新随机生成。
  • 停止访客上报:当前版本未提供开关;上报不含可识别信息,且失败静默、不影响页面。如需彻底停用,请用浏览器扩展拦截 POST /site/presence。
  • 登录态:退出登录会清除 mox_token 与 mox_sid;mox_sid Cookie 30 天自动过期。
  • 登录设备:个人中心「登录设备」可查看、单踢、退出其他设备。
  • 账号与私有数据:个人中心 DELETE /me 注销账号(硬删 + 财务流水匿名化 + 身份墓碑),不可恢复。
  • 留言 / 举报:凭一次性票据在 /submit/progress 查进度;如需删除某条工单,请通过第九节的 GitHub Issues 提出。
  • 已上报的历史记录:site_presence 90 天后自动清理;如需按 anon_id 提前删除,请通过 GitHub Issues 说明该匿名 ID(前 8 位即可)。
  • GitHub 授权:在 github.com/settings/connections/applications/<client_id> 可撤销对 OAuth App 的授权;Gitee 同理在其账号设置中撤销。

六、儿童

本服务不面向未满 14 周岁的儿童,当前版本未实现年龄核验,不会有意收集儿童个人信息。若监护人发现儿童提交了留言、举报或联系方式,请通过 GitHub Issues 联系我们,我们会删除相关内容。

七、跨境

本站与 mox-id 运行在 Cloudflare 全球边缘网络,D1 / Durable Objects / KV 的数据可能在你所在国家/地区之外处理;GitHub、Gitee、爱发电、Cloudflare Turnstile 也各自按其条款在其所在地处理相应数据。我们未自建跨境传输机制,也不对这些第三方的数据留存地作承诺。

八、第三方服务条款入口(我们不为其背书)

只给出口,不代替它们解释、不担保其可用性、不对其行为负责。以各站最新公布的条款为准:

服务 条款 / 隐私政策入口
GitHub https://docs.github.com/en/site-policy/github-terms/github-terms-of-service · https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
Gitee https://gitee.com/(以其站内公布的《用户协议》《隐私政策》为准)
爱发电 https://afdian.com/(以其站内公布条款为准;备用域 afdian.net / ifdian.net)
Cloudflare https://www.cloudflare.com/privacypolicy/(及其站内公布的 Terms)

使用这些服务即同时受其条款约束;它们的收集行为不在本政策范围内。

九、变更通知与联系方式

  • 政策变更会直接更新本仓库的 PRIVACY.md,并在 Git 提交记录与官网 /changelog 中留痕;我们不向个人主动推送(不发邮件 / 短信 / 站内信),重大变更在仓库公告,请自行留意。已登录用户的 GitHub OAuth 主邮箱确按 2.3 节存储,但仅用于账号,不用于推送政策变更。
  • 唯一联系方式:在对应仓库开 GitHub Issues(https://github.com/codecloud-dev/<repo>/issues),或联系 GitHub 账号 codecloud-dev。
  • 我们不提供、也不在本文中编造客服邮箱、电话、通信地址、公司名或注册号。请勿把任何敏感信息(密码、令牌、订单凭据)直接贴在公开 Issue 里。

---

English

Repository: codecloud-dev/mox-site (MoX series official website, hosted on Cloudflare Pages) Effective date: 2026-11-15 Controller: codecloud-dev — a personal GitHub account run by an individual developer. It is not a company or legal entity; there is no company name, registration number, registered address, or support phone number. "We" in this document refers only to this account and the public repositories it maintains.

Chinese comes first, English follows, in the same file. Both versions describe the same practices; if there is a conflict in interpretation, the Chinese text controls. This policy describes only behaviour that actually exists in this repository's current code. Anything not implemented is explicitly marked "not implemented / not collected in the current version". Written in the spirit of data minimisation, purpose limitation and transparency (referencing the principles behind the GDPR and China's PIPL; no statutory text is quoted or copied).

1. What this site is and what it does online

mox-site is a static site (HTML/CSS/JS) plus Cloudflare Pages Functions. It makes or forwards these network requests:

  1. Visitor environment reporting: each page posts a set of coarse enumerated fields via prefs.js to POST /site/presence, so the admin console can show "what devices, languages and themes visitors use".
  2. Login and accounts: the site reverse-proxies same-origin /auth/*, /me, /membership/*, /marketplace/*, /afdian/*, /account/*, /devices/*, /products/*, /fan/*, /contact/* requests to the unified identity backend mox-id (Cloudflare Workers). Login uses GitHub OAuth / Gitee OAuth; sessions use the mox_sid cookie.
  3. Redemption and sponsorship: the account centre redeems product entitlements with a redeem code or an Afdian order number; the sponsor entry links to Afdian.
  4. Messages / reports / complaints: /submit/message (login required) and /submit/report (anonymous allowed) forward content to mox-id's ticket ledger; /submit/progress looks up status with a one-time ticket.
  5. Human verification: Cloudflare Turnstile, or a server-signed PoW fallback challenge.
  6. Static assets and mirrors: in mainland China, GitHub links are rewritten to a read-only Gitee mirror; sponsor-domain reachability probing (/api/afdian-probe).

2. What we collect (field-by-field, matched to the code)

2.1 Visitor environment reporting — POST /site/presence

The payload built by prefs.js matches the whitelist in mox-id/src/site_presence.ts field for field; the backend rejects any extra field with HTTP 400.

Field Value / source Purpose
anon_id A locally generated random 33-character hex string (starting with a), stored in localStorage as mox-presence-anon, resettable Count unique visitors; never linked to any account
page Canonical page path (query and hash stripped; pretty URLs normalised back to .html) Per-page visit counts
lang zh / en Language distribution
lang_source user / url / ip / browser / default Verify language switching works
country Two-letter country code from Cloudflare's edge CF-IPCountry Regional routing and distribution (country only, no city or coordinates)
theme light / dark Theme preference distribution
theme_source user / system User choice vs. system
platform android / ios / windows / macos / linux / other, coarsely derived from the platform name Device type distribution
form_factor mobile / tablet / desktop, coarsely derived from window width and pointer: coarse Screen form (not exact dimensions)
client Fixed mox-site Identify the reporting client
client_version Front-end version string, e.g. 2026.11.12 Version split
created_at Server time (written by the backend; client-supplied time is not accepted) Timeline

Explicitly never read or uploaded (stated in the prefs.js header and 0024_site_presence.sql): IP address, raw User-Agent, exact screen dimensions, timezone, font/canvas fingerprint, referrer, URL query (which may carry code / token), and any account identifier. The IP participates in rate limiting in memory only and is never persisted; limits are per anon_id (30/min) and global (2000/min). The admin console shows only the first 8 characters of anon_id.

2.2 Browser-local storage (stays on your device, not uploaded)

Key Location Content
mox-lang, mox-lang-source, mox-country, mox-presence-anon localStorage Language preference, its source, country code, anonymous ID
mox-theme localStorage Theme preference
mox-presence-sent:* sessionStorage "already reported for this page" flag
mox_lang Cookie Explicitly chosen language, Max-Age=31536000 (1 year), SameSite=Lax; Secure; automatic detection does not set it
mox_token localStorage Login session credential (sid), same 30-day lifetime as mox_sid
mox_sid sessionStorage (legacy key) Legacy session credential on redeem/bind pages, migrated to mox_token on read

The mox_sid session cookie is issued by mox-id: HttpOnly; Secure; SameSite=Lax; Max-Age=2592000 (30 days).

2.3 Login and account data (handled by mox-id; the site only reverse-proxies)

  • GitHub OAuth: /auth/github/start → /auth/github/callback, scope read:user user:email; reads api.github.com/user and /user/emails for login, numeric id, name, avatar_url, and the primary verified email.
  • Gitee OAuth: /auth/gitee/start → callback; reads id / login / name / avatar_url / email from gitee.com/api/v5/user.
  • Token login: POST /auth/token verifies a GitHub access token, then creates a session.
  • One account can bind both a GitHub and a Gitee identity (/auth/<provider>/start?bind=1).
  • Sessions are stored in the sessions table: token_hash, device_id, creation/expiry, last_active, plus ip, ua, device_label used by the "my login devices" page (ip from cf-connecting-ip; device_label normalised server-side from the UA, never trusted from the client).

Note the distinction: /site/presence visitor reporting never collects raw IP/UA; but session management for logged-in users does store IP and UA in server-side session rows per 0017_account_center.sql, for the device list and remote sign-out. These are two different data flows and are not conflated here.

2.4 Redemption, orders and devices

  • GET /devices: device picker (device_token, name, platform, last_seen).
  • POST /products/redeem: redeem code or Afdian out_trade_no (either one) + device_token; the backend verifies the order was really paid and not already redeemed, then writes product_entitlements (user_id, product_id, device_token, source, out_trade_no, code, exp, status, rebinds).
  • GET /products/entitlements, POST /products/rebind: my entitlements; one rebind per month.
  • GET /me/orders: order / redemption / entitlement / purchased-plugin records.
  • GET /me/sessions, DELETE /me/sessions, POST /me/sessions/revoke-all: device management and sign-out.
  • DELETE /me: delete account (hard-delete identity and private data, anonymise financial records, write an identity tombstone so the same OAuth identity cannot sign in again) — irreversible; a non-empty wallet blocks deletion.

2.5 Messages / reports / complaints (/submit/*)

The edge gateway forwards a strict business-field whitelist and strips captcha tokens and anything else:

Field Meaning
subject Title
body Body (content you write; please do not paste passwords or secrets)
lang zh / en
kind (reports only) security / conduct
contact (reports only, optional) Contact detail voluntarily left by an anonymous reporter; may be empty

mox-id's contact_messages table stores ticket_hash (SHA-256; the plaintext ticket is shown once to the submitter), user_id (0 = anonymous), kind, subject, body, contact, lang, status, timestamps, lookup_count. The system does not automatically collect IP / UA / device info and has no dedicated email field; the IP is hashed for per-minute rate limiting only and never persisted. Exception: for anonymous reports, contact is an optional free-text field where the reporter may voluntarily enter any contact detail (possibly including an email), and that user-supplied text is stored in the row; for logged-in messages contact is always an empty string (see §2.5).

2.6 Human verification and edge rate limiting

  • Turnstile: the front end renders with the sitekey from /turnstile.js; the server calls challenges.cloudflare.com/turnstile/v0/siteverify with remoteip (the client IP). The verification token and IP are therefore submitted to Cloudflare.
  • PoW fallback: GET /contact issues a 2-minute challenge; nonce + timestamp + client IP are covered by an HMAC-SHA256 signature; the client computes a SHA-256 proof of work and the server re-verifies. The IP only enters the signature and an in-memory sliding window, never storage.
  • In-memory per-IP edge limits: 8 message attempts/min, 5 anonymous reports/min, 30 progress lookups/min.

2.7 Other

  • /api/afdian-probe: the server GETs a fixed path on afdian.com, afdian.net, ifdian.net in turn with a fixed probe UA; the result is cached 2 minutes in the Cache API. No visitor data is included.
  • Region routing and language switching read CF-IPCountry, Accept-Language, and crawler UA patterns (only to skip auto-redirects; not for profiling or security decisions). /region.js emits only a two-letter country code and language enums, never the IP itself.

3. Retention, location, and sharing

Data Where Retention
site_presence reports mox-id Cloudflare D1 90 days (RETENTION_MS in site_presence.ts, probabilistically triggered cleanup); admin aggregates look back at most 90 days
Accounts / sessions / devices / orders / entitlements mox-id Cloudflare D1; large sync objects in Durable Objects / KV Account data until you delete the account; session cookie 30 days; after deletion financial records are kept anonymised for reconciliation
Message / report tickets mox-id Cloudflare D1 No automatic expiry in the current version; handled by the admin; status can be checked with the one-time ticket
Language / theme / anon ID / session sid Your browser (localStorage / sessionStorage / Cookie) Language cookie 1 year; session 30 days; anon ID resets when localStorage is cleared
Redeem codes, order numbers Submitted to mox-id for verification and ledgering Retained with the order/entitlement ledger

Recipients (each acts under its own terms; see §8):

  • Cloudflare: Pages (static hosting + Functions + _middleware), Workers, D1, Durable Objects, KV, Cache API, Turnstile, edge CF-IPCountry. Data may be processed across its global edge network.
  • GitHub: OAuth, token verification, /user, /user/emails; canonical repository and Issues.
  • Gitee: parallel OAuth login and the mainland-China read-only mirror.
  • Afdian (afdian.com / afdian.net / ifdian.net): sponsor entry, order-number lookup and reconciliation. We never receive your card number, payment password, or payment-account credentials — only the order number.
  • mox-id: the unified identity backend, also under codecloud-dev, and the actual processor of the above data; this policy is consistent with it.

We do not sell, rent, use for advertising profiling, or provide to data brokers any data. The current version includes no ad SDK, analytics SDK, or third-party tracking.

4. What we explicitly do not collect (current version)

  • Never read or persist (for /site/presence): raw IP (see the §2.3 exception for sessions), raw User-Agent, exact screen dimensions, timezone, font/canvas fingerprint, referrer, code/token in URL queries, any account identifier.
  • We do not collect: real name, government ID, phone number, precise location, contacts, SMS, call logs, photo library, biometrics, advertising identifiers.
  • We do not collect: your terminal command contents, container file contents, clipboard contents, or browsing history (this site does not read them).
  • We do not collect: card numbers, payment passwords, or SMTP authorisation codes.
  • Not implemented in the current version: profiling, cross-site tracking, behavioural advertising, automated decision-making, face recognition, real-name verification, age verification.
  • This repository has no database of its own; apart from the fields proxied to mox-id above, the front end sends nothing to any server of ours.

5. How to view, reset and delete

  • Reset anon ID and preferences: clear this site's localStorage / cookies, or call MoxPrefs.resetAnon() in the console; a new anon_id is then generated.
  • Stop visitor reporting: no toggle exists in the current version; the report carries no identifying data and fails silently. To disable it completely, block POST /site/presence with a browser extension.
  • Login state: signing out clears mox_token and mox_sid; the mox_sid cookie expires after 30 days.
  • Login devices: the account centre lets you list, sign out a single device, or sign out all other devices.
  • Account and private data: DELETE /me in the account centre (hard delete + anonymised financial records + identity tombstone), irreversible.
  • Messages / reports: check status with the one-time ticket at /submit/progress; to delete a ticket, open a GitHub Issue (§9).
  • Historical presence rows: auto-purged after 90 days; to request earlier deletion, open a GitHub Issue quoting the anon ID (first 8 characters suffice).
  • OAuth grants: revoke the GitHub OAuth App at github.com/settings/connections/applications/<client_id>; revoke Gitee in its account settings.

6. Children

The service is not directed at children under 14. The current version has no age verification and does not knowingly collect children's personal information. If a guardian finds a child has submitted a message, report, or contact detail, contact us via GitHub Issues and we will delete it.

7. Cross-border transfers

This site and mox-id run on Cloudflare's global edge network; D1 / Durable Objects / KV data may be processed outside your country. GitHub, Gitee, Afdian and Cloudflare Turnstile each process their respective data under their own terms and in their own locations. We have not built a bespoke cross-border transfer mechanism and make no promise about third-party data locations.

8. Third-party terms (we do not endorse them)

Entry points only. We do not interpret, guarantee availability, or take responsibility for them. The latest published terms on each site govern:

Service Terms / privacy policy
GitHub https://docs.github.com/en/site-policy/github-terms/github-terms-of-service · https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
Gitee https://gitee.com/ (see its published User Agreement / Privacy Policy)
Afdian https://afdian.com/ (see its published terms; fallback domains afdian.net / ifdian.net)
Cloudflare https://www.cloudflare.com/privacypolicy/ (and its published Terms)

Using these services also binds you to their terms; their collection practices are outside this policy.

9. Changes and contact

  • Changes update this repository's PRIVACY.md directly and are visible in Git history and the site's /changelog. We do not proactively notify individuals (no email / SMS / in-app messages); significant changes are announced in the repository, so please check back. Logged-in users' GitHub OAuth primary email is indeed stored per §2.3, but is used for the account only, not for policy-change push notifications.
  • Only contact channels: open a GitHub Issue at https://github.com/codecloud-dev/<repo>/issues, or reach the GitHub account codecloud-dev.
  • We do not provide, and do not invent here, any support email, phone number, postal address, company name, or registration number. Please do not post secrets (passwords, tokens, order credentials) in a public Issue.

10. Fenestra commercial signature records

The signing page at /commercial uses the same MoX session as the rest of the site. Submitting the agreement calls POST /commercial/sign on mox-id, which stores your account id, login, contact-email snapshot, chosen plan (monthly / yearly), the price snapshot shown at signing time, agreement_version, an optional company/entity name and note, status (awaiting_payment by default), and timestamps. No IP address, user agent, card number, payment password, or payment credential is stored. Prices and the payment entry are administrator-configured; the page does not invent an amount and refuses to sign while prices are not published.

A signature record is not a commercial licence. It records that you accepted the agreement; authorisation takes effect only after payment and a system-issued credential stating entity, scope, plan and dates. You can review your own records on the signing page (GET /commercial/mine). To request deletion, open a GitHub Issue as described in §9.

© 2026 MoX · 隐私政策 / Privacy Policy · 服务条款 / Terms · Fenestra 商业授权