Why 21YunBox Pricing Contact Log in
Talk to an expert Test your site in China

Does FullStory Work in China? Session Replay, PIPL & Data Residency

FullStory records your visitors — their DOM, clicks, inputs and full session replays — and processes and stores that behavioral data on Google Cloud in the US or the EU, with no mainland-China region. For China that is a PIPL cross-border transfer and a data-residency question, not a speed one. A compliance-first look at session replay in China.

Does FullStory work in China?

Whether you can use FullStory in China is first a data-residency and cross-border-data question, not a speed one. FullStory is session-replay analytics you embed as a script, and it works by recording your visitors — so the moment it runs for a mainland user, you are collecting and exporting that person's behavioral data.

In FullStory's own documentation, it "captures the user interface (UI)" by "tracking the DOM structure and any changes to it," and "the data capture script sends changes to the DOM structure to Fullstory's servers, along with raw input events and metadata" — a replay of what each visitor saw and did. FullStory "uses Google Cloud Platform data centers to process and store data," with "the default data center for all customers" in the US and an EU option — and no region inside mainland China. So your China visitors' session recordings are held offshore, a cross-border transfer of personal information PIPL governs. FullStory's Private by Default and masking controls narrow what sensitive text you export, but they don't move the data home. The table below is FullStory's own wording and the rules it triggers.

This is a risk picture, not a verdict — your duties turn on your data volumes, your role, and how much you leave unmasked. Our China team can map your FullStory exposure with you →

Compliance snapshot

  • ! Embeds a script that records your mainland visitors' sessions — the DOM and its changes, plus raw input events and interactions — rebuilt as watchable session replays
  • ! FullStory "uses Google Cloud Platform data centers to process and store data" — the US by default, the EU by option — so China visitors' recordings sit offshore
  • ! Sending those session recordings and behavioral data abroad is a PIPL cross-border transfer (notice + separate consent + a transfer mechanism)
  • ✕ FullStory's only data-residency regions are the US and the EU — it names no mainland-China region, so in-country storage isn't an option on FullStory itself
  • ✓ A compliant in-country capture, delivery and storage path exists — no rebuild, no migration
Get a compliance assessment
No China entity required to start

What FullStory's own documentation says about China

FactPrimary source
In FullStory's own words, it records a replay of each visitor's session. FullStory's help docs state that it "captures the user interface (UI)," that "the only method Fullstory uses for capturing the UI is by tracking the DOM structure and any changes to it," and that "the data capture script sends changes to the DOM structure to Fullstory's servers, along with raw input events and metadata." Rebuilt, that is a frame-by-frame reconstruction of what a person saw and did on your site — and under Chinese law, that reconstruction is personal information. Fullstory Help — How do I protect my users' privacy in Fullstory?, retrieved 2026-10-07
Those recordings are processed and stored on Google Cloud, offshore. FullStory's Data Residency page states it "uses Google Cloud Platform data centers to process and store data," that "the default data center for all customers is located in the US" (NA1, us-central1), and that "as of August 2022" it also runs an EU region (EU1, europe-west3). Those are the only two regions it documents — there is no mainland-China region — so your China visitors' session data is held outside the mainland. Fullstory Help — Fullstory Data Residency, retrieved 2026-10-07
Sending that data offshore is a cross-border transfer under PIPL. Session recordings and behavioral data captured from mainland visitors are personal information, and exporting them to FullStory's Google Cloud regions abroad is a cross-border transfer governed by PIPL: the personal-information handler — you, FullStory's customer, not FullStory — 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
FullStory's privacy controls narrow the capture — they don't move it onshore. With industry-standard settings FullStory blocks a set of "default exclusions" — passwords, "all credit card data / payment card information," and hidden inputs — and for excluded or masked elements the data "never leave[s] your users' browsers ... or touch[es] Fullstory's servers." But the protection is only as wide as what you mask: "Unmask is Fullstory's 'capture everything' setting," and PIPL's sensitive personal information category reaches far beyond passwords and card numbers. Masking lowers how much sensitive text you export; it does not change that the behavioral record itself still leaves the mainland. Fullstory Help — How do I protect my users' privacy in Fullstory?, retrieved 2026-10-07
The exposure scales with volume, role and sensitivity. Since the CAC's March 2024 cross-border rules, a non-CIIO transferring fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, standard contract and certification — but sensitive personal information and larger volumes carry stricter duties. And for a CIIO or large-volume handler, personal information collected in China must be stored inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — which FullStory's US and EU regions cannot do, so the only way to keep that data on Chinese soil is to run the capture and storage on infrastructure inside the mainland. CAC — Provisions on Promoting and Regulating Cross-border Data Flows, March 2024; 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 FullStory is not how quickly its session replays render — it is whose data has to leave the country for those replays to exist. FullStory is digital-experience analytics, and the way it works is by recording your visitors: it reconstructs the page they saw and the actions they took, then processes and stores that recording on Google Cloud. Point it at your mainland visitors and you are exporting their session recordings and behavioral data across the border — something China’s privacy law governs directly. Whether FullStory’s capture script happens to load on a given day inside China is a delivery detail; where the recordings end up, and whether anything sensitive rides along, is the exposure.

FullStory Data Residency help page stating that it uses Google Cloud Platform data centers to process and store data, with the default data center in the US (NA1, us-central1) and an EU data center (EU1, europe-west3) — and no mainland-China region
FullStory's own Data Residency page: “Fullstory uses Google Cloud Platform data centers to process and store data,” and “The default data center for all customers is located in the US” — with an EU data center added in August 2022 and no region inside mainland China. Source: help.fullstory.com — Fullstory Data Residency

FullStory in China at a glance

What decides it In FullStory's own terms
What it records FullStory “captures the user interface (UI)” by “tracking the DOM structure and any changes to it,” sending “changes to the DOM structure to Fullstory's servers, along with raw input events and metadata” — rebuilt into a replay of each visitor's session. All personal information.
Where it's stored FullStory “uses Google Cloud Platform data centers to process and store data,” defaulting to the US (NA1, us-central1), with an EU region (EU1, europe-west3) added in August 2022. It names no mainland-China region, so your China visitors' recordings sit offshore.
The privacy controls Private by Default, Mask and Exclude keep flagged content on the device — excluded or masked elements “never leave your users' browsers ... or touch Fullstory's servers” — and passwords, payment fields and hidden inputs are blocked by default. But “Unmask is Fullstory's 'capture everything' setting,” so anything you leave unmasked is still captured.
The sensitive-data catch PIPL's sensitive personal information — and its stricter separate-consent and necessity rules — reaches well past passwords and card numbers to health, financial, location and other data a session replay can pick up unless you mask it. Those defaults don't cover all of it.
The residency rule Exporting China users' session and behavioral data is a cross-border transfer under PIPL (notice, separate consent, a transfer mechanism); CIIOs and large-volume handlers must store it in the mainland — which a US or EU Google Cloud region cannot do.

A session recording is personal data in the making

FullStory doesn’t wait for you to collect anything extra — the recording is the data collection. In its own help docs, FullStory “captures the user interface (UI),” and “the only method Fullstory uses for capturing the UI is by tracking the DOM structure and any changes to it.” In practice, “the data capture script sends changes to the DOM structure to Fullstory’s servers, along with raw input events and metadata” — enough to replay, moment by moment, what a visitor saw and how they moved through your site. A reconstruction of a real person’s session is personal information under China’s law. So the instant FullStory runs for a mainland visitor, you are handling that visitor’s personal data — and handling it by streaming it to FullStory.

The recordings are processed and stored on Google Cloud — offshore

Asked where that data lives, FullStory is specific: it “uses Google Cloud Platform data centers to process and store data,” and “the default data center for all customers is located in the US.” Since August 2022 there is also an EU region (EU1, europe-west3 on Google Cloud); the US region is NA1, on us-central1. Those are the only two choices FullStory documents — there is no region inside mainland China. So your China visitors’ session recordings are processed and stored outside the mainland. Under China’s Personal Information Protection Law that is a cross-border transfer, and the handler — you, FullStory’s customer — must give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification) under 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 a US or EU Google Cloud region cannot meet, and one no account setting inside FullStory changes.

Private by Default narrows the capture — it doesn’t move it home

FullStory, to its credit, builds in real privacy controls, and they matter here. Capture runs in three modes — Exclude, Mask and Unmask. For excluded elements, “the element itself (and any child elements) will be ignored by data capture”; for masked elements, “all text will be replaced by irreversibly transformed placeholder text meant to resemble a wireframe of the original content.” Crucially, “excluded or masked elements never leave your users’ browsers or mobile applications or touch Fullstory’s servers” — the filtering happens on the device, before anything is sent. Under industry-standard settings FullStory also blocks a set of “default exclusions”: passwords, “all credit card data / payment card information,” and hidden inputs.

Two limits keep that from settling the China question. First, the protection is only as wide as what you mask: “Unmask is Fullstory’s ‘capture everything’ setting,” and when elements are unmasked “Fullstory will capture all text, images, and user interactions.” Anything you leave unmasked — or any sensitive content those default selectors don’t catch — is captured and exported like the rest, and PIPL’s definition of sensitive personal information reaches far past passwords and card numbers, to health, financial, location and other data a replay can easily pick up. Second, even a perfectly masked session is still a behavioral record of a real person, and it still leaves the mainland. Masking lowers how much sensitive text you export; it does not change that the recording itself is a cross-border transfer.

Reachable or not, the data still leaves the mainland

FullStory runs by embedding a capture script that loads from a FullStory-operated endpoint and streams what it records back to Google Cloud. Whether that endpoint loads cleanly from any given mainland line is a delivery question, and not the one that decides whether you may use FullStory. Even on the connections where the script loads perfectly, it loads in order to send your visitors’ session recordings offshore; a steadier path would only export that data more efficiently, not make the transfer lawful. The half that settles whether FullStory is usable for China is the legal one — where the recordings are stored, how much sensitive content rides along, and under what mechanism they cross the border — not the network one.

This is a risk map, not a verdict: whether you owe separate consent, a transfer mechanism, in-country storage, stricter handling for sensitive data, or all of these turns on what FullStory captures for you, how much you leave unmasked, your data volumes, and who your users are — worth settling with counsel before you rely on it.

Where 21YunBox fits — a compliant overlay, not a migration

FullStory can stay exactly where it is. What we add is the piece FullStory leaves to you: ICP-filed, in-country delivery set in front of your existing origin inside mainland China — no rebuild, no second codebase, no move off your current analytics. Our China team traces where your visitors’ recordings travel today, weighs your PIPL cross-border and data-residency duties against your entity and your data volumes, and — where the law requires your China users’ behavioral data to stay on the mainland — stands up the lawful, in-country capture and storage FullStory’s US and EU regions cannot provide, while FullStory and the rest of your stack keep running where they already are.

Get a compliance assessment →


Related reading:

Frequently Asked Questions

Does FullStory store Chinese users' data in China?

No. By FullStory's own Data Residency page it "uses Google Cloud Platform data centers to process and store data," with the default data center in the US and an EU region added in August 2022 — the only two regions it documents. There is no mainland-China region, so the session recordings and behavioral data FullStory captures from your mainland visitors are processed and stored offshore.

Doesn't FullStory's Private by Default masking solve the privacy problem for China?

It helps, but it doesn't settle it. Private by Default, Mask and Exclude keep flagged content in the user's browser — excluded or masked elements, in FullStory's words, "never leave your users' browsers ... or touch Fullstory's servers" — and passwords, payment fields and hidden inputs are blocked by default. But anything you leave unmasked is still captured ("Unmask is Fullstory's 'capture everything' setting"), PIPL's sensitive-data category is broader than those default fields, and even a fully masked session is still a behavioral record that leaves the mainland. So masking reduces your exposure; the cross-border transfer and any residency duty remain. Treat it as a risk to assess with counsel.

Can 21YunBox help make our FullStory setup compliant in China?

Yes. Our China team can assess your cross-border and data-residency exposure for your data volumes and role, and stand up the compliant, ICP-filed in-country delivery — and, where the law requires your China users' behavioral data to stay on the mainland, in-country capture and storage — around the stack you already run. Get in touch to work through your specific case.

ARTICLES RELATED TO FULLSTORY

Make Your Site Work inside the Great Firewall of China

Enter your information, and our staff will assist you in getting a 21YunBox account for China.

Make Your Site Work Within the Great Firewall of China
Make Your Site Work Within the Great Firewall of China

By clicking 'Get Started', I also agree to 21YunBox's Terms of Service and Privacy Policy.