Does REVIEWS.io Work in China? Reviewer Data, PIPL & Where It's Stored
REVIEWS.io stores your reviewers' names, emails and review content on servers in the UK, EU, US and Australia — with no mainland-China region — so collecting reviews from Chinese users ships their personal data offshore under PIPL, and its widget loads from offshore. A compliance-first look at the data-residency door.
Does REVIEWS.io work in China?
REVIEWS.io's widget may well paint your star ratings for Chinese shoppers — but that was never the compliance question. REVIEWS.io exists to collect reviewers' and customers' personal data — names, email addresses and the review text itself — and it stores that data on servers in the UK, the EU, the US and Australia, which it states in its own privacy policy. For your mainland users the exposure isn't whether it loads; it's that their personal information is held offshore.
REVIEWS.io's user privacy policy says plainly, "We store data in the region collected. We have data servers in the UK, European Union, USA & Australia" — with no mainland-China region anywhere. So the personal information REVIEWS.io collects from your Chinese reviewers is a cross-border transfer PIPL governs — notice, separate consent and a transfer mechanism — and under REVIEWS.io's own data processing addendum, when you use it to collect reviews the handler is you, the business, not REVIEWS.io. That same offshore footprint is why the on-site review widget, fetched from outside the mainland, can load late or fail. The table below is REVIEWS.io's own wording and the rule each line triggers.
This is a risk map, not a verdict — whether a data-localization duty or China's content rules on public reviews also apply turns on your role, your data volumes and who your users are. Our China team can map your REVIEWS.io exposure with you →
What Reviews.Io's own documentation says about China
| Fact | Primary source |
|---|---|
| REVIEWS.io stores reviewer and customer data on offshore servers — in its own words. Its user privacy policy states: "We store data in the region collected. We have data servers in the UK, European Union, USA & Australia." Not one of those is in mainland China, and REVIEWS.io publishes no mainland-China region — so the personal information it collects from your Chinese reviewers is held outside China, a cross-border transfer under PIPL. | REVIEWS.io User Privacy Policy (reviews.io/legal/user-privacy-policy), retrieved 2026-10-07 |
| Everything REVIEWS.io needs in order to run is personal information. Its user privacy policy makes a reviewer's "Name & Email information ... mandatory, which means that it will not be possible to write a review on the Website without it," and adds that "REVIEWS.io is an open review platform, we will publish your name next to your review unless you have chosen to be anonymous." Names, email addresses and review content identify and profile individuals — so collecting them from mainland users and holding them offshore is a cross-border transfer under PIPL (notice, separate consent and a transfer mechanism, Articles 38–43). | REVIEWS.io User Privacy Policy (reviews.io/legal/user-privacy-policy), retrieved 2026-10-07; PIPL Articles 38–43 |
| Under REVIEWS.io's own data processing addendum, the handler is you — not REVIEWS.io. When you use it to collect reviews, the addendum states the "Customer acts as a controller and AppHub acts as Customer's processor" — REVIEWS.io is operated by AppHub, a US company — and it routes international transfers through UK and EU Standard Contractual Clauses. So the cross-border duties under PIPL fall on you, the business collecting the data; and for a CIIO or large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — which offshore servers cannot do. | REVIEWS.io / Clearer.io Data Processing Addendum (reviews.io/legal/data-processing-agreement), retrieved 2026-10-07; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
| The on-site widget is the delivery half of the question — not the legal half. REVIEWS.io's data-protection page says the data it collects is "held securely on state-of-the-art servers" — the same offshore servers named above — and its review widget is a script pulled onto your pages from REVIEWS.io's own domain outside the mainland, so from inside China it can load slowly or fail. Reachability is not the gap that decides lawfulness, though: the ICP filing a public mainland site needs (State Council Order No. 292; MIIT Order No. 33) attaches to your own site, not to the REVIEWS.io widget — so don't let an ICP checkbox hide the real exposure, which is where the reviewer data lives. | REVIEWS.io Data Protection page (reviews.io/legal/data-protection), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, REVIEWS.io raises a data question well before a speed one. It is a review and user-generated-content platform, and its core job is to collect personal information from the people who write and read reviews — their names, email addresses, and the review content itself — then display that content on your pages through a widget it serves from its own domain. REVIEWS.io is candid in its own policies about where all of this lives: on servers in the UK, the European Union, the US and Australia, with nothing inside mainland China. The reviews will likely appear for your Chinese visitors; the exposure is that the personal data behind them crosses the border under China’s privacy law, and the widget that renders them has no footing in the mainland either.
REVIEWS.io in China at a glance
| What decides it | In REVIEWS.io's own terms |
|---|---|
| Where your data lives | REVIEWS.io's user privacy policy: “We store data in the region collected. We have data servers in the UK, European Union, USA & Australia.” No server sits inside mainland China; the company is UK-based and its service is operated by AppHub, a US company. |
| What it collects | To leave a review, “Name & Email information is mandatory”; REVIEWS.io is “an open review platform” that publishes the reviewer's name unless they choose anonymity, and review text, emails and social-profile data are tied to each person — personal information, not anonymous metrics. |
| Who carries the duty | Its data processing addendum states the “Customer acts as a controller and AppHub acts as Customer's processor.” Collecting reviews from mainland users makes you — the business — the personal-information handler under PIPL, not REVIEWS.io. |
| Crossing the border | REVIEWS.io routes international transfers through UK and EU Standard Contractual Clauses — a European/US framework, not a mainland-China one. For Chinese reviewers that is a cross-border transfer PIPL governs (Articles 38–43). |
| Widget & ICP | The on-site review widget is served from REVIEWS.io's offshore domain, so it can load slowly or fail in China; the ICP filing a public mainland site needs attaches to your own site, not to the widget. |
Where your reviewers’ data actually lives
REVIEWS.io does not run on infrastructure you control, and none of it sits in mainland China. Its user privacy policy answers the residency question directly: “We store data in the region collected. We have data servers in the UK, European Union, USA & Australia.” REVIEWS.io is a UK company, and its service is operated by AppHub, a US company whose data processing addendum names it the processor acting on your data. So every location that holds your reviewers’ personal information is in Europe, North America or Australia — and there is no mainland-China region to place any of it inside the country. That geography settles the data-residency question before a single word about page speed: the information your Chinese reviewers hand over is stored offshore by design.
Your Chinese reviewers’ data crosses the border — and the duty lands on you
REVIEWS.io is explicit that it collects identifiable information from the people who use it. To leave a review, its policy says, “Name & Email information is mandatory, which means that it will not be possible to write a review on the Website without it,” and because “REVIEWS.io is an open review platform,” it “will publish your name next to your review unless you have chosen to be anonymous.” Names, email addresses and the review text are personal information, not anonymous metrics. When the people handing them over are in mainland China, moving that information to the UK, the EU, the US or Australia is a cross-border transfer under the Personal Information Protection Law: the handler must give notice, obtain separate consent, and clear one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification (Articles 38–43). For 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 offshore servers cannot satisfy. And the handler carrying these duties is you: REVIEWS.io’s own data processing addendum states the “Customer acts as a controller and AppHub acts as Customer’s processor,” routing its international transfers through UK and EU Standard Contractual Clauses — European mechanisms built for Europe’s regime, not China’s.
The review widget is served from offshore — and ICP isn’t REVIEWS.io’s door
REVIEWS.io’s reviews reach your visitors through a widget: a script loaded onto your pages from REVIEWS.io’s own domain, drawing the review content from the same offshore servers as everything above, with no point of presence inside the mainland. The widget is not blocked, but an offshore third-party script reached from inside China can resolve slowly or fail outright, and a review box that stalls holds up the part of the page it occupies. It is just as important not to invent a door that isn’t there: REVIEWS.io runs as an embedded component on your site, so the ICP filing a public-facing mainland site requires (State Council Order No. 292; MIIT Order No. 33) belongs to your own site, not to the REVIEWS.io widget — treating the widget as if it needed its own filing would aim the assessment at the wrong risk. Separately — and this is a question for counsel, not one to overstate — public, user-generated reviews displayed to a mainland audience can touch China’s content rules, one more reason to treat a China-facing review display as a compliance decision rather than a drop-in snippet.
This is a risk map, not a verdict: how much of it bites depends on how much personal data you collect through REVIEWS.io, whether you count as a CIIO or large-volume handler, and who your users are — worth settling with counsel before you ship it to China.
Where 21YunBox fits — a compliant overlay, not a migration
REVIEWS.io stays exactly where it is — your review collection, widgets and reviewer workflow keep running untouched, and you migrate nothing. What we add is the piece an offshore review platform cannot provide for itself: compliant, ICP-filed delivery from inside the mainland, placed in front of the site and origin you already run — no rebuild, no second codebase, and no move off REVIEWS.io. Our China team works through what personal information you actually gather through REVIEWS.io, weighs your PIPL cross-border and data-residency position against your entity and data volumes, and stands up the in-country delivery and lawful data handling a China presence calls for, while your reviews keep coming from REVIEWS.io and your application stays put.
Related reading:
