数据驻留与出境Data Residency and Cross-border Transfer

驻留讲存储位置，由配置决定；出境讲传输的合法路径，由法律决定。开了同一个区域开关，不等于有出境合法依据。

云端的驻留通常是可选项：AWS 的数据隐私问答写明由客户选择内容存储在哪个区域，并声明未经客户同意不会把内容移出或复制到所选区域之外。

欧盟侧的机制是合同：欧委会提供预先批准的标准合同条款（SCC），用于向第三国转移个人数据。

中国侧的机制是申报评估：《数据出境安全评估办法》第四条列举应当申报的情形，包括向境外提供重要数据，以及关键信息基础设施运营者或处理一百万人以上个人信息的数据处理者向境外提供个人信息。

自建部署把出境问题挪了位置：提示词和日志留在本地，但模型的权重、更新源、以及你调用的任何外部服务（向量库、监控、第三方 API）仍可能在另一个辖区。

Residency is about storage location and is a configuration decision. Cross-border transfer is about the lawful route and is a legal decision. Picking a region does not by itself give you a basis for exporting data.

In the cloud, residency is usually a choice you make: AWS's data privacy FAQs state that the customer chooses the region where content is stored, and that AWS will not move or replicate content outside the chosen regions without the customer's agreement.

On the EU side the mechanism is contractual: the European Commission publishes pre-approved Standard Contractual Clauses for transfers of personal data to third countries.

On the China side the mechanism is a filed assessment. Article 4 of the Measures for Security Assessment of Outbound Data Transfers lists the situations that require a declaration, including providing important data abroad, and personal-information transfers by critical information infrastructure operators or processors of data on more than one million people.

Self-hosting moves the question rather than removing it: prompts and logs stay local, but weights, update sources and any external service you call - vector store, monitoring, third-party APIs - may still sit in another jurisdiction.