Does Simple Analytics Work in China? Reachability, EU Hosting & Privacy-First Facts
Simple Analytics is cookieless, EU-hosted in The Netherlands, and collects no personal data by its own account — so the real China question isn't a big PIPL problem, it's delivery: its tracking script is served offshore from scripts.simpleanalyticscdn.com, which every mainland visitor fetches cross-border. A compliance-first look at reachability and light data residency.
Does Simple Analytics work in China?
Simple Analytics is one of the few tools where the China question is not really about personal data — it is privacy-first by design — but about whether its offshore tracking script reaches your mainland visitors reliably.
Simple Analytics is cookieless and, in its own documentation, collects no personal data: it sets no cookies, assigns no visitor IDs, states "No IP address collection or storage," and keeps its servers in The Netherlands. That genuinely lightens the PIPL and consent story that cookie- or identity-based analytics carry. The live issue is delivery: the tracking script loads from scripts.simpleanalyticscdn.com, offshore, so every mainland page view fetches it cross-border — where it can arrive slowly or intermittently fail, under-counting your China traffic and delaying the page. The table below pairs each vendor fact with what it means for a China audience.
This is a risk picture, not a verdict — your exposure turns on what you actually collect and how you configure it. Our China team can map your Simple Analytics setup and its China delivery with you →
What Simple Analytics's own documentation says about China
| Fact | Primary source |
|---|---|
| The product is cookieless by design: "We do NOT set any cookies (or use similar technologies)," and it assigns no visitor identifiers — "None of these IDs are linked to a person or personal data, and none are stored on the device." On its site it also states "No IP address collection or storage." By its own account it measures pageviews and events without identifying visitors, which keeps it well clear of the separate-consent and cross-border-personal-data duties that cookie- or identity-based analytics trigger. | Simple Analytics — What we collect (documentation) and simpleanalytics.com, retrieved 2026-10-07 |
| Simple Analytics states that "our servers are located in The Netherlands, and your data is always encrypted," and markets itself as EU-hosted. Whatever it records for your site therefore stays in the EU — offshore from mainland China, which is a data-residency fact to note rather than, on the vendor's own account, a personal-data one. | Simple Analytics — What we collect (documentation), retrieved 2026-10-07 |
Simple Analytics is installed with a single tag — <script async src="https://scripts.simpleanalyticscdn.com/latest.js"></script> — served from the vendor's own offshore CDN. For a visitor inside mainland China, every page view makes a cross-border request for that file, so its reachability and load time from behind the border are set by the network, not by the tool. | Simple Analytics — Script (documentation), retrieved 2026-10-07 |
| Because Simple Analytics reports that it holds no personal data, the heavier PIPL cross-border-transfer duties that cookie- and identity-based analytics pull in are largely not engaged here. The caveat worth keeping with counsel is narrow: if you ever configure or combine fields so that any of the data becomes personal, sending it to servers in the Netherlands is still a cross-border transfer, and PIPL applies from that point. | PIPL Chapter III, Articles 38–43 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, Simple Analytics is an unusual case among analytics tools: the thing that normally decides the question — what personal data the tool collects and where it sends it — is, by Simple Analytics’ own account, barely in play. It is cookieless, identifies no visitors, and keeps its data in the EU. What is left to decide is quieter and more practical. The small script that does the measuring lives offshore, and a visitor in mainland China has to reach across the border to load it on every page. That reachability, not a personal-data problem, is where a China audience is won or lost.
Simple Analytics in China at a glance
| What decides it | In Simple Analytics' own terms |
|---|---|
| Personal data | Cookieless and identity-free by its own account: “We do NOT set any cookies,” no visitor IDs, and “No IP address collection or storage.” Pageviews and events are measured without identifying visitors — so the usual China data problem is light. |
| Where the data lives | “Our servers are located in The Netherlands, and your data is always encrypted.” In the EU — offshore from mainland China, but not, on the vendor's account, a cross-border personal-data store. |
| How it's delivered | A single offshore tag: scripts.simpleanalyticscdn.com/latest.js. Every mainland page view fetches it across the border, on a route the tool does not control. |
| The China risk | Reachability and load time of that offshore script. A slow load delays the page; an intermittent failure quietly under-counts your China traffic. This is the real exposure — not personal data. |
| Data residency | Light. It becomes a cross-border question only if you configure or combine fields so that something you collect becomes personal — then PIPL applies to sending it to the Netherlands. |
Privacy-first by design, so the usual data problem is light
Most analytics questions for China start with personal data: cookies, visitor IDs, IP addresses, and where all of it is processed. Simple Analytics answers most of that in its own documentation. It is cookieless — “We do NOT set any cookies (or use similar technologies)” — assigns no visitor identifiers (“None of these IDs are linked to a person or personal data, and none are stored on the device”), and on its site states “No IP address collection or storage.” It reports pageviews and events without identifying the people behind them.
The practical effect is that the heavy PIPL cross-border-personal-data and separate-consent duties that cookie- and identity-based analytics drag in are, on the vendor’s own account, largely not engaged. That is a genuine point in its favor, and it is worth stating plainly rather than manufacturing a data problem that the product’s design does not create. Being privacy-friendly is not the same as being reachable, though — and reachability is the part a China audience actually feels.
The real China question: reaching an offshore script
Simple Analytics is installed as a single tag, <script async src="https://scripts.simpleanalyticscdn.com/latest.js"></script>, served from the vendor’s own offshore CDN. That tag is a dependency every one of your pages carries. For a visitor inside mainland China, loading it means a cross-border request on every page view, and the behavior of that request is decided by the network between them and the Netherlands, not by the tool’s settings.
Two things follow. If the script is slow to arrive, it can hold up the page it sits on. If it intermittently fails to load at all, the visits that fail are simply never counted — which means the China traffic you most need to understand is the traffic least likely to appear in the dashboard. Neither is a flaw in Simple Analytics; both are what happens when a measurement script is fetched from outside the border. We are deliberately not publishing a latency number here: a single probe’s figure would not fairly represent what a real visitor’s network does, so we describe the shape of the risk rather than put a misleading number on it.
Light data residency — where the little it keeps lives
Whatever Simple Analytics does record sits on its servers in The Netherlands — in its words, “our servers are located in The Netherlands, and your data is always encrypted.” That is offshore from mainland China, so it is a data-residency fact worth noting; it becomes a compliance fact only if any of that data is ever treated as personal, which the vendor says it is not. The caveat to keep with your counsel is narrow: if you extend or combine what you collect so that a field becomes personal, then sending it to the Netherlands is a cross-border transfer and PIPL applies from that point. Short of that, the residency question here is genuinely lighter than for most analytics.
This is a risk map, not a verdict: whether anything you collect counts as personal, and whether any filing obligation attaches to how you serve China, depends on your site and your users — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep Simple Analytics exactly as it is. What we add is the piece an offshore script cannot provide for a China audience: compliant, ICP-filed delivery from inside the mainland, placed in front of your site so that the tracking script — and the rest of your page — is fetched locally by visitors in China rather than pulled across the border. No rebuild, no second codebase, and no move off Simple Analytics. Our China team can review how you have it installed, confirm whether any part of what you collect raises a data-residency question for your case, and stand up the in-country delivery that makes the measurement reliable while your analytics stay exactly where they already run.
Related reading:
