Does Miro Work in China? Data Residency, PIPL & Offshore Boards
Miro is reachable from mainland China, but the deciding question is data residency, not speed. Miro stores your boards and user data in offshore regions — the EU, US, Australia and (soon) Japan, none in mainland China — so the board content and accounts of your Chinese users sit offshore: a cross-border transfer PIPL governs. A compliance-first look at the data door.
Does Miro work in China?
Whether you can use Miro in China is first a data-residency question, not a speed one. Miro is a hosted whiteboard — the boards, their contents and the accounts that open them live on Miro's servers, and where those servers sit is what China's law responds to.
By Miro's own data-center residency documentation, storage is "Available in the European Union (default), United States, Australia, and Japan (coming soon)," and "Full storage of your data in Miro is available in your region of choice" — none of those regions is in mainland China. So the boards and user data of your China teams are held offshore: a cross-border transfer of personal information PIPL governs, needing notice, separate consent and a transfer mechanism, and for a CIIO or large-volume handler, in-country storage. The table below pairs Miro's own wording with the rule each point triggers.
This is a risk picture, not a verdict — your obligations turn on your data volumes and your role. Our China team can map your Miro exposure with you →
Compliance snapshot
- ! Reachable as a hosted service, but boards sync in real time to offshore servers across the border
- ! Stores boards, comments and user data in offshore regions (EU default; US, Australia; Japan coming soon)
- ! Board content and user PI held offshore is a cross-border transfer — PIPL applies
- ✕ No mainland-China region or data-residency option
- ✓ A compliant in-country delivery path exists — no rebuild, no migration
What Miro's own documentation says about China
| Fact | Primary source |
|---|---|
| In Miro's own words: data-center residency is "Available in the European Union (default), United States, Australia, and Japan (coming soon)," and "Full storage of your data in Miro is available in your region of choice." Every one of those regions is outside mainland China — the nearest live option, Australia, is still offshore — so the boards and accounts Miro keeps for your China users rest abroad. | Miro — Data Center Residency, retrieved 2026-10-07 |
| Miro stores personal information — the accounts and email addresses of members you invite, comments, and whatever your team writes or uploads onto a board — in whichever offshore region you select. Data gathered from users in China therefore leaves the country. PIPL governs that cross-border transfer: the personal-information handler (you, Miro's customer — not Miro) 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 using the tool: under the CAC's March 2024 cross-border rules, a non-CIIO transferring 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 mainland China (CSL Article 39 (formerly Article 37); PIPL Article 40). Miro publishes no mainland-China region, so the only way to keep your China users' board data on Chinese soil is to run that storage and its delivery on infrastructure inside the mainland — and standing that up legally is what brings an ICP filing into the picture. | PIPL Article 40; CSL Article 39 (formerly Article 37); Miro — Data Center Residency (regions offered), retrieved 2026-10-07 |
| Encryption is not data residency. Miro states "all customer content is encrypted in transit with TLS 1.3 protocol and at rest with AES 256 algorithm" — strong protection, but under PIPL the compliance question is where the data rests, not only how well it is guarded. Encrypted or not, boards stored in Miro's offshore regions are still held outside mainland China. | Miro — Data Center Residency, retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a team in mainland China, the deciding question about Miro is not how quickly a board loads — it is where the boards themselves, and the accounts that open them, are allowed to live. Miro is a hosted whiteboard: every board, its contents and every user you invite are stored on Miro’s own servers, in a region you pick from Miro’s published list. By Miro’s own documentation, not one of those regions is in mainland China. So a China-facing team on Miro can reach it, yet every board and account it keeps for your Chinese users is held offshore — a cross-border transfer China’s data law governs, not a performance problem. Because a Miro board is live and collaborative, it syncs continuously to that offshore region; but even a board that synced instantly would still rest abroad. Reaching Miro is not the issue; where it keeps your boards and your users is.
Miro in China at a glance
| What decides it | In Miro's own terms |
|---|---|
| Where your board data lives | Miro stores your content in a region you choose — storage is “Available in the European Union (default), United States, Australia, and Japan (coming soon).” None is in mainland China; the nearest live option, Australia, is still offshore. |
| The cross-border transfer | The boards, comments and accounts of users you add in China land in that offshore region. That is a cross-border transfer of personal information PIPL governs — and the handler is you, the Miro customer, not Miro. |
| When the rules bite harder | Exposure scales with volume and role. 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. |
| Data residency | For a CIIO or large-volume handler, personal information collected in China must be stored inside the mainland (CSL Article 39 (formerly Article 37); PIPL Article 40) — a duty no Miro region can meet. |
| Is it reachable? | Miro is a hosted whiteboard that syncs boards in real time to those offshore servers, so smooth collaboration rides on the cross-border path. Reaching it is a delivery question; where the boards and accounts live is the compliance one. |
Where your Miro boards and accounts actually live
Miro lets you choose where your content is stored, and publishes the regions it offers. In its own data-center residency material, storage is “Available in the European Union (default), United States, Australia, and Japan (coming soon),” and “Full storage of your data in Miro is available in your region of choice.” The European Union is the default; the United States and Australia are the other live choices, with Japan marked as coming.
That list settles the China question before performance is even on the table: it has no mainland-China entry. The closest region to the mainland — Australia today, or Japan once it opens — is still outside it. So the moment your team opens boards and invites users in China, the board content and the accounts Miro stores for them are kept abroad — and that, not latency, is what China’s data law responds to.
Open boards for China users and their data crosses the border
A Miro board is rarely just shapes on a canvas — it carries the names and email addresses of invited members, their comments, uploaded files, and whatever personal or business information your team writes onto it. All of it is written to the offshore region you selected. Under China’s Personal Information Protection Law, keeping that data outside the mainland is a cross-border transfer, and the obligation falls on the personal-information handler — you, as the Miro customer, not Miro as the platform. PIPL asks that handler to give affected users notice, obtain their separate consent for the transfer, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. “We already use Miro everywhere else” settles none of that; using a tool and being cleared to move Chinese users’ data out of the country are different questions.
How much is at stake depends on your volume and your role
The weight of these duties is not uniform. Under the CAC’s March 2024 Regulations on Promoting and Regulating Cross-border Data Flows, a handler that is not a critical information infrastructure operator and moves fewer than 100,000 individuals’ non-sensitive personal information in a calendar year is exempt from the security assessment, the standard contract and certification — a genuinely lighter path for a smaller rollout.
At the other end, a CIIO or a large-volume handler carries a data-residency duty: personal information collected in China must be stored inside the mainland (Cybersecurity Law Article 39 (formerly Article 37); PIPL Article 40). No Miro region can satisfy that, because none sits in China. Keeping your Chinese users’ board data on Chinese soil means running that storage and its delivery on infrastructure inside the mainland — and standing that up legally is what brings an ICP filing into the picture.
Reachable, but synced from offshore — which is why this is a data question
Miro is not among the services China categorically blocks. As a hosted whiteboard, though, it holds a live connection to its offshore servers so that a board updates in real time for everyone on it — which means smooth collaboration from inside the mainland rides entirely on the cross-border network path to those offshore regions. Whether a board loads and syncs cleanly is the delivery question, and it is a real one.
But that is the delivery half, not the compliance half. Even if every board painted and synced instantly, the boards and accounts would still be stored offshore — and that is the fact PIPL responds to. Encryption does not change it either: Miro states that “all customer content is encrypted in transit with TLS 1.3 protocol and at rest with AES 256 algorithm,” which protects the data in motion and at rest, but encryption secures data, it does not relocate it — under PIPL what matters is where the data comes to rest, not only how well it is guarded.
This is a risk map, not a verdict: whether you owe notice and consent only, a full transfer mechanism, or in-country storage of the board data itself turns on how much personal information you hold and whether your role pulls you into the CIIO or large-volume tier — worth working through with counsel before you commit.
Where 21YunBox fits — a compliant overlay, not a migration
Your team keeps working in Miro; your boards do not move. What we add is the layer a hosted whiteboard with no mainland region cannot provide on its own: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing origin — no re-architecture and no second tool to learn. Our China team first maps your cross-border and data-residency obligations against your entity and your data volumes. Then, for the strictest case — where Chinese users’ data has to stay on the mainland — we help you stand up the in-country delivery and storage a lawful China presence needs, while Miro stays exactly where your team already uses it.
Related reading:
Frequently Asked Questions
Does Miro store Chinese users' boards and data in China?
No. By Miro's own data-center residency documentation, storage is available in the European Union (default), the United States, Australia and Japan (coming soon) — none in mainland China. So the boards, comments and accounts of your China teams are held offshore, in whichever region you select.
Is it against the law to use Miro in China?
Not inherently. The issue is the cross-border transfer of personal information, which PIPL permits if you give notice, obtain separate consent and meet one of its transfer mechanisms. Whether you also face a data-localization duty depends on your role (for example, whether you are a CIIO) and the volume of personal information you handle. Treat this as a risk to assess with counsel, not a blanket prohibition.
Can 21YunBox help make our Miro setup compliant in China?
Yes. Our China team can help you assess the cross-border and data-residency exposure for your data volumes and role, and stand up the compliant, ICP-filed in-country delivery — and, where the law requires your China users' data to stay on the mainland, in-country storage. Get in touch to work through your specific case.
