[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-zh-/where-one-intermind-meeting-actually-runs":3},{"page":4,"surround":446},{"id":5,"title":6,"authors":7,"badge":10,"body":11,"date":436,"description":437,"extension":438,"image":439,"meta":440,"navigation":441,"path":442,"seo":443,"stem":444,"__hash__":445},"blog_zh/blog/where-one-intermind-meeting-actually-runs.md","一场 InterMIND 会议实际运行在何处",[8],{"name":9},"The Mind.com Team","Sovereignty",{"type":12,"value":13,"toc":425},"minimark",[14,18,27,30,33,36,41,44,54,57,59,62,65,178,181,183,186,348,351,353,357,364,371,374,382,385,387,391,394,401,407,409,412,422],[15,16,6],"h1",{"id":17},"一场-intermind-会议实际运行在何处",[19,20,21,22,26],"p",{},"每一场严肃的企业采购对话最终都会绕回到同一个问题:",[23,24,25],"em",{},"\"这些数据会去哪里?\""," DPO 想要一份子处理者清单。CIO 想知道哪些供应商注册在美国。法务想要一张带箭头的示意图。",[19,28,29],{},"与其分批通过邮件零散地告诉您,不如让您一次看到全貌。所以这里就是一场会议的数据路径——它所接触的每一项外部服务、各自在何处运行、以及哪些数据流经其中。已在 2026-05-28 对照实际部署配置进行核验。",[19,31,32],{},"其中有一条路径,供应商注册地目前仍在美国,我们也直说。其余部分在运行时均位于欧盟。",[34,35],"hr",{},[37,38,40],"h2",{"id":39},"在何处运行究竟意味着什么","\"在何处运行\"究竟意味着什么",[19,42,43],{},"在主权相关讨论中,有两件事常被混为一谈,但它们并不是同一回事:",[45,46,47,51],"ol",{},[48,49,50],"li",{},"**运行时 / 数据路径。**您会议的字节在请求过程中被实际处理的物理位置。这才是数据驻留法规和大多数 DPA 真正关心的对象。",[48,52,53],{},"**供应商公司注册地。**该 SaaS 供应商的法律注册地。这是 CLOUD Act 讨论关心的对象——即美国理论上可以对供应商母公司施加的强制力,无论实际工作负载在哪里运行。",[19,55,56],{},"几乎所有\"这是欧盟的吗?\"的问题,其实都是上述两者之一,只是问得不够精确。下文中我们对每一家供应商分别作答。",[34,58],{},[37,60,61],{"id":61},"一场会议的数据路径",[19,63,64],{},"让我们追踪一次通话,从加入会议到事后跟进邮件:",[45,66,67,79,86,97,104,114,128,138,152,164],{},[48,68,69,73,74,78],{},[70,71,72],"strong",{},"浏览器打开会议页面。"," SSR 在 Vercel 上运行,固定于 ",[75,76,77],"code",{},"fra1","(法兰克福)。所有请求/响应数据——会话 cookie、API 负载、服务端渲染的 HTML——在运行时均于欧盟内处理。",[48,80,81,82,85],{},"**WebSocket 连接到我们位于巴黎(",[75,83,84],{},"cdg",")的会议服务器。**会议编排、在线状态、信令——全部在欧盟。",[48,87,88,89,96],{},"**语音识别在发言者的浏览器中运行。**本地完成。在转写结果被送去翻译之前,从不离开设备。(我们在 ",[90,91,93],"a",{"href":92},"/blog/inside-the-translation-pipelines",[23,94,95],{},"翻译流水线内幕"," 中介绍了原因。)",[48,98,99,100,103],{},"**语音和聊天翻译进入我们部署在 OVH 法国的自有引擎。**这就是 ",[75,101,102],{},"mind-sdk-web","——我们的代码,我们的主机,位于法国。链路中没有任何第三方模型。亚秒级预算、按语言划分的 WebSocket 连接池、每一跳都在欧盟。",[48,105,106,109,110,113],{},[70,107,108],{},"拖入聊天的文档","(PDF、DOCX、PPTX、XLSX)从巴黎的 ws-server 服务端发送至位于科隆的 ",[70,111,112],{},"DeepL","。德国公司,德国境内处理。语音和聊天不会接触 DeepL。",[48,115,116,119,120,127],{},[70,117,118],{},"应用数据","——用户、团队、消息、会议元数据——存放于 ",[70,121,122,123,126],{},"AWS 法兰克福(",[75,124,125],{},"eu-central-1",")上的 Neon Postgres","。快照在同一区域。",[48,129,130,133,134,137],{},[70,131,132],{},"录像、附件、导出文件","存放于 ",[70,135,136],{},"Tigris",",基于 S3 兼容的对象存储,运行在 Fly 上。边缘复制;对于需要更严格固定区域的租户,存储桶可配置为多区域欧盟。",[48,139,140,143,144,147,148,151],{},[70,141,142],{},"错误与性能追踪","发送至 ",[70,145,146],{},"Sentry 的欧盟实例","(",[75,149,150],{},"de.sentry.io",")。美国组织已于五月停用。",[48,153,154,143,157,147,160,163],{},[70,155,156],{},"产品分析",[70,158,159],{},"PostHog EU",[75,161,162],{},"eu.i.posthog.com",")。",[48,165,166,169,170,173,174,177],{},[70,167,168],{},"事务性邮件","(魔法链接、邀请、收据)通过 ",[70,171,172],{},"Resend"," 自 ",[75,175,176],{},"eu-west-1","(爱尔兰)发出。",[19,179,180],{},"以上所有内容在运行时均位于欧盟。翻译引擎——您大部分数据真正流经的部分——也是我们自己的代码,这意味着对于有需要的客户,引擎本身可以被审计或自行托管。",[34,182],{},[37,184,185],{"id":185},"供应商一览",[187,188,189,205],"table",{},[190,191,192],"thead",{},[193,194,195,199,202],"tr",{},[196,197,198],"th",{},"供应商",[196,200,201],{},"用途",[196,203,204],{},"运行位置",[206,207,208,225,240,256,270,282,294,309,322,335],"tbody",{},[193,209,210,219,222],{},[211,212,213,147,216,218],"td",{},[70,214,215],{},"OVH",[75,217,102],{},")",[211,220,221],{},"语音 + 聊天翻译引擎",[211,223,224],{},"法国",[193,226,227,232,235],{},[211,228,229],{},[70,230,231],{},"Fly.io",[211,233,234],{},"会议 WebSocket 编排",[211,236,237,238,218],{},"巴黎(",[75,239,84],{},[193,241,242,248,251],{},[211,243,244,247],{},[70,245,246],{},"Vercel","(Nuxt + Nitro API)",[211,249,250],{},"应用外壳、服务端 API、SSR",[211,252,253,254,218],{},"法兰克福(",[75,255,77],{},[193,257,258,263,266],{},[211,259,260],{},[70,261,262],{},"Neon",[211,264,265],{},"应用 Postgres",[211,267,122,268,218],{},[75,269,125],{},[193,271,272,276,279],{},[211,273,274],{},[70,275,136],{},[211,277,278],{},"对象存储(录像、附件)",[211,280,281],{},"边缘复制;可固定于欧盟",[193,283,284,288,291],{},[211,285,286],{},[70,287,112],{},[211,289,290],{},"文档翻译(PDF/DOCX/PPTX/XLSX)",[211,292,293],{},"科隆",[193,295,296,301,304],{},[211,297,298],{},[70,299,300],{},"Sentry",[211,302,303],{},"错误追踪",[211,305,306,308],{},[75,307,150],{},"(欧盟)",[193,310,311,316,318],{},[211,312,313],{},[70,314,315],{},"PostHog",[211,317,156],{},[211,319,320],{},[75,321,162],{},[193,323,324,328,330],{},[211,325,326],{},[70,327,172],{},[211,329,168],{},[211,331,332,333,218],{},"爱尔兰(",[75,334,176],{},[193,336,337,342,345],{},[211,338,339],{},[70,340,341],{},"Stripe",[211,343,344],{},"支付",[211,346,347],{},"爱尔兰(Stripe Payments Europe Ltd.),面向欧盟客户",[19,349,350],{},"按数据量计算,最重的两条数据流——通过我们在 OVH 上的自有引擎进行的语音/聊天翻译,以及通过 DeepL 进行的文档翻译——其母公司也恰好都位于欧盟。这覆盖了会议内容的大部分。完整的子处理者清单及公司注册地详情,按惯例随 DPA 一并提供;上表呈现的是运行时视角,而这正是大多数数据驻留条款真正关心的内容。",[34,352],{},[37,354,356],{"id":355},"目前唯一的空白直说","目前唯一的空白,直说",[19,358,359,360,363],{},"通话结束后,我们会生成一份会后 ",[70,361,362],{},"AI digest","——议题、决策、行动项、待解决问题。生成 digest 的模型通过 Vercel 的 AI Gateway(一个欧盟区域的代理)接入,但底层模型是 Google Gemini 2.5 Flash,并以 Anthropic Claude Sonnet 作为回退——两者均为美国注册的供应商。",[19,365,366,367,370],{},"实时语音、实时聊天和文档翻译",[70,368,369],{},"不会","经过这条路径。digest 是一个独立的会后步骤,基于我们已经生成的转写文本,在其之上写出摘要。",[19,372,373],{},"我们正以两种方式来填补这一空白:",[45,375,376,379],{},[48,377,378],{},"**由所有者控制的退出开关,即将推出。**工作区所有者将能够完全禁用 AI digest 流水线,届时不会生成任何会后摘要,转写文本就停留在它原本所在的位置——欧盟内。对新租户默认关闭;现有租户会收到通知,如愿意可继续保持启用。",[48,380,381],{},"**自托管的欧盟摘要模型。**我们正在 OVH 上部署一个开源权重模型(Kimi 级别),用于摘要这类不需要前沿级推理能力的任务。一旦它成为 digest 的后端,这一权衡就不复存在——同一条流水线将不再涉及任何美国注册的供应商。",[19,383,384],{},"如果 digest 是您的采购评估中\"这套方案可行\"与\"不可行\"之间的分水岭,请告知我们——我们会据此调整优先级。",[34,386],{},[37,388,390],{"id":389},"这对您的-dpa-意味着什么","这对您的 DPA 意味着什么",[19,392,393],{},"对于大多数欧盟买家——德国 Mittelstand、运行标准 GDPR DPA 的受监管行业——上述图景直接回答了数据驻留问题:您的会议在运行时的每一跳都位于欧盟。供应商注册地按惯例在子处理者清单中披露;没有任何意外。",[19,395,396,397,400],{},"对于法国 ",[23,398,399],{},"souveraineté numérique"," 和 SecNumCloud 级别的采购,供应商公司注册地本身就是评估标准的一部分,而不仅仅是运行时位置。那是另一种对话——一种替代性的部署拓扑,使每一个组件都处于欧洲司法管辖的供应商之下。我们不会默认运行该拓扑;但对于确有此类需求并且合同足以支撑该建设的租户,我们会为其搭建。",[19,402,403,404,406],{},"对于美国本土以及大多数亚太地区买家而言,情况通常正好相反——他们希望从自己所在区域获得低延迟,这是另一个问题。今天我们以单区域方式运行于 ",[75,405,77],{},"。如果您的流量足以支撑美国边缘节点,我们会与您一起规划。",[34,408],{},[37,410,411],{"id":411},"这篇文章对我们的约束",[19,413,414,415,418,419,421],{},"这是 2026-05-28 时的图景。当技术栈发生变化时——供应商更换、区域迁移、新增外部服务——我们会更新。当前配置可以在我们开放的 ",[75,416,417],{},"vercel.json","、运行于 OVH 法国的 ",[75,420,102],{}," 引擎,以及每个供应商各自的控制台中得到核验。",[19,423,424],{},"如果这里有什么看起来不对,或者您的 DPO 需要这份图景没有给出的答案,请联系我们。我们宁愿补上一个遗漏的细节,也不愿让您在合同评审中才发现它。",{"title":426,"searchDepth":427,"depth":428,"links":429},"",2,3,[430,431,432,433,434,435],{"id":39,"depth":427,"text":40},{"id":61,"depth":427,"text":61},{"id":185,"depth":427,"text":185},{"id":355,"depth":427,"text":356},{"id":389,"depth":427,"text":390},{"id":411,"depth":427,"text":411},"2026-05-28","逐一梳理哪些外部服务会接触您的会议、它们在何处运行、以及哪些数据会流经其中。包括目前唯一一条在供应商层面仍会离开欧盟的路径——以及我们正在如何处理。","md","/blog/where-one-intermind-meeting-actually-runs.svg",{},true,"/blog/where-one-intermind-meeting-actually-runs",{"title":6,"description":437},"blog/where-one-intermind-meeting-actually-runs","L1Euk42U7kNZMkKkSehDq6f741DQtQTwR1N-1PBX6n8",[447,453],{"title":448,"path":449,"stem":450,"description":451,"order":452,"children":-1},"博客","/blog","blog/index","InterMIND 团队的最新消息和更新。",8,{"title":454,"path":455,"stem":456,"description":457,"children":-1},"虚假流利陷阱:当\"够用\"的英语比不会英语更糟糕","/blog/false-fluency-trap","blog/false-fluency-trap","航空监管机构在特内里费和阿维安卡空难之后强制要求改革。医学文献已将其量化到每次诊疗中的错误数量。四十年的国际商业研究记录了董事会会议室中的相同机制。为什么在共同语言上的部分流利,比完全没有共同语言更糟糕——附数据佐证。"]