Does Zendesk Work in China? Data Residency, PIPL & Your Support Data
Zendesk runs no data center inside mainland China — its own docs host Service Data only in the US, the EEA, the UK, Japan and Australia — so every ticket, chat and contact you keep for Chinese users is stored offshore, a cross-border transfer PIPL governs. A compliance-first look at Zendesk data residency in China.
Does Zendesk work in China?
Yes — Zendesk loads in mainland China, but loading was never the question. Zendesk runs no data center inside the mainland, so every ticket, chat transcript and contact record you keep for Chinese users is stored offshore — and under China's privacy law that storage, not the speed, is the exposure.
Zendesk's own hosting-locations document lists every region it stores Service Data in — "US East (Northern Virginia), US East (Ohio), US West (Oregon), EEA (Ireland), EEA (Frankfurt), UK (London), Asia-Pacific (Tokyo), Asia-Pacific (Osaka), Asia-Pacific (Sydney)" — and none is in mainland China. Even its paid Data Center Location Add-On only pins data to "the United States, the European Economic Area, the United Kingdom, Japan (Tokyo or Osaka), or Australia." So support data from your Chinese users crosses the border to one of those regions — a cross-border transfer of personal information PIPL governs, on infrastructure that cannot be ICP-filed. The table below is Zendesk's own wording and the rule each line triggers.
This is a risk map, not a verdict — which duties bite turns on your data, your volumes and who your users are. Our China team can map your exposure with you →
Compliance snapshot
- ! Zendesk has no mainland-China region — your support data is stored offshore
- ! Tickets, chat transcripts and contacts are personal data; PIPL governs the transfer
- ✕ Even Zendesk's Data Center Location add-on has no mainland-China option
- ! For a CIIO or large-volume handler, that data must be stored in China
- ✓ Zendesk is reachable from China — but that is the delivery half, not the legal one
What Zendesk's own documentation says about China
| Fact | Primary source |
|---|---|
| Zendesk stores your support data offshore — there is no mainland-China region. Zendesk's own hosting-locations document names every region it holds Service Data in: "US East (Northern Virginia), US East (Ohio), US West (Oregon), EEA (Ireland), EEA (Frankfurt), UK (London), Asia-Pacific (Tokyo), Asia-Pacific (Osaka), Asia-Pacific (Sydney)." None sits inside mainland China, and Zendesk adds that "we may move account data between regions without notice" — so you cannot assume your Chinese users' data even stays in the nearest offshore region. | Zendesk — Data Hosting Locations for Your Zendesk Service Data (support.zendesk.com), retrieved 2026-10-07 |
| Even Zendesk's paid data-residency option cannot pin your data to China. Zendesk commits to a hosting location only "where Subscribers have purchased our Data Center Location Add-On," and its Regional Data Hosting Policy says ticket, user and attachment data can be "Hosted in any Zendesk region (i.e., the United States, the European Economic Area, the United Kingdom, Japan (Tokyo or Osaka), or Australia)." Mainland China is not on that list, so the add-on relocates your cross-border transfer between offshore jurisdictions — it does not end it. | Zendesk — Regional Data Hosting Policy & Data Hosting Locations (support.zendesk.com), retrieved 2026-10-07 |
| Support tickets, chats and contacts are personal data, so holding them offshore is a cross-border transfer. Once your Chinese users' information lands in one of Zendesk's US, EU, UK, Japan or Australia regions, China's Personal Information Protection Law treats the move as a cross-border transfer: the handler — you, not Zendesk — must give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification) under PIPL Articles 38–43. | PIPL Articles 38–43 (cross-border transfer); Zendesk hosting-location docs, retrieved 2026-10-07 |
| For a CIIO or high-volume handler, offshore storage may be barred outright, not just regulated. Personal information collected in mainland China by a critical information infrastructure operator or a large-volume handler must be stored in the mainland (Cybersecurity Law Article 39 (formerly Article 37); PIPL Article 40). None of Zendesk's regions can meet that duty, because none is in China — and a public help center served to mainland visitors from offshore has no mainland hosting resource to attach an ICP filing to. | Cybersecurity Law Article 39 (formerly Article 37); PIPL Article 40 (data localization); State Council Order No. 292 & MIIT Order No. 33 (ICP); Zendesk hosting-location docs, retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the real question about Zendesk is not how quickly the agent workspace or the help center paints — it is where the personal data behind them is allowed to live. Zendesk answers that in its own documentation: it hosts Subscriber Service Data in the United States, the EEA, the UK, Japan and Australia, and runs no data center inside mainland China. Zendesk is reachable from the mainland, so the exposure is not that your team cannot open it — it is that every ticket, chat transcript and contact record you keep for Chinese users is stored offshore, which China’s privacy law treats as a cross-border transfer. Reachability is the easy half; data residency is the half that decides whether you may lawfully run it.
Zendesk in China at a glance
| What decides it | In Zendesk's own terms |
|---|---|
| Where it runs | Nine AWS regions — US East (Northern Virginia), US East (Ohio), US West (Oregon), EEA (Ireland), EEA (Frankfurt), UK (London), and Asia-Pacific (Tokyo, Osaka and Sydney). None is inside mainland China. |
| Data-residency option | The paid Data Center Location Add-On lets you pin data to “the United States, the European Economic Area, the United Kingdom, Japan (Tokyo or Osaka), or Australia.” Mainland China is not a choice. |
| What is stored | Tickets, users, attachments and chat conversations — the personal data of your Chinese customers — held in whichever offshore region above applies. |
| Your China users' data | Stored outside the mainland — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Is it reachable? | Yes — the agent interface and a hosted help center generally load from the mainland. The distance shows up as slower, less predictable delivery, not a block. |
No mainland region, so your support data lives offshore
Zendesk’s hosting runs on AWS, and Zendesk lists the regions itself: “US East (Northern Virginia), US East (Ohio), US West (Oregon), EEA (Ireland), EEA (Frankfurt), UK (London), Asia-Pacific (Tokyo), Asia-Pacific (Osaka), Asia-Pacific (Sydney).” Not one of them is in mainland China, and the company is explicit that it “may move account data between regions without notice” unless you buy a residency add-on. Even that add-on — the Data Center Location Add-On, the only setting under which Zendesk “makes commitments on the Hosting location of Subscriber’s Service Data” — stops short of China: ticket, user and attachment data can be “Hosted in any Zendesk region (i.e., the United States, the European Economic Area, the United Kingdom, Japan (Tokyo or Osaka), or Australia).” So however you configure it, the support data of your Chinese customers comes to rest outside the mainland. That is the fact the rest of the compliance question hangs on.
Tickets and chats are personal data — so PIPL is the gate
A support stack is a personal-data store by design: names, emails, order details, device identifiers, and whatever a customer types into a ticket or a live chat. When that information is collected from people in mainland China and stored in one of Zendesk’s offshore regions, China’s Personal Information Protection Law treats the storage as a cross-border transfer of personal information. The duty lands on you as the handler, not on Zendesk: you must give notice, obtain separate consent for the transfer, and clear one of the statutory mechanisms — a CAC security assessment, the CAC standard contract, or certification (PIPL Articles 38–43). If you are a critical information infrastructure operator, or you process personal information above the regulated volume thresholds, the law goes further and requires that data collected in China be stored in China (Cybersecurity Law Article 39 (formerly Article 37); PIPL Article 40) — a residency duty no US, EU, UK, Japanese or Australian region can satisfy.
Reachable, and a public help center raises a second door
Zendesk is not blocked in mainland China; the agent interface and a hosted help center generally load, though delivery can be slower and less predictable than a visitor expects. That reachability is worth stating plainly — but it is the delivery half of the question, not the legal half. One thing it does raise: if you publish a customer-facing help center to mainland visitors on your own domain, you are serving public web content into China, and a public site served to mainland users turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33 — a filing that must attach to a mainland hosting resource Zendesk does not provide. So both doors trace back to the same gap: Zendesk has nothing inside the mainland to file against or to keep data in.
This is a risk map, not a verdict: whether you face a cross-border-transfer duty, an in-country storage duty, an ICP filing, or all three depends on what you collect, how much of it, and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep running Zendesk exactly as you do today — same account, same agents, same workflows. What 21YunBox adds is the piece Zendesk has no region for: compliant, ICP-filed delivery from inside the mainland, set in front of the Zendesk endpoints your China users reach, so your help center and portals arrive over in-country infrastructure — with no rebuild and no second codebase. Our China team first maps the obligations that actually apply to you — the PIPL cross-border transfer, any data-localization duty, and the ICP filing a public help center needs — against your entity and your data volumes, then stands up the in-country delivery and the lawful data path a compliant China presence requires, while your Zendesk tenant stays where it already lives.
Related reading:
Frequently Asked Questions
Where does Zendesk store our customers' support data?
In AWS regions Zendesk names in its own documentation — US East (Northern Virginia and Ohio), US West (Oregon), the EEA (Ireland and Frankfurt), the UK (London), and Asia-Pacific (Tokyo, Osaka and Sydney). None is in mainland China, and even the paid Data Center Location Add-On only lets you pin data to the US, the EEA, the UK, Japan or Australia. So the tickets, chats and contact records of your Chinese users are held offshore — which is what makes it a cross-border transfer under PIPL.
Does the Zendesk Data Center Location add-on make us compliant in China?
No. The add-on lets you choose which Zendesk region holds your data, but mainland China is not one of the choices — the list is the US, the EEA, the UK, Japan or Australia. It can help satisfy EU or other residency requirements; it does not create a mainland-China storage location, so it removes neither the PIPL cross-border transfer nor any China data-localization duty. Treat it as a tool for other jurisdictions, not a China answer, and confirm your own obligations with counsel.
Can 21YunBox help us run Zendesk compliantly for China?
Yes. Our China team can map your exposure — the PIPL cross-border and data-residency obligations that attach to the tickets, chats and contact records Zendesk stores offshore, assessed for your entity, your data volumes and your users — and stand up the ICP-filed, in-country delivery a compliant China presence needs, in front of the Zendesk stack you already run. Get in touch to work through your specific case.
