Does Freshdesk Work in China? Data Residency, PIPL & an Offshore Help Desk
Freshdesk stores your support tickets, contacts and conversation history in offshore Freshworks data regions — US, EEA, UAE, India or Australia, none inside mainland China — so your China customers' personal data leaves the country under PIPL. A compliance-first look at the data-residency and ICP doors.
Does Freshdesk work in China?
Whether you can use Freshdesk in mainland China is first a data-residency question, not a speed one. Freshdesk is a help desk — it stores the support tickets, contact records and conversation history your customers send — and where Freshworks keeps that data is what China's law responds to.
By Freshworks' own documentation, its "Data Centres are located in: US, EEA, UAE, IND, AU," and "You can choose your preferred data location when you sign up for your account" — none of them in mainland China. So the tickets, profiles and conversation logs of your China customers come to rest offshore: a cross-border transfer of personal information PIPL governs, needing notice, separate consent, a transfer mechanism, and — for a CIIO or large-volume handler — in-country storage. Because support tickets can carry sensitive personal information, PIPL holds them to a higher bar. The table below is Freshworks' own wording and the rules it triggers.
This is a risk picture, not a verdict — your obligations turn on what your tickets contain, your data volumes and your role. Our China team can map your Freshdesk exposure with you →
Compliance snapshot
- ! Reachable, but the portal, agent app and help widget are served from an offshore region
- ! Tickets, contacts and conversation history are stored offshore (US, EEA, UAE, India or Australia)
- ! Those records cross the border — PIPL cross-border rules apply, more so for sensitive data in tickets
- ✕ No mainland-China data region to choose, and no ICP-filing path for a Freshworks-hosted portal
- ✓ A compliant, ICP-filed in-country path exists — no rebuild, no migration off Freshworks
What Freshdesk's own documentation says about China
| Fact | Primary source |
|---|---|
| In Freshworks' own words: "Our Data Centres are located in: US, EEA, UAE, IND, AU," and "You can choose your preferred data location when you sign up for your account." The region is fixed at signup, there is no mainland-China option to choose, and moving regions later means contacting Freshworks support — the nearest regions, India and the UAE, are still offshore. | Freshworks (Freshdesk) — Where are your data servers located, retrieved 2026-10-07 |
| Freshdesk holds personal information — names, email addresses, ticket contents and full conversation history — in whichever offshore region your account is assigned. Data collected from customers in China therefore leaves the country. PIPL governs that cross-border transfer: the personal-information handler (you, Freshworks' customer — not Freshworks) 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 |
| Support tickets routinely carry sensitive personal information — ID numbers, payment details, health or account complaints customers paste into a ticket or attachment. Under PIPL, sensitive personal information may be handled only for a specific purpose, with demonstrated necessity and separate consent (PIPL Articles 28–29), and moving it across the border raises the bar rather than lowering it. | PIPL Articles 28–29 |
| 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). Freshworks publishes no mainland-China region, so the only way to keep your China ticket data on Chinese soil is to run the collection and storage 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); Freshworks data-centre list, retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about Freshdesk is not how quickly the help widget paints — it is where your customers’ support data is allowed to live. Freshdesk is a help desk: it stores the tickets, contact records and conversation history your customers send, and Freshworks answers the question that settles compliance in its own documentation — that data sits in an offshore region, with none inside mainland China. The portal is reachable; the data residency and the cross-border transfer are the exposure.
Freshdesk in China at a glance
| What decides it | In Freshworks' own terms |
|---|---|
| Where the data lives | Five data regions — US, EEA (Europe), UAE (Middle East), India and Australia. “You can choose your preferred data location when you sign up,” but no region is inside mainland China; the nearest, India and the UAE, are still offshore. |
| What is stored | Support tickets, contact records, conversation history and knowledge-base content — personal information, and tickets can carry sensitive personal information such as ID numbers, payment details or health complaints. |
| Choosing the region | The data location is set at signup; there is no mainland-China option to pick, and moving to a different region later means contacting Freshworks support. |
| Serving the public | A branded portal or help widget served to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource. Hosted offshore by Freshworks, it offers no ICP-filing path of its own. |
| Your China data under PIPL | Personal information of Chinese users sits offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
Where your China customers’ tickets actually live
Freshworks states plainly where it keeps customer data. In its own support documentation its “Data Centres are located in: US, EEA, UAE, IND, AU,” and “You can choose your preferred data location when you sign up for your account.” Not one of those five regions is inside mainland China, the choice is fixed at signup, and there is no mainland option to pick — moving regions later means contacting Freshworks support.
That geography settles the data-residency question before performance ever enters it. Serve Chinese customers through Freshdesk and the tickets, profiles and conversation logs you collect from them come to rest in the United States, Europe, the Middle East, India or Australia. Under China’s Personal Information Protection Law that is a cross-border transfer of personal information, and the handler — you, Freshworks’ customer, not Freshworks — has to give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. That is where “we already run on Freshdesk” runs out: reaching China is not the same as being cleared to collect Chinese users’ data there.
Support tickets can carry sensitive personal information
A help desk is not a static asset like a font or a script — it is a funnel for whatever a customer types. Account recovery, billing disputes and medical or financial complaints routinely arrive with ID numbers, payment details and health information pasted into the ticket body or an attachment. PIPL holds that category — sensitive personal information — to a stricter standard: it may be handled only for a specific purpose, with demonstrated necessity and under separate consent (PIPL Articles 28–29), and sending it across the border raises the bar rather than lowering it. The more your queues collect, the heavier the obligation — and for a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (Cybersecurity Law Article 39 (formerly Article 37); PIPL Article 40), a residency duty none of Freshworks’ five offshore regions can satisfy.
A public help portal still turns on an ICP filing
If you publish a branded support portal or embed the Freshdesk help widget on a site served to mainland visitors from inside China, you are running a public internet information service — and that turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, a filing that must attach to a hosting resource physically inside the mainland. A Freshworks-hosted portal runs on offshore infrastructure, so there is nothing on it to file against. Tuning the stack does not create the mainland footing a filing needs.
Reachable is not the same as compliant
Freshdesk is not the kind of service that simply refuses to load in China — the exposure is quieter and more durable than a slow paint. Every ticket a mainland customer submits, and every help-widget asset the page pulls, is answered from that offshore region, so the data crosses the border by design, not by accident. Even if the portal opened instantly, using it would still place your China customers’ personal information outside the country. Where the data lives, not how fast it arrives, is what the law responds to.
This is a risk map, not a verdict: whether you need separate consent, a transfer mechanism, in-country storage, an ICP filing, or some combination depends on what your tickets contain, how much personal data you hold and who your customers are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep running on Freshdesk. We add the piece a help desk with no mainland region cannot: compliant, ICP-filed delivery from inside the mainland, set in front of your existing Freshworks portal — no rebuild, no second help desk, and no move off Freshworks. Our China team maps your PIPL cross-border and data-residency obligations against your entity, your ticket contents and your data volumes, then stands up the in-country delivery and, where the law requires your China customers’ data to stay on the mainland, the in-country storage a lawful China presence needs — while your agents keep working in the Freshdesk they already use.
Related reading:
Frequently Asked Questions
Does Freshdesk store Chinese users' ticket data in China?
No. By Freshworks' own documentation, its data centres are in the US, EEA, UAE, India and Australia, and you choose your region at signup — none is in mainland China. So your China customers' tickets, contacts and conversation history are held offshore, and there is no mainland region to select.
Is it against the law to use Freshdesk 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. Sensitive personal information in tickets, and any data-localization duty (for example if you are a CIIO or a large-volume handler), raise the bar further. Treat this as a risk to assess with counsel, not a blanket prohibition.
Can 21YunBox help make our Freshdesk setup compliant in China?
Yes. Our China team can help you assess the cross-border and data-residency exposure for your ticket contents, data volumes and role, and stand up compliant, ICP-filed in-country delivery — and, where the law requires your China customers' data to stay on the mainland, in-country storage. Get in touch to work through your specific case.
