Does Amazon Translate Work in China? PIPL Cross-Border Data Transfer & Content Residency

Whether Amazon Translate “works” in mainland China is a compliance question before it is a networking one, and for a machine-translation API the question has a sharp, under-appreciated shape: the content you most need translated is exactly the content most likely to contain personal information. Amazon Translate is a raw neural machine-translation service — text in, translated text out — and there is no Amazon Translate region inside mainland China. Even AWS’s separate China partition, which does offer AI services like Amazon Transcribe and Polly, does not offer Translate. So a China-facing caller reaches a non-China AWS region, and every string you send — support tickets, documents, product copy, contracts — is carried across the border to be processed, carrying whatever personal, sensitive or confidential information it holds. That is a cross-border transfer of personal information under PIPL (Articles 38–40, 数据出境); sensitive content adds Article 28; a critical-information-infrastructure or high-volume handler also faces an in-country storage duty; and by AWS’s own account the text is stored and used to improve its models unless you opt out.

Amazon Translate in China at a glance

What you actually send — and where it goes

Start with what a translation call actually is. Amazon Translate does not translate a reference to your content held somewhere safe; it translates the content itself. You hand the API the source text in full, and the exposure is the text — and everything inside it. The jobs that most need translating are support tickets, HR and legal documents, contracts, knowledge-base articles, product copy and user-generated content, and those are exactly the payloads most likely to carry names, email addresses, order records, health or financial details, and confidential business information. You cannot strip a document down to a reference and still get it translated; the whole of it goes.

Where does it go? To a non-China AWS region. There is no Amazon Translate region inside mainland China, and — the nuance that trips teams up — Translate is not available even in AWS’s separate China partition. AWS does run a China partition (the Beijing Region operated by Beijing Sinnet Technology Co., Ltd. and the Ningxia Region operated by Ningxia Western Cloud Data Technology Co., Ltd.), and AWS’s own China Region Table lists AI services such as Amazon Transcribe, Polly and SageMaker as available there — but Amazon Translate is absent from that list. So the “just use the China partition” move that works for some AWS services does not work for Translate (see Does AWS work in China? for the two-door partition structure). A China-facing caller reaches a region outside the mainland, and by AWS’s own FAQ the content is “encrypted and stored at rest in the AWS region where you are using Amazon Translate,” with some portion that “may be stored in another AWS region” for model improvement. Either way, the source text — and the personal information in it — is processed and held offshore.

It’s a cross-border data transfer — under PIPL

Because the source text leaves China to be processed, sending it to Amazon Translate is a cross-border transfer of personal information, not a routing detail. The duty sits on you as the handler, not on AWS as the processor. PIPL Articles 38–40 require that, before personal information is sent abroad, you give notice, obtain a separate consent distinct from any general agreement to use your product, and put one transfer mechanism in place — a CAC security assessment, the CAC standard contract, or certification. Where your content carries sensitive personal information — medical, financial, biometric, religious or ID data, which translation jobs frequently do — PIPL Article 28 adds a separate consent and a prior personal-information protection impact assessment, and you cannot anonymize text you need rendered in full. Above certain thresholds, genuinely necessary exports also run through China’s data-export security assessment (数据出境安全评估) before anything leaves.

Residency is the other half. If your organization is a critical information infrastructure operator — or a high-volume personal-information handler — the Cybersecurity Law’s Article 39 (formerly Article 37 — the 2025 Cybersecurity Law amendment, in force January 1, 2026, renumbered the data-localization article from 37 to 39, its substance unchanged) requires personal information generated in China to be stored in China, with any genuinely necessary export cleared through a security assessment (see also PIPL Article 40). A translation call that ships the content to an offshore region, and may keep a copy in yet another region, is squarely in tension with that duty. None of this turns on how fast the API responds; it turns on where the content is read and kept. For that reason this page publishes no China latency figure for Amazon Translate: speed is not the axis for a decision that turns on residency and cross-border transfer.

Reaching the API isn’t the question — keeping the content in-country is

The reflex is to point the SDK at the nearest region — Tokyo, Singapore, Hong Kong — and treat the distance as the problem solved. But every Amazon Translate region sits outside mainland China, so a nearer one changes the latency, not the law: the source text is still carried across the border, still processed offshore, and — on the default settings — still stored and used to improve AWS’s models. A nearer region is not an in-country one, and Hong Kong is a separate jurisdiction from the mainland for data-export purposes.

So the honest levers are three, and none of them is “make the offshore API reachable.” First, Amazon Translate offers no mainland-China region and no self-hosted deployment, so for China-origin content the durable option is a licensed in-country machine-translation or localization alternative — a domestic service that keeps the data in China — rather than an offshore call. Second, minimize and pseudonymize the personal information in your strings before any offshore call: translate the template, not the customer record; strip names, contact details and identifiers where the translation does not need them. Third, where you still use an offshore engine for content that carries no China personal information, set the AWS Organizations opt-out policy so the input is no longer stored and used to train AWS’s models — understanding that opting out reduces the retention exposure but does not change the fact that the text still crosses the border on every call. What none of this is: a tunnel that ships the content offshore anyway and calls it local.

This is a risk map, not a verdict that Amazon Translate is “blocked” or “illegal.” Which of these obligations bite depends on your entity, the personal and sensitive data your content carries, your role under Chinese law and who your users are — worth settling with counsel before your translation pipeline depends on it.

The lawful path — map, localize, deliver

There is a compliant way to translate content for a China-facing product, and it has a shape.

First, map. Our China compliance team charts what content actually flows to Amazon Translate today — which jobs carry personal or sensitive information, which reach a non-China region, whether the input is retained or used for model training, and where you lack a lawful basis for the cross-border leg. We build the technical picture; the legal conclusions are settled with your counsel.

Then localize. Where China-origin content has to be translated on a China footing, we move it onto a lawful in-country path — a licensed in-country machine-translation or localization service with the data kept in the mainland — and we minimize and pseudonymize personal information before any string that still must go offshore, so your China users’ content stops leaving the country by default. You keep Amazon Translate for the markets and content where it already serves you.

Then deliver. The China-facing site or app that displays the translations is itself a public service in the mainland, so it carries an ICP filing duty and needs compliant, in-country delivery. 21YunBox delivers it in-country — the 21YunBox Optimizer — set in front of the origin you already run, with no rebuild and no re-platform. The result is a China-facing product whose translation and delivery both run legally and compliantly for your users in China. 21YunBox never uses or suggests circumvention of any kind: we localize what must stay in-country, deliver in-country, and never move personal information out of China by stealth.

Get a compliance assessment →

Related reading:

• Cross-border data transfers under PIPL
• China’s Cybersecurity Law (data localization, Article 39)
• China’s data-export security assessment measures
• How to get an ICP filing for China

RELATED TECHNOLOGIES

Crowdin

Crowdin

DeepL

DeepL

Google Cloud Translation

Google Cloud Translation

Lokalise

Lokalise

Microsoft Translator

Microsoft Translator

Phrase

Phrase

Smartling

Smartling