FactRelay Docs
China and Global Data Regions
How the China site and the global site are separated — independent domains, builds, application channels, and processing chains — and the four fields that must never collapse into one.
FactRelay operates two independent web properties: a China site (getfactrelay.com, Chinese) and this global site (English). They share a brand, a method, and a design system. They deliberately do not share client data paths.
The separation model
| Layer | China region | Global region |
|---|---|---|
| Domain and build | Independent | Independent |
| Application channel | China-region processing only | Global-region processing only |
| Client data, facts, snapshots, reports | China region | Global region |
| Keys, logs, backups, admin access | China region | Global region |
Shared across regions: code, public documentation, templates, design system, and de-identified test fixtures. Never shared automatically: client accounts, application data, approved facts, snapshots, evidence, reports, and credentials.
Four fields, not one
“Region” hides four distinct questions, and engagements record them separately:
- Client jurisdiction — where the contracting entity is established;
- Target market — where the buyers you care about are;
- Measurement location — where sampling runs and under which platform terms;
- Data storage region — where engagement data lives.
A China-based exporter targeting English-speaking markets is not automatically a global-region client: contracting through a China entity defaults the engagement to the China region, with any cross-border model or vendor calls evaluated per project. A US or EU entity engages through this site into the global region.
Current status — honestly stated
The global site is presently a static informational site: no accounts, no payment, no analytics pixels, and no application form. Until the global operating entity, hosting, and privacy documentation are published, the only data touched by this site is standard hosting access logs. The application channel opens only after those prerequisites are met — this is a hard gate, not a scheduling detail.
When the global channel opens
Application forms will collect the minimum viable fields (work email, company, website, target market, what changed), state purpose, retention, and deletion terms in the privacy notice, route exclusively through global-region processing, and name the vendors involved. Whether GDPR, UK GDPR, or CCPA/CPRA obligations apply depends on the operating entity and audience at that time; the applicable terms will be published before the first field is collected.