Data Compliance + Cross-Border Transfer for a SaaS Company

A Singaporean B2B SaaS company built a China data compliance programme and set up cross-border data transfer pathways to support their China customers from their existing regional infrastructure.

Verifiable details
Conducted by
Geason Law Offices
Client type
Enterprise SaaS / B2B Software
Rules applied
  • Personal Information Protection Law
  • Data Security Law
  • Measures on Standard Contracts for Cross-Border Data Transfer
Authority
Cyberspace Administration of China (CAC)
Deliverables
  • Full data flow map (China entry and exit)
  • PIPL compliance framework and privacy policy
  • Cross-border transfer standard contract filing
  • Data classification and grading policy
  • Vendor compliance review programme
Duration
10 weeks
Outcome
Completed
The non-obvious judgment You do not always need a China entity or China-localised servers to serve China customers — but you do need to carefully map your data flows and set up the right cross-border transfer pathways. The key is understanding what data is in scope, not just where the servers are.

Background

The client is a Singapore-headquartered B2B SaaS company providing an enterprise project management platform with AI-powered analytics features. They had been serving international customers for several years and had recently started gaining traction with Chinese enterprise customers — primarily multinational companies with operations in China.

Their infrastructure was based in Singapore and AWS US-West. They did not have a China entity, and they did not have any servers inside mainland China. But they were processing personal information of their Chinese enterprise customers’ employees — names, email addresses, project data, and usage analytics.

As their China customer base grew, they started getting questions from customers about data compliance: where is our data stored? Is it compliant with Chinese law? Do you have the necessary approvals for cross-border data transfer? They realised they needed to build a proper China data compliance programme — not just to satisfy customer questions, but to make sure they were actually operating within the law.

Key Challenges

Do we even need to comply with Chinese data law? The company’s first question was whether PIPL and other Chinese data laws even applied to them. They had no China entity, no China servers, and their service was sold internationally. We needed to walk them through the extraterritorial scope of PIPL and help them understand where they stood.

What data is actually in scope? They had a complex data environment: customer account data, user profile data, project content (which could include personal information or not, depending on what customers put in), and usage analytics. They needed help mapping all of this and figuring out what counted as “personal information” under Chinese law, what was “sensitive personal information,” and what was not in scope at all.

Cross-border transfer pathway selection. Since all their data processing happened outside China, transferring data out of China was a core issue. They needed to understand which cross-border transfer pathway was right for them: standard contract, security assessment, or certification. And they needed to know what the process involved, how long it would take, and what the ongoing obligations were.

Customer-facing compliance documentation. Their enterprise customers were asking for compliance documentation: data processing agreements, security assessments, privacy policies in Chinese. They needed to create a set of customer-facing compliance materials that were accurate, complete, and appropriate for the Chinese market.

Vendor and sub-processor management. They used several sub-processors (cloud infrastructure, analytics tools, support services) that also touched data. They needed to make sure their vendor agreements met PIPL requirements for data processing entrustment.

Geason’s Approach

We approached the engagement in five stages, building from understanding to implementation.

Stage 1: Scope assessment and data mapping. We started by thoroughly mapping all the company’s data flows related to Chinese users: what data they collected, where it came from, where it was stored, where it was processed, who it was shared with, and why. This was not just a paperwork exercise — it involved working with their engineering team to trace actual data paths through their systems. We categorised each data type according to Chinese law: personal information vs. non-personal information, sensitive vs. non-sensitive, important data vs. ordinary data.

The key finding from this stage was that while some of their data was clearly personal information (user names, emails, profile data), a significant portion (project content that customers uploaded) was the customer’s responsibility, not theirs. This reduced the scope of what they needed to handle directly — though they still had obligations as a data processor.

Stage 2: Legal basis and compliance framework design. Based on the data map, we designed a PIPL compliance framework appropriate for their situation. We identified the legal basis for each processing activity (primarily contract performance and legitimate interests, since this was a B2B enterprise product). We designed the privacy notice structure, consent mechanisms (where needed), and data subject rights processes. We also helped them understand their obligations as a data processor vs. a data controller — since for some data types they were the controller and for others they were processing on behalf of their customers.

Stage 3: Cross-border transfer setup. We determined that the standard contract pathway was appropriate for their situation — they were transferring personal information from China to Singapore and the US, but the volumes were moderate and the data was not particularly sensitive. We prepared the standard contract filing package, including the data flow description, impact assessment, and supporting documents. We also helped them implement the operational requirements of the standard contract: data security measures, record-keeping, and procedures for handling data subject requests.

Stage 4: Documentation and customer materials. We drafted the full set of compliance documentation: a China-specific privacy policy (in both English and Chinese), a data processing agreement template for their enterprise customers, vendor data processing agreements for their sub-processors, and internal data protection policies. We also created a customer-facing compliance FAQ that they could share with prospects and customers who had questions about China data compliance.

Stage 5: Implementation and training. We supported their engineering and product teams in implementing the required changes to their product and systems — updating the privacy policy interface, adding consent flows where needed, and setting up processes for handling data subject requests. We also conducted training for their customer-facing teams (sales and support) so they could answer basic compliance questions from customers and know when to escalate to legal.

The Non-Obvious Judgment

The most important judgment in this case was about scope — specifically, what was not in scope.

Many companies assume that because they have Chinese users, all their data activities are subject to Chinese data law. But the reality is more nuanced. PIPL applies to the processing of personal information of individuals in China — but the exact scope depends on what you are processing, why you are processing it, and whether there is a sufficient nexus to China.

In this case, the key distinction was between:

  1. User account data (names, emails, login data) — clearly personal information of individuals in China, fully subject to PIPL
  2. Enterprise project data (content that customers uploaded into the platform) — the customer was the data controller; the company was the data processor, with different (but still real) obligations
  3. Aggregated, anonymised analytics data — if properly anonymised (not just pseudonymised), this may fall outside the scope of PIPL

Getting the scope right was crucial because it determined everything else: what needed to go into the privacy policy, what cross-border transfer mechanisms were needed, what data subject rights processes were required, and how much work was involved. Overestimating the scope would have meant unnecessary work and cost; underestimating it would have meant compliance gaps.

A second important judgment was the timing of the cross-border transfer filing. The company initially thought they needed to complete everything before they could continue serving Chinese customers. But the reality is more nuanced — the regulations recognise that companies may already be processing data when they come into scope, and there is a reasonable period to come into compliance. We helped them understand the timeline, prioritise the most important things first, and build a plan to get fully compliant without disrupting their business.

Key Outcomes

  • Complete data flow map covering all China-related data: 17 data types mapped, categorised, and assigned legal basis
  • PIPL compliance framework implemented: privacy policy (EN/CN), consent management, data subject rights process, data breach response plan
  • Standard contract filing submitted and accepted for the cross-border transfer of personal information of Chinese users
  • Data processing agreement template for enterprise customers, addressing both PIPL requirements and customer expectations
  • Vendor compliance programme: 6 sub-processors reviewed, contracts updated to include PIPL-required data processing terms
  • Customer-facing compliance materials: compliance FAQ, data security white paper, and standard responses for RFPs
  • Team training: product, engineering, sales, and support teams trained on China data compliance basics
  • Compliance calendar: annual review schedule set for ongoing monitoring and updates

The company has since doubled their China customer base and reports that having proper compliance documentation has become a competitive advantage — many prospects choose them over competitors precisely because their data compliance programme is more mature and transparent.

FAQ

Q: Does PIPL apply to us if we do not have a China entity or China servers?

A: It can. PIPL applies to the processing of personal information of individuals in China, regardless of where the processor is located, if the processing is related to providing products or services to individuals in China or analysing or evaluating their behaviour. If you have Chinese users and you process their personal information, PIPL likely applies — even if you have no physical presence in China. The specific obligations depend on what data you process and how.

Q: What is the standard contract pathway for cross-border data transfer?

A: The standard contract (or SCC) pathway is one of three legal pathways for transferring personal information out of China. It involves signing a standard contract with the overseas recipient (using the government’s standard template), conducting a personal information protection impact assessment, and filing the contract with the CAC. It is the most commonly used pathway for routine transfers of moderate data volume. The process typically takes 1-2 months from submission to completion.

Q: How much does a China data compliance programme cost?

A: For a mid-size SaaS company with Chinese customers but no China entity, building a basic PIPL compliance programme typically costs RMB 80,000 to 250,000 depending on data complexity — the number of data types, the number of sub-processors, whether you need cross-border transfer filings, and how much customer-facing documentation you need. Ongoing compliance costs are lower — usually RMB 20,000 to 80,000 per year for monitoring, updates, and advisory support.

Q: Do we need a data protection officer in China?

A: Not necessarily. The requirement to appoint a personal information protection officer applies to companies that process personal information on a large scale — the definition of “large scale” is specified in implementing regulations. For many B2B SaaS companies with moderate numbers of Chinese users, the threshold is not met. Even if you are not required to have a dedicated officer, you should still have someone responsible for data protection within your organisation. And you may need to appoint a China-based representative for certain regulatory interactions.

Q: Can we use our global privacy policy for China?

A: You can base it on your global policy, but it needs to be adapted for Chinese law. PIPL has specific requirements for what information must be in a privacy notice — including the identity of the controller, the purposes and methods of processing, the categories of personal information, retention periods, data subject rights, and contact information. You also need a Chinese language version for Chinese users. Simply translating your global policy is usually not sufficient — there are substantive differences in what is required.

Related services

More in this category

If your product sits at a similar point, walk us through where you are. We will identify which obligations are triggered before discussing scope.

Discuss a similar matter