首页Home/信任与合规Trust

信任是系统,不是一枚徽章。Trust is a system, not a badge.

这一页是我们愿意公开的全部事实:应用身份、数据流向、安全控制、以及三份对外发布的合规文件。没有「通过若干认证」这种说法,只有可以核对的东西。This page is everything we are willing to state publicly: app identity, data flows, security controls, and the three compliance documents we publish. No "certified to several standards" claims — only things you can check.

META APP ID 1626694105804782 DOCS VERSION v1.1 · 2026-11-16 RUNTIME Cloudflare Workers · D1 · R2 STATUS Published

应用身份App identity

谁在运营这个应用。Who operates the app.

Lumi Ads Platform 是我们自用的投放与结算控制台,通过 Meta Marketing API 管理客户授权的广告账户。以下信息与 Meta 应用后台、合规中心页面保持一致。Lumi Ads Platform is the buying and settlement console we run ourselves; it manages client-authorised ad accounts through the Meta Marketing API. The details below match the Meta app dashboard and our compliance pages.

Application
Lumi Ads Platform
Meta App ID
1626694105804782
运营主体Operating entity
杭州希望方舟网络科技有限公司Hangzhou Hope Ark Network Technology Co., Ltd.
控制台Console
合规中心Compliance center
安全联系Security contact
数据托管Data hosting
Cloudflare (Workers · D1 · R2 · Queues)
文档版本Document version
v1.1 · 2026-11-16

数据流向Data flow

数据从哪里来,到哪里去。Where data comes from, where it goes.

控制台只处理三类数据:你授权的广告账户数据、投放产生的报表数据、以及操作审计日志。我们不做数据转售,也不把客户数据用于训练模型。The console handles three classes of data: ad-account data you authorise, performance data produced by buying, and operator audit logs. We do not resell data or use client data to train models.

01 · Source 你的广告账户Your ad accounts 经 OAuth 授权,可随时撤销。Granted via OAuth, revocable at any time.
02 · Console Lumi Ads · Cloudflare 按工作区隔离存储,权限到人。Stored per workspace, permissioned per person.
03 · Action 渠道写入Channel writes 先鉴权与审计,再调用,最后回读。Authorise and log, then call, then read back.
04 · Output 报表与结算Reporting & settlement 回传至你的工作区,可导出。Returned to your workspace, exportable.

采集什么What we collect

广告账户 ID、campaign / ad set 结构与预算、素材、投放指标(曝光、点击、花费、CPI、ROAS)、结算与发票记录。个人层面只保留操作者身份用于审计。Ad account IDs, campaign and ad set structure, budgets, creative, performance metrics (impressions, clicks, spend, CPI, ROAS), settlement and invoice records. At the personal level, only the operator identity needed for audit.

不采集什么What we don't collect

不采集终端用户的实名信息、通讯录、精确位置或支付卡号。支付由持牌机构处理,我们不接触卡数据。No end-user real names, contact books, precise location or card numbers. Payments run through licensed providers; card data never reaches us.

保留多久Retention

投放与结算数据在合作期内保留,结束后 90 天内可导出并删除;审计日志按合规要求保留更长时间,且只追加不改写。Performance and settlement data persist for the engagement; after it ends you can export and delete within 90 days. Audit logs are retained longer as required, append-only.

安全控制Security controls

六道能验证的边界。Six boundaries you can verify.

身份与会话Identity & session

控制台通过 Cloudflare Access 统一登录,会话按工作区绑定,离职或撤权即失效。Console access runs through Cloudflare Access; sessions are bound to a workspace and die when access is revoked.

工作区隔离Workspace isolation

所有资源查询强制带工作区条件;权限范围为空时直接拒绝,不做静默过滤。Every resource query carries a workspace condition; an empty permission scope is refused outright, never silently filtered.

写入闸门Write gate

广告写入统一走一条链路:重验权限与渠道身份 → 记审计 → 调用渠道 → 读回真实结果,失败回滚。All ad writes take one path: re-check permission and channel identity, log, call the channel, read the real result back; roll back on failure.

审计Audit

操作者、规则、渠道响应与 request id 全量记录,只追加;可按工作区导出。Actor, rule, channel response and request id recorded in full, append-only, exportable per workspace.

存储与加密Storage & encryption

数据存于 Cloudflare D1 / R2,传输全程 TLS;素材为私有对象,读取必须鉴权。Data lives in Cloudflare D1 and R2 over TLS; creative objects are private and every read is authorised.

人工兜底Human override

自动化动作超出策略会停并在后台排队等人工确认;任何一步都能手动暂停全部投放。Actions outside policy stop and queue for human approval; any step can halt all buying manually.

合规文件Compliance documents

三份文件,公开发布。Three documents, publicly published.

为 Meta 应用审核发布,同样适用于任何客户尽调。文件位于独立的合规站,版本与日期可核对。Published for Meta app review, and equally valid for any client diligence. They live on the separate compliance site with a checkable version and date.

第三方处理Sub-processors

数据会经过谁。Who else touches it.

只列必要的几类:托管、渠道、支付、归因。每一类都签有数据处理条款,且只拿到完成该职能所需的最小数据。Only the necessary classes: hosting, channels, payments, attribution. Each is under data-processing terms and receives the minimum needed for its function.

ClassProvider
托管HostingCloudflare Workers · D1 · R2 · Queues
广告渠道Ad channelsMeta · Google · TikTok · Apple Search Ads
支付Payments持牌收单与本地支付机构Licensed acquirers and local payment providers
归因AttributionMMP postback 与 SKAN 4MMP postbacks and SKAN 4
访问控制AccessCloudflare Access

尽调Diligence

需要更细的材料?Need the deeper file?

数据流清单、权限矩阵、子处理方列表与最近一次安全检查记录,可在保密协议下提供。写邮件说明你的场景即可。Data-flow inventory, permission matrix, sub-processor list and the latest security review are available under NDA. Write with your scenario and we will send the pack.