Does everviz Work in China? ICP, PIPL & an Offshore Embed
everviz is an offshore, cloud-based visualization service — run from Norway on AWS and Google Cloud, with no mainland-China region — so a China-facing page that embeds it makes a PIPL cross-border transfer and the ICP filing sits on your own site, not on everviz. A compliance-first look at the doors.
Does everviz work in China?
Yes — your everviz charts will embed and render for visitors in mainland China, but that is the easy half. everviz is an offshore, cloud-hosted layer that holds your chart data and logs every viewer, so putting it on a China-facing page is a compliance question — a PIPL cross-border transfer — and the ICP filing sits on the site that embeds it, not on everviz.
everviz's operator, Visual Elements AS, works "from our offices in Norway" and calls everviz "a leading cloud-based solution for data visualizations." Its privacy policy says it acts "as a data controller," that "Most of our data is collected and processed within the EEA," and that account data is "hosted on Amazon web services and in Google Cloud Platform" — all offshore, none in mainland China. Because the embedded chart calls home — "Visualizations created with everviz log views through an Ajax call to our own servers" — each Chinese viewer's referrer and user agent leave the mainland, a cross-border transfer of personal information PIPL governs (Articles 38–43). And since the chart is third-party content inside your page, the ICP filing a public mainland site needs attaches to your site, not to everviz. The table below is everviz's own wording and the rule each line triggers.
This is a risk map, not a verdict — whether everviz's data flows need a PIPL transfer mechanism, and what the site embedding it must file, turns on your entity, your data and who your users are. Our China team can map your exposure with you →
Compliance snapshot
- ! everviz runs offshore — Norway and the EEA, on AWS and Google Cloud — with no mainland-China region
- ! Each China view sends the visitor's referrer and user agent to everviz's offshore servers — PIPL applies
- ! The ICP filing sits on the site that embeds everviz, not on everviz itself
- ✕ No mainland region, so no in-country storage for a CIIO or large-volume handler
- ✓ everviz is an embedded layer — your own host stays put and your chart code is unchanged
What Everviz's own documentation says about China
| Fact | Primary source |
|---|---|
| everviz is an offshore, cloud-based service with no mainland-China region. Its operator calls everviz "a leading cloud-based solution for data visualizations," run "from our offices in Norway," and its privacy policy states that "Most of our data is collected and processed within the EEA," with account information "hosted on Amazon web services and in Google Cloud Platform." None of that sits inside mainland China, so everything everviz stores and serves for your Chinese users is offshore by design. | everviz — About us & Privacy policy (everviz.com), retrieved 2026-10-07 |
| everviz is an embedded layer, so the ICP filing belongs to your site — not to everviz. everviz's own docs describe the chart as third-party content your page pulls in: "the visualization is fetched from everviz and shown within the iFrame frame on your website," loading "necessary files and libraries from everviz." The public mainland site that displays it is what needs the ICP filing (State Council Order No. 292; MIIT Order No. 33), tied to a mainland hosting resource — a footing an embedded offshore widget neither carries nor creates. | everviz — Publishing codes (help.everviz.com), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
| Every chart view sends a visitor's data across the border to everviz. everviz states that "Visualizations created with everviz log views through an Ajax call to our own servers," and that "The information we gather through this view counter is limited to the referrer and user agent." For a visitor in China that request leaves the mainland for everviz's offshore cloud — a cross-border transfer of personal information under PIPL, which the handler must cover with notice, separate consent and a transfer mechanism (Articles 38–43). | everviz — Privacy policy (everviz.com), retrieved 2026-10-07; PIPL Articles 38–43 |
| everviz answers to EU law, not China's — your mainland compliance is still yours to arrange. everviz says that "In collecting information about you, we are acting as a data controller," that its handling "is compliant with the European Union's General Data Protection Regulation (GDPR)," and that for "processing that is taking place outside EEA, we have in addition provided appropriate safeguards." Those safeguards serve GDPR, not PIPL; and with no mainland region, personal data everviz processes for Chinese users cannot be stored in-country — a data-localization duty for CIIOs and large-volume handlers (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | everviz — Privacy policy (everviz.com), retrieved 2026-10-07; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the deciding question about everviz is not whether its charts will draw — they will — but what crosses the border when they load, and whose name is on the filing. everviz is a cloud-based service: your chart lives on everviz’s platform, and each visitor’s browser fetches it from there. Its operator runs that platform from Norway, on offshore cloud, with no region inside mainland China. So three compliance facts, not a performance grade, decide whether everviz belongs on a China-facing page — the data everviz holds and logs about your Chinese viewers is a cross-border transfer under PIPL; the ICP filing a public mainland site needs sits on your site, not on the embedded chart; and nothing everviz offers can be stored in-country. Reaching the chart is the easy half; clearing it to operate is the other.
everviz in China at a glance
| What decides it | In everviz's own terms |
|---|---|
| Where it runs | everviz is “a leading cloud-based solution for data visualizations,” run “from our offices in Norway,” with data “collected and processed within the EEA” and “hosted on Amazon web services and in Google Cloud Platform.” No region sits in mainland China. |
| What it is in your page | An embedded, third-party layer: “the visualization is fetched from everviz and shown within the iFrame frame on your website,” loading “necessary files and libraries from everviz.” Your page displays the chart; everviz hosts it. |
| Serving the public (ICP) | A public mainland site needs an ICP filing tied to a mainland hosting resource. everviz is a third-party embed with no mainland footing, so the filing attaches to your site — not to everviz. |
| Your viewers' data | everviz “log[s] views through an Ajax call to our own servers” — a visitor's referrer and user agent — and acts “as a data controller.” For Chinese visitors that is a cross-border transfer PIPL governs. |
| Data residency | With no mainland region, personal data everviz processes for Chinese users cannot be stored in-country — a duty for CIIOs and large-volume handlers that offshore cloud cannot meet. |
An embedded layer, so the ICP filing stays on your site
everviz does not host your website; it hosts a chart your website pulls in. In everviz’s own documentation the embed is third-party content fetched at view time — “the visualization is fetched from everviz and shown within the iFrame frame on your website,” with the script form loading “necessary files and libraries from everviz.” That architecture decides the licensing question, because the ICP filing (ICP 备案) a public mainland site requires under State Council Order No. 292 and MIIT Order No. 33 attaches to a hosting resource physically inside the mainland. An embedded offshore widget carries no such record and creates no such footing. So the filing obligation lands where it always did — on the site that displays the chart — and adding everviz neither satisfies it nor makes it disappear. “We only embed a chart” is not a path around the door; the door still belongs to your page.
Every view carries personal data across the border
The moment a chart loads for someone in China, data about that person leaves the country. everviz states plainly that “Visualizations created with everviz log views through an Ajax call to our own servers,” and that “The information we gather through this view counter is limited to the referrer and user agent.” Limited or not, that is personal information moving from a mainland visitor to everviz’s offshore cloud — and under China’s Personal Information Protection Law a transfer out of the mainland is a cross-border transfer the handler must cover with notice, separate consent, and one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification) under Articles 38–43. everviz confirms it sits on the EU side of that line: “In collecting information about you, we are acting as a data controller,” its handling “is compliant with the European Union’s General Data Protection Regulation (GDPR),” and for “processing that is taking place outside EEA, we have in addition provided appropriate safeguards.” Those safeguards answer to GDPR — not to PIPL — so the China-side compliance is yours to arrange, not everviz’s.
Offshore by design — reachable, but nothing lands in-country
everviz runs from Norway, and its privacy policy puts the data “within the EEA” and “hosted on Amazon web services and in Google Cloud Platform.” Not one of those locations is in mainland China. Two consequences follow, and neither is about speed. First, every view fetches the chart and its libraries from everviz’s offshore cloud, so each load is a cross-border request for third-party content — a delivery consideration, and the honest half of “will it show up,” separate from whether you may use it. Second, and the heavier half: with no mainland region, any personal data everviz processes for your Chinese users cannot be stored in-country. For a critical information infrastructure operator or a large-volume handler, China requires that personal information collected in the mainland be stored there (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty an offshore visualization service has no way to meet.
This is a risk map, not a verdict: whether you owe a PIPL transfer mechanism, in-country storage, or an ICP filing on the embedding site depends on what you publish, how much personal data you hold, and who your users are — worth settling with counsel before you ship.
Where 21YunBox fits — a compliant overlay, not a migration
You keep everviz exactly as it is — same editor, same charts, same embed code. What a China-facing page still needs is the piece an offshore visualization service never supplies: compliant, ICP-filed delivery from inside the mainland, set in front of your existing origin — no rebuild, no second codebase, and no move off everviz. Our China team maps what actually crosses the border when your charts render, weighs your PIPL cross-border and data-residency exposure against your entity and your users, and stands up the in-country, ICP-filed delivery a lawful mainland presence requires — so the page your everviz charts live in is cleared to operate, not merely able to load.
Related reading:
Frequently Asked Questions
Do our everviz charts need their own ICP filing in China?
No — everviz is an embedded, third-party layer, so it carries no ICP record of its own. What needs the filing is the public mainland website that displays the chart: an ICP filing tied to a mainland hosting resource, under State Council Order No. 292 and MIIT Order No. 33. Embedding everviz doesn't create that mainland footing, and it doesn't lift the duty from the site that pulls the chart in.
Is it a problem under China's law to embed everviz on a site we serve to mainland users?
Treat it as a risk to assess with counsel, not a flat yes or no. everviz is hosted offshore — in Norway, on AWS and Google Cloud — and its own privacy policy says each view is logged "through an Ajax call to our own servers." So every mainland visitor's referrer and user agent leave the country, which PIPL governs as a cross-border transfer of personal information (notice, separate consent, a transfer mechanism). Whether a data-localization duty also applies turns on your role — for example a CIIO — and how much personal data you handle.
Can 21YunBox help make our everviz-powered site work in China?
Yes. Our China team can map what actually crosses the border when your charts load, assess your PIPL cross-border and data-residency exposure for your entity and your users, and stand up the ICP-filed, in-country delivery a compliant mainland presence needs — in front of the site you already run, with everviz left exactly as it is. Get in touch to work through your specific case.
