Does Matterport Work in China? Reachability, Data Residency & the Embedded Tour
Matterport hosts your 3D digital twin and streams its viewer from offshore AWS — there is no mainland-China region — so a China-embedded tour loads across the border and your spatial captures and user data sit outside the mainland under PIPL. A compliance-first look at reachability, data residency and the ICP question.
Does Matterport work in China?
Whether you can use Matterport in China is first a delivery-and-data-residency question, not a speed one. Matterport hosts your 3D "digital twin" and streams its interactive viewer and the heavy capture assets from its own offshore cloud — and where that cloud sits is what China's law responds to, and what decides whether an embedded tour loads cleanly for mainland visitors.
By Matterport's own trust documentation, "The Matterport infrastructure is hosted within Amazon's AWS ecosystem," and it engages sub-processors "located in the United States and Australia" — none in mainland China. Two things follow for a China audience: the viewer and the multi-megabyte 3D assets cross the border to load, so a tour is reachable but can be slow to start or fail to finish; and the spatial captures plus any personal data they contain are held offshore — a cross-border transfer of personal information PIPL governs. The table below is Matterport's own wording and the rules it triggers.
This is a risk picture, not a verdict — your obligations turn on what you capture, your data volumes and your role. Our China team can map your Matterport exposure with you →
What Matterport's own documentation says about China
| Fact | Primary source |
|---|---|
| In Matterport's own words: "The Matterport infrastructure is hosted within Amazon's AWS ecosystem," and Matterport "engages with first and third-party Sub-processors located in the United States and Australia." Data is encrypted in transit and "at rest within the databases" — but none of that infrastructure sits in mainland China. Your digital twins and the viewer that serves them are hosted and delivered from offshore. | Matterport — Trust (Data center security; Sub-processors; Encryption), retrieved 2026-10-07 |
| Because the captures, account records and any personal data they contain live on that offshore infrastructure, data gathered from users in China leaves the country. PIPL governs that cross-border transfer: the personal-information handler — you, Matterport's customer, not Matterport — must give notice, obtain separate consent, and satisfy one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. | PIPL Chapter III, Articles 38–43 |
| The exposure scales with volume and role, not merely with embedding a tour: under the CAC's March 2024 cross-border rules, a non-CIIO moving fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, standard contract and certification. | CAC — Regulations on Promoting and Regulating Cross-border Data Flows, March 2024 |
| For a CIIO or large-volume handler, personal information collected in China must be stored inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Matterport publishes no mainland-China region, so keeping your China users' captures and data on Chinese soil means running that storage and delivery on infrastructure inside the mainland — which is where an ICP filing enters the picture. | PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| Matterport is almost always embedded in your own website. A public-facing site served to mainland visitors turns on an ICP filing tied to a mainland hosting resource (State Council Order No. 292; MIIT Order No. 33). Matterport runs no mainland region and offers no ICP-filing path of its own, so the filing — and the in-country delivery an embed needs to load cleanly — has to be arranged separately. | State Council Order No. 292; MIIT Order No. 33, reviewed 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about Matterport is not how sharp the 3D looks — it is whether the tour will load across the border, and where the scan and the data behind it are allowed to live. Matterport answers the hosting question in its own trust documentation: its infrastructure runs within Amazon’s AWS ecosystem, with sub-processors in the United States and Australia and no region inside mainland China. A tour embedded on a China-facing page is therefore reachable but served entirely from offshore — which carries the heavy 3D assets across a long border hop, leaves your captures and user data outside the mainland under PIPL, and gives the host page no ICP footing of its own. The picture loads; the delivery and the data residency are the exposure.
Matterport in China at a glance
| What decides it | In Matterport's own terms |
|---|---|
| Where it runs | “The Matterport infrastructure is hosted within Amazon's AWS ecosystem,” across AWS regions and availability zones. No region is inside mainland China. |
| Who processes the data | Matterport “engages with first and third-party Sub-processors located in the United States and Australia” — both offshore, neither in the mainland. |
| Serving the tour | The viewer and the multi-megabyte 3D capture assets stream from that offshore cloud, so an embedded tour crosses the border on every load. It is reachable, but can be slow to start — or fail to finish — for mainland visitors. |
| Your captures & user data | Spatial scans, account records and any personal data they contain sit offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore storage cannot meet. |
| The embedding site | A public site served to mainland visitors needs an ICP filing tied to a mainland host. Matterport runs no mainland region and provides no ICP-filing path of its own. |
Reachable, not blocked — but served from offshore
Matterport is not blocked in China. The difficulty is distance and weight: the interactive viewer and the assets behind a tour — the mesh, the panorama tiles, the player code — all stream from Matterport’s offshore AWS cloud. Embedded on a China-facing page, every one of those requests makes a long cross-border hop, so the tour is reachable but can be slow to initialize and, when an offshore dependency stalls, can fail to finish loading for mainland visitors. That is a delivery problem whose cause is network distance — not the compliance question, and not something tuning on the offshore side resolves.
No mainland region, so your captures and user data stay offshore
Matterport states that its infrastructure is “hosted within Amazon’s AWS ecosystem,” with sub-processors “located in the United States and Australia.” Not one of those is in mainland China. That geography settles the data question before performance ever enters it. A Matterport capture is personal- and property-related data — a dimensional scan of a real interior, usually with account and viewer records attached — and serving or storing it from AWS in the US or Australia keeps the data of your Chinese users outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, not Matterport — must give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty no offshore AWS region can satisfy.
The page that embeds the tour still needs its own ICP filing
Matterport is almost always embedded in someone else’s website, and that host page is where the second door sits. A public-facing site delivered to mainland visitors from inside China turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, attached to a hosting resource physically located in the mainland. Matterport runs no mainland region, so there is nothing on Matterport to file against and nothing that puts the embed itself in-country. “We already use Matterport” therefore does not carry into China: reaching the tour is not the same as being cleared to serve it, and the mainland footing a filing needs has to come from somewhere other than the offshore platform.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both — and how a detailed site scan should be handled for your particular premises — depends on what you capture, how much personal data you hold, and who your users are. It is worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep capturing and hosting on Matterport. We add the piece an offshore platform cannot: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing site and its embedded tour — no rebuild, no second codebase, and no move off Matterport. Our China team maps your ICP and data-residency obligations against your entity and data volumes, then stands up the in-country delivery and, where the law requires it, the storage a lawful China presence needs — so the tour loads cleanly for mainland visitors while your captures stay exactly where they already live.
Related reading:
