Fable
The warehouse boundary and the truck transit
Old Zheng runs a multinational logistics business and has warehouses in three countries. Each country's warehouse stores information on local customers' goods. Old Zheng thinks he is doing well on compliance: each country's data is stored in its own local data center and never mixed together.
One day, the data analysis team at headquarters raised a request: could the operational data from warehouses in three countries be aggregated onto the headquarters server for a global efficiency analysis? The headquarters server was located in Country A, but the three warehouses were in Country A, Country B, and Country C respectively. Old Zheng said yes—after all, the data belonged to the company anyway.
After the legal team received the request, they called an emergency halt. Legal drew two diagrams on the whiteboard. The first showed warehouses in three countries, with each warehouse's data stored locally—this is called data residency. The regulations of Country B and Country C explicitly require that certain data involving their citizens must be stored on servers within their borders, regardless of whether the company is the data owner. Lao Zheng had never had a problem on this front because he had never moved data across national borders before.
The second diagram shows Country A's headquarters servers and three trucks departing from Country B and Country C. Legal said: what you need to do now is cross-border data transfer—moving data from Country B and Country C to Country A. Data residency governs where the warehouse is built; cross-border transfer governs whether trucks can leave the border and what procedures are required. The two are approved by different authorities and require different submissions.
Old Zheng then understood that what he had previously done—'store all data locally'—only satisfied the data residency requirement, but that did not mean he could freely move data out of the country. Residency is a fixed line of defense—where data is placed. Cross-border transfer is a flow line of defense—whether data can move and what conditions must be met for movement.
Legal helped Old Zheng work out a process: first confirm the legal basis for cross-border transfer separately in Country B and Country C—whether standard contractual clauses were signed, whether an adequacy decision applies, or whether case-by-case approval is required. Once the basis is established, conduct a data transfer impact assessment. Finally, configure access controls on the headquarters server to ensure data coming across borders is not forwarded again to unauthorized countries.
Old Zheng went through this process once. Country B approved it, and Country C required that the headquarters server must have a local mirror. The final solution was that data would not leave Country C, and the headquarters deployed an analysis node in Country C. Although it was not the originally envisioned "aggregate everything to headquarters," the compliance path became clear.
Later, Old Zheng told a colleague one thing: where the warehouse is located is a residency matter; whether a truck can cross the border is a cross-border transfer matter. Two checkpoints, two different sets of procedures.