<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Attorney's Substack]]></title><description><![CDATA[My personal Substack]]></description><link>https://attorneymikewu.substack.com</link><image><url>https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png</url><title>Attorney&apos;s Substack</title><link>https://attorneymikewu.substack.com</link></image><generator>Substack</generator><lastBuildDate>Sat, 06 Jun 2026 00:28:27 GMT</lastBuildDate><atom:link href="https://attorneymikewu.substack.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Attorney Mike Wu]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[attorneymikewu@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[attorneymikewu@substack.com]]></itunes:email><itunes:name><![CDATA[Attorney Mike Wu]]></itunes:name></itunes:owner><itunes:author><![CDATA[Attorney Mike Wu]]></itunes:author><googleplay:owner><![CDATA[attorneymikewu@substack.com]]></googleplay:owner><googleplay:email><![CDATA[attorneymikewu@substack.com]]></googleplay:email><googleplay:author><![CDATA[Attorney Mike Wu]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The independent creator’s advantage is real. Use it.]]></title><description><![CDATA[A client who runs a content business called me last week.]]></description><link>https://attorneymikewu.substack.com/p/the-independent-creators-advantage</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/the-independent-creators-advantage</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Fri, 05 Jun 2026 14:46:54 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A client who runs a content business called me last week. First sentence: &#8220;Mike, someone accused my AI-assisted article of plagiarism. What do I do?&#8221;</p><p>I asked three questions. Are the source materials your own interviews? How much did you rewrite the AI output? Did you disclose AI assistance when you published?</p><p>He couldn&#8217;t answer any of them. That conversation is the reason I&#8217;m writing this.</p><p>I&#8217;m a China-licensed cross-border lawyer based in Guangzhou. I&#8217;ve practiced for seven years, with most of the last two years&#8217; work touching AI in some form &#8212; copyright disputes, compliance consulting, cross-border platform takedowns, contract review for AI-augmented service providers. I also use AI daily in my own practice. So I&#8217;m writing this from both sides of the table: the lawyer who defends creators, and the creator who relies on these tools to ship faster.</p><p>This piece was prompted by Jasmine Sun&#8217;s recent Substack on the independent writer&#8217;s advantage in the AI age. Her core argument: stop racing machines on output. Ask instead which skills are being commoditized and which are getting scarcer. I agree with her completely, and I want to extend her argument into the legal layer &#8212; because the moat she describes is also the legal moat, and most creators don&#8217;t see it yet.</p><h2>The AI Defense Doesn&#8217;t Exist</h2><p>The single most expensive misconception I see among content creators is this: &#8220;If I disclose I used AI, or if the AI generated it, I&#8217;m not liable.&#8221;</p><p>Wrong in every jurisdiction I practice in.</p><p>You are the publisher. Under Chinese law, EU law, and US law, the entity that distributes content owns the legal exposure. AI is not a legal person. AI cannot be sued, cannot be served process, cannot be held liable. The plaintiff comes after you.</p><p>China&#8217;s Interim Measures for the Administration of Generative AI Services (effective August 15, 2023) places obligations on both providers and users. Article 12 requires conspicuous labeling of generated images, videos, and other content. The Cyberspace Administration&#8217;s Measures for Labeling AI-Generated Synthetic Content (effective September 1, 2025) further specifies explicit and implicit labeling requirements.</p><p>The EU AI Act (Regulation 2024/1689, effective August 1, 2024) imposes transparency obligations on deep synthesis content that become mandatory from August 2026. The US is fragmented &#8212; the Copyright Office&#8217;s March 2023 guidance states that purely AI-generated works are not copyrightable, but the publisher liability framework under DMCA and state defamation law applies to whoever distributes.</p><p>If you operate across all three jurisdictions &#8212; TikTok plus &#23567;&#32418;&#20070; plus YouTube, say &#8212; you face stacked compliance. Compliant in China doesn&#8217;t mean compliant in the EU.</p><p>The &#8220;AI wrote it&#8221; defense is a legal fiction. Treat it as one.</p><h2>What Actually Gets Creators Sued</h2><p>In my casework over the past eighteen months, AI-related disputes cluster into three categories. None of them is about whether AI output has copyright.</p><p><strong>Training data infringement.</strong> A Chinese court in Guangzhou (2024 &#31908; 0192 &#27665;&#21021; 113&#21495;) ruled in early 2024 against an AI platform that had used Ultraman images without authorization to train its model. The platform paid damages and was ordered to cease. As a creator, you may not know what data trained the model you use. But if your output is identified as closely mimicking a specific IP, you can be drawn in.</p><p><strong>Output infringement.</strong> This is the most common one. The &#8220;AI laundering&#8221; case I handled last year: a Chinese content creator ran an English Substack piece through ChatGPT, published the rewrite, and got hit with a DMCA notice routed through to the Chinese platform. The client wanted to argue &#8220;the AI wrote it.&#8221; I told him the same thing I told you: legally, you&#8217;re the publisher, you eat the risk. We settled &#8212; apology plus modest payment. Cheaper than litigating.</p><p><strong>Failure to disclose.</strong> The most overlooked. Both Chinese and EU rules now impose labeling obligations. Most creators I talk to don&#8217;t label. The cost of disclosure is near-zero. The cost of getting caught not disclosing &#8212; especially in a regulated content category like financial advice, legal commentary, or medical information &#8212; is significant.</p><h2>The Three Things AI Cannot Do</h2><p>Jasmine Sun&#8217;s framing is right, and it maps directly onto what I see in legal practice: AI commoditizes the middle, and elevates the edges.</p><p>What AI commoditizes: generic explainers, summary writing, polite emails, structured essays following common templates. The first ten Google results for any informational query are about to become indistinguishable.</p><p>What AI cannot do, and what therefore becomes scarcer and more valuable:</p><p><strong>First-hand information.</strong> Cases I&#8217;ve actually worked. Conversations I&#8217;ve actually had with clients. Courts I&#8217;ve actually appeared in. Coffees I&#8217;ve actually had with Latin American counsel. This raw material &#8212; the unrecorded, unindexed lived experience of doing the work &#8212; is not in any training corpus and cannot be synthesized.</p><p><strong>Judgment with a point of view.</strong> AI produces hedged, risk-averse, middle-of-the-distribution answers. Real professional opinion has a stance. &#8220;The Mexican anti-corruption statute translates accurately, but in practice the prosecutor&#8217;s evidentiary logic runs differently &#8212; here&#8217;s how the case I worked last year actually played out.&#8221; That&#8217;s the answer clients pay for. AI cannot generate it because it cannot have had the experience.</p><p><strong>Human trust.</strong> Clients ultimately hire people they trust. AI can be helpful, articulate, even charming. It cannot build a real trust relationship over time. The lawyer who has been at the same email address for ten years, who returns calls, who remembers your last matter &#8212; that lawyer wins against the AI that has none of those properties.</p><p>The implication for creators is straightforward. Lean hard into the parts of your work that draw on first-hand experience, sharpen your stance, and build durable identity. Outsource the commoditized middle to AI if you want, but don&#8217;t compete with AI on the commoditized middle. You&#8217;ll lose.</p><h2>Three Compliance Habits Every AI-Assisted Creator Should Build</h2><p>If you&#8217;re using AI to assist your content workflow &#8212; and you should be &#8212; three habits keep you out of trouble.</p><p><strong>Document the process.</strong> Save your prompts. Note the model and version. Timestamp the generation. Record what you edited. I keep a simple Notion table for this. If a dispute arises, this is your evidentiary foundation. Without it, you&#8217;re arguing your innocence with no record of what happened.</p><p><strong>Disclose for commercial use.</strong> Paid work, sponsored content, professional advice &#8212; label AI assistance visibly. Both Chinese and EU rules now require it. Even where not strictly required, disclosure is a near-zero-cost trust signal. Audiences increasingly respect it.</p><p><strong>Verify every legal citation manually.</strong> AI hallucinates statutes and case numbers routinely. Last month a major model handed me a Supreme People&#8217;s Court judicial interpretation as if it were current law. It had been repealed in 2021. Had I published it in a client memo, my professional reputation would have taken a hit. For every specific citation &#8212; statute number, case number, quote, regulatory reference &#8212; verify at the official source. Westlaw, &#23041;&#31185;&#20808;&#34892;, &#21271;&#22823;&#27861;&#23453;, court websites. No exceptions.</p><h2>What This Means for You</h2><p>If you&#8217;re an independent writer or creator: AI is not a threat to your moat if you understand where the moat actually is. It&#8217;s in your first-hand experience, your stance, and the trust you&#8217;ve built. Use AI to handle the commodity layer faster, then invest the time saved into deepening the parts AI can&#8217;t touch.</p><p>If you&#8217;re running a content business across borders: stop assuming compliance in one jurisdiction equals compliance elsewhere. Map your distribution footprint to the disclosure regimes. Build the documentation habits before you need them.</p><p>If you&#8217;re a lawyer or professional advisor watching AI eat your industry: the same logic applies. The commodity layer of legal work &#8212; basic research, first-draft contracts, summary memos &#8212; is being commoditized. The high-margin work &#8212; judgment, strategy, courtroom presence, relationship &#8212; is becoming scarcer and more valuable.</p><p>I help cross-border content businesses and creators structure AI compliance frameworks, draft platform-specific disclosure policies, and handle copyright disputes that touch AI-assisted work. If that&#8217;s a fit for what you need, book a consultation at wzklaw.com?src=ss.</p><p>The independent creator&#8217;s advantage is real. Use it.</p><p>&#8212;&#8212;&#8212;<br>Mike Wu, China-licensed Attorney &#183; Cross-border practice<br>4 languages (CN/EN/ES/JA)<br>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p>]]></content:encoded></item><item><title><![CDATA[Two-Way Piercing: Why China and the US Quietly Aligned on Cracking Down on Chinese Outbound Investment]]></title><description><![CDATA[Two-Way Piercing: Why China and the US Quietly Aligned on Cracking Down on Chinese Outbound Investment]]></description><link>https://attorneymikewu.substack.com/p/two-way-piercing-why-china-and-the</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/two-way-piercing-why-china-and-the</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Wed, 03 Jun 2026 16:33:29 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h2>Two-Way Piercing: Why China and the US Quietly Aligned on Cracking Down on Chinese Outbound Investment</h2><p>The same week, two regulators on opposite sides of the Pacific issued new rules. They look unrelated. They&#8217;re not.</p><p>I&#8217;m Mike Wu, a China-licensed cross-border attorney based in Guangzhou. I spend most of my week structuring outbound deals for Chinese manufacturers going to Latin America, Southeast Asia, and increasingly North America&#8217;s nearshoring corridor. What I&#8217;m about to describe has rearranged my desk over the past 30 days.</p><h2>The Coincidence That Isn&#8217;t</h2><p>In late May 2026, China&#8217;s State Council released its updated Outbound Investment rules. Within days, the US Bureau of Industry and Security (BIS) updated its chip licensing guidance.</p><p>Read individually, each is a routine regulatory update. Read together, they reveal that Beijing and Washington &#8212; for entirely different reasons &#8212; have converged on the same enforcement technique: <strong>piercing through corporate structures to identify the real actor on the other side.</strong></p><p>China wants to know: where is your money actually going, and what sensitive industry will it serve?</p><p>The US wants to know: is this entity, regardless of where it&#8217;s registered, ultimately controlled by Chinese interests, and could the technology reach a controlled end-use?</p><p>For decades, Chinese outbound structures relied on intermediary jurisdictions &#8212; Hong Kong, Singapore, BVI, Cayman, increasingly UAE &#8212; to provide a layer of separation between the home company and the offshore operation. That separation worked because each regulator stayed in its own lane.</p><p>That lane is gone. The intermediary layer is now the most scrutinized layer.</p><h2>A Case That Crystallized It For Me</h2><p>In March 2026, an industrial equipment manufacturer engaged me after signing a letter of intent for an assembly plant in Baja California, Mexico. The plan was textbook nearshoring: produce in Mexico under USMCA, supply US clients, use the Mexican entity for tariff and tax efficiency.</p><p>The original structure: Shenzhen parent &#8594; Hong Kong holding &#8594; Mexican operating entity. Chips sourced from China. Assembled products exported to the US.</p><p>Under 2024 rules, clean. Under the rules in effect when they came to me, three landmines:</p><p><strong>Landmine one &#8212; Capital outflow disclosure.</strong> The new outbound rules require disclosure of ultimate use of funds and sensitive-industry classification. &#8220;General investment&#8221; no longer works as a description. We had to file accurately: equipment assembly serving US end customers. That triggered a higher-tier review.</p><p><strong>Landmine two &#8212; BIS coverage.</strong> The updated BIS guidance treats overseas subsidiaries of Chinese-controlled entities as &#8220;covered entities&#8221; for chip licensing purposes. Even though the Mexican factory was a Mexican legal entity with Mexican employees and Mexican operations, piercing through ownership made it Chinese-controlled. Their planned chip supplier became unusable for any product destined for US end-use.</p><p><strong>Landmine three &#8212; Re-export as circumvention.</strong> Assembled products containing controlled chips, re-exported to the US, can be deemed a circumvention pattern. The penalty for being deemed a circumventor isn&#8217;t a fine &#8212; it&#8217;s entity list designation, which kills the entire group&#8217;s US market access.</p><p>The solution required two structural changes. We introduced a Mexican strategic investor with US ties to dilute Chinese control below 50%, removing the entity from &#8220;Chinese-controlled&#8221; treatment. We swapped the chip supplier to a BIS-whitelisted alternative. The project lost four months and added compliance cost equivalent to roughly 3% of total project investment.</p><p>What it gained: it didn&#8217;t get investigated from both sides simultaneously.</p><h2>Why Intermediary Jurisdictions Stopped Working</h2><p>I want to dwell on this because most outbound playbooks still assume the old logic.</p><p>The traditional intermediary structure works on a simple premise: the regulator at each end can only see what&#8217;s directly in front of it. China sees Shenzhen sending money to Hong Kong. The US sees a Mexican company doing business with US customers. Neither sees the full chain.</p><p>That premise just died. Both regulators now require, by rule, that ultimate beneficial ownership be disclosed and considered. Both have developed enforcement tools &#8212; financial intelligence sharing, supply chain mapping, AI-assisted entity resolution &#8212; that make piercing through five-layer structures routine rather than exceptional.</p><p>Worse: complex structures now create their own risk. The more layers a transaction passes through, the higher the probability of being characterized as &#8220;designed to obscure&#8221; or &#8220;circumvention by design.&#8221; That characterization carries punitive treatment in both jurisdictions.</p><p>My current advice to clients: simplify ruthlessly. If the deal is genuinely Chinese-controlled, structure it as Chinese-controlled and accept the regulatory burden. If you genuinely want non-Chinese control for operational reasons, make it real &#8212; give up actual decision rights, not just paper ones. The half-measure of &#8220;diluted on paper, controlled in practice&#8221; is the worst of all worlds in 2026.</p><h2>What This Means For You</h2><p>If you&#8217;re a Chinese company with outbound operations, or considering them, here&#8217;s what I&#8217;d do this quarter:</p><p>First, audit your existing structures. Any deal closed before 2025 that relies on intermediary jurisdictions for substantive separation needs a fresh look. Grandfathering is narrow.</p><p>Second, move compliance upstream. About 60% of the inquiries I get arrive after an MOU is signed and key structural decisions are locked. Reverse that order. Counsel goes in before site selection and equity design, not after.</p><p>Third, recognize that &#8220;cross-border&#8221; is no longer one skill. It&#8217;s two &#8212; fluency in Chinese national-security framing AND fluency in US end-use and circumvention framing. They use different vocabulary, different presumptions, and different evidentiary standards. Counsel who can only speak one of these languages can only get you halfway.</p><p>Fourth, if your business touches semiconductors, AI, biotech, new energy, or critical minerals, double your compliance budget for 2026. This isn&#8217;t conservatism. It&#8217;s the realistic cost of operating across the new fault line.</p><p>If you&#8217;re navigating any of this and want a working session, I take a limited number of cross-border structuring consultations per month. Reach me at wzklaw.com?src=ss.</p><p>&#8212;&#8212;&#8212;<br>Mike Wu, China-licensed Attorney &#183; Cross-border practice<br>4 languages (CN/EN/ES/JA)<br>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p>]]></content:encoded></item><item><title><![CDATA[ China Just Issued Its First State Council Regulation on Outbound Investment. Here’s What It Actually Says.]]></title><description><![CDATA[# China Just Issued Its First State Council Regulation on Outbound Investment.]]></description><link>https://attorneymikewu.substack.com/p/china-just-issued-its-first-state</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/china-just-issued-its-first-state</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Tue, 02 Jun 2026 07:23:16 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p># China Just Issued Its First State Council Regulation on Outbound Investment. Here&#8217;s What It Actually Says.</p><p>For 20 years, China governed outbound investment through ministry-level rules. That era ended on June 1, 2026.</p><p>I&#8217;m Mike Wu, a cross-border lawyer based in Guangdong. On June 1, Xinhua officially released the full text of the **Regulations of the State Council on Outbound Investment** (State Council Order No. 837), together with a joint Q&amp;A from the Ministry of Justice (MOJ), the National Development and Reform Commission (NDRC), and the Ministry of Commerce (MOFCOM). The regulation enters into force on **July 1, 2026**.</p><p>I read the 34 articles and the Q&amp;A three times before writing this. Below is my working analysis for international clients, overseas Chinese, and fellow cross-border practitioners.</p><p>## The Four Dates You Cannot Confuse</p><p>Lawyers reading Chinese regulations often mix up the dates of passage, signing, publication, and effectiveness. For Order No. 837:</p><p>- **April 17, 2026** &#8212; passed at the 83rd State Council Executive Meeting</p><p>- **May 5, 2026** &#8212; signed by Premier Li Qiang as State Council Order No. 837</p><p>- **June 1, 2026** &#8212; full text + Q&amp;A published by Xinhua</p><p>- **July 1, 2026** &#8212; effective date</p><p>When citing the regulation in due diligence memoranda or compliance opinions, the proper form is: *Regulations of the State Council on Outbound Investment (State Council Order No. 837, effective July 1, 2026).*</p><p>## Why Now?</p><p>The Q&amp;A opens with one telling sentence: the model of governing outbound investment through &#8220;departmental rules and normative documents&#8221; no longer fits reality.</p><p>That&#8217;s bureaucratic language for a real structural shift. Over the past three years, three pressure points have built up in cross-border practice:</p><p>1. Individual Chinese residents using offshore SPVs, trusts, and real estate structures occupied a legal grey zone &#8212; neither clearly inside nor outside ODI compliance.</p><p>2. The line between &#8220;outbound investment&#8221; and &#8220;export of controlled technology, data, or services&#8221; became increasingly blurred as Chinese tech companies internationalized.</p><p>3. When Chinese investors faced discriminatory measures abroad, there was no direct domestic legal basis for countermeasures.</p><p>The new regulation addresses all three.</p><p>The drafting process itself signals seriousness: the MOJ ran **three rounds** of consultation with **more than 100 central and local entities**, plus expert panels and field research. This regulation will shape ODI compliance for years.</p><p>## Signal One: Individuals Are Now &#8220;Investors&#8221;</p><p>The Q&amp;A is explicit: *&#8221;Investors include enterprises, organizations, and resident individuals.&#8221;*</p><p>This single sentence reshapes the planning landscape for high-net-worth Chinese residents. Cross-border structures that have lived in compliance grey zones &#8212; offshore SPVs, family trusts, foreign real estate held for investment purposes &#8212; now sit squarely inside the ODI regulatory perimeter.</p><p>For my international clients, this matters in two ways. First, Chinese partners structuring joint ventures abroad may face additional individual-level filing requirements. Second, M&amp;A targets controlled by Chinese individuals through offshore vehicles need to be diligence with this regulation in mind, particularly for projects closing after July 1.</p><p>## Signal Two: A Hard Link to Export Controls</p><p>The regulation prohibits using outbound investment to:</p><p>- Export or use goods, technology, services, or data that China prohibits from export</p><p>- Use, without license, items subject to export licensing</p><p>- Transfer the above indirectly via cross-border personnel dispatch or technical guidance</p><p>That last clause is the one tech companies need to read twice. The historic workaround &#8212; &#8220;we&#8217;re not exporting the technology, we&#8217;re just sending engineers abroad to provide guidance&#8221; &#8212; is now explicitly closed.</p><p>Going forward, ODI projects involving technology transfer, cross-border SaaS, or sensitive data flows will likely need to clear **two parallel approvals**: the ODI filing/approval, and the export control license. Compliance teams should build this dual-track review into deal timelines.</p><p>## Signal Three: Penalties Scale With Investment Size</p><p>Article 27 is the teeth of this regulation. The penalty structure:</p><p>| Violation | Investor Fine | Personal Fine |</p><p>|---|---|---|</p><p>| Prohibited investment, refusal to comply | Confiscation + **5&#8240;&#8211;10&#8240;** of investment amount | **RMB 50,000&#8211;100,000** |</p><p>| Failure to file for approval/recordation | **1&#8240;&#8211;5&#8240;** of investment amount | **RMB 20,000&#8211;50,000** |</p><p>| Refusal to cure | Escalates to **5&#8240;&#8211;10&#8240;** | &#8212; |</p><p>Plus: **1&#8211;3 year ban on new outbound investment**; applications not accepted for up to 3 years.</p><p>The key word is *percentage*. ODI projects routinely involve hundreds of millions to billions of RMB. A 10&#8240; fine on a USD 200M project is USD 2M. This level of exposure forces GCs and CCOs to take the regulation seriously in a way fixed-amount fines never did.</p><p>## Signal Four: Sanctions Toolkit Formally Linked</p><p>The regulation addresses foreign discriminatory measures: China may conduct investigations, adjust country-specific investment policies, and exercise countermeasures under the **Anti-Foreign Sanctions Law**, including restrictions on foreign entities and individuals investing in or entering China.</p><p>For international clients, this means the political risk dimension of cross-border investment is now formally codified on the Chinese side. Cross-default scenarios &#8212; where measures by one government trigger countermeasures by another &#8212; have a clearer legal architecture.</p><p>## What This Means for You</p><p>If you have ODI projects in flight, offshore structures held by Chinese individuals, or technology/data flows between China and abroad, the next 30 days matter. My suggested checklist:</p><p>1. **Audit existing projects** against the new framework before July 1.</p><p>2. **Run an export control overlay** on any technology, data, or service flows.</p><p>3. **Restructure individual offshore holdings** where Chinese-resident individuals are ultimate beneficiaries.</p><p>4. **Anticipate security review** for sensitive sector or sensitive region projects.</p><p>5. **Front-load dispute resolution clauses** &#8212; the regulation explicitly endorses arbitration, mediation, and litigation. Pick your seat and rules deliberately (HKIAC, SIAC, ICC).</p><p>Cross-border legal work isn&#8217;t translation. It&#8217;s path-finding between two systems. State Council Order No. 837 just redrew the Chinese-side map. Make sure your structures still fit.</p><p>For specific questions on your outbound investment structure, joint venture, or cross-border tech transfer, you can reach me directly at mike@wzklaw.com or book a consultation at wzklaw.com/contact.php?source=substack&amp;src=ss. I practice in Chinese, English, Spanish, and Japanese.</p><p>&#8212;&#8212;&#8212;</p><p>Mike Wu, Attorney-at-Law &#183; Guangdong Jinglang Law Firm &#183; License 144012510953782</p><p>Cross-border practice &#183; 4 languages (CN/EN/ES/JA)</p><p>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p><p>Bar verification: credit.acla.org.cn</p>]]></content:encoded></item><item><title><![CDATA[ Korea Just Ended the "One Global Compliance" Era for Chinese Companies]]></title><description><![CDATA[# Korea Just Ended the &#8220;One Global Compliance&#8221; Era for Chinese Companies]]></description><link>https://attorneymikewu.substack.com/p/korea-just-ended-the-one-global-compliance</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/korea-just-ended-the-one-global-compliance</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Mon, 01 Jun 2026 16:27:24 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p># Korea Just Ended the &#8220;One Global Compliance&#8221; Era for Chinese Companies</p><p>Asia&#8217;s first comprehensive AI law is live. Here&#8217;s what changes &#8212; and what I&#8217;m advising my clients to do in the next 90 days.</p><p>I&#8217;m Mike Wu, a cross-border attorney based in Guangdong, China. I advise Chinese enterprises expanding into Asia, Europe, and Latin America on AI compliance, data protection, and cross-border contracts. I work in Chinese, English, Spanish, and Japanese.</p><p>Yesterday, Korea&#8217;s AI Basic Act officially entered into force &#8212; Asia&#8217;s first comprehensive AI regulation. In the last three months alone, I&#8217;ve fielded preliminary inquiries from five Chinese e-commerce and AI companies with Korean exposure. The conversations all started the same way: &#8220;We thought we had time.&#8221;</p><p>They don&#8217;t.</p><p>This newsletter is my honest read on what just changed, the most common compliance blind spots I&#8217;m seeing, and a 90-day roadmap for Chinese enterprises that already have &#8212; or plan to build &#8212; Korean operations.</p><p>## What Korea&#8217;s AI Basic Act Actually Does</p><p>The Act follows the structural template of the EU AI Act but with three uniquely Asian wrinkles.</p><p>**First**, the high-impact AI category &#8212; covering hiring, healthcare, credit scoring, energy, and public services &#8212; comes with mandatory pre-deployment obligations. If you&#8217;re a Chinese company offering AI recruitment software, AI credit scoring, or AI medical decision support to Korean users, you&#8217;re captured the moment the system goes live.</p><p>**Second**, generative AI content carries a hard labeling requirement. Every AI-generated image, every virtual influencer video, every AI chatbot interaction must carry an explicit &#8220;AI-generated&#8221; marker. This hits Chinese cross-border e-commerce particularly hard because virtual influencer livestreaming has become a dominant sales channel in Korea over the past 18 months.</p><p>**Third**, and most critically: the law applies extraterritorially. Your company can be incorporated in Shenzhen, your servers can be in Hangzhou, your team can be entirely in mainland China &#8212; if your AI services touch Korean users, Korean regulators have jurisdiction. The era of &#8220;we&#8217;re a Chinese company, we follow Chinese law&#8221; is over.</p><p>## The Real Risk Stack I&#8217;m Seeing</p><p>When clients come to me, I make them draw their data flow on paper before we talk law. Here&#8217;s what shows up most often.</p><p>A typical Chinese cross-border AI company has data flowing in four directions: Korean user data flowing back to China for model training, Chinese training data flowing to Korean cloud deployments, third-party API calls (often to US-based LLM providers), and inter-affiliate data sharing with the Korean subsidiary if one exists.</p><p>Every single one of these arrows now needs a legal basis under three regimes simultaneously: China&#8217;s PIPL plus Cross-Border Data Transfer Security Assessment, Korea&#8217;s PIPA, and the new Korean AI Act. The same byte of data crosses three regulatory gates.</p><p>The most common defense I hear from clients is: &#8220;But we&#8217;re just using OpenAI/Anthropic&#8217;s API &#8212; we don&#8217;t actually build AI models.&#8221; The Korean AI Act closes this door. Any entity that builds a public-facing service on top of a general-purpose AI model is classified as an AI service provider with full transparency, risk assessment, and user notification obligations. SaaS shielding doesn&#8217;t work anymore.</p><p>## A Case I Worked Last Quarter</p><p>A Guangzhou-based cross-border e-commerce company doing roughly USD 24 million in GMV through Korean AI virtual livestreamers came to me in Q4 2025. Their model: train AI models in China, deploy via cloud to Korea, run Korean-language virtual influencers on Coupang and Naver Shopping, and feed user behavior data back to Guangzhou for model iteration.</p><p>Their CEO opened with: &#8220;Should we set up a Korean entity?&#8221;</p><p>My answer: &#8220;You&#8217;re at least a year late &#8212; but we can still salvage this.&#8221;</p><p>Three problems jumped out immediately. Data flowing back from Korea to China was running through zero formal channels &#8212; non-compliant under China&#8217;s outbound transfer regime and clearly violating PIPA on cross-border personal information transfers. Their virtual influencers carried no AI-generated labeling, which is now a punishable violation under the new Korean AI Act. And the company had zero Korean legal presence, meaning no compliance contact point during any regulatory inquiry.</p><p>The fix took shape in three phases: immediate AI-content labeling deployment, Korean subsidiary plus local representative within 60 days, and a fundamental data architecture rebuild &#8212; training data localized in Korea, with only model weights (not raw user data) flowing back to China.</p><p>## What This Means for You</p><p>If you&#8217;re a Chinese company with any Korean exposure &#8212; direct sales, AI deployment, data processing, or even just Korean users hitting your service &#8212; you need to act in 2026, not 2027.</p><p>My 90-day playbook for clients:</p><p>**Weeks 1-2**: Map every Korea-touching business line and draw the data flow on paper. You cannot fix what you cannot see.</p><p>**Month 1**: Korean-language privacy policy, user agreement, and AI disclosure. AI-generated content labeling system deployed across all consumer-facing surfaces.</p><p>**Month 2-3**: Bilateral cross-border data review &#8212; China outbound assessment plus Korean PIPA evaluation. Establish or confirm a Korean local representative.</p><p>**Beyond Day 90**: For high-impact AI systems, prepare an Algorithmic Impact Assessment ahead of launch. Korea requires this *before* deployment, not after &#8212; unlike the EU&#8217;s audit-based regime.</p><p>## My Forecast</p><p>Korea is the first domino. Japan&#8217;s AI Promotion Basic Act draft will likely move through the Diet by mid-2027. India&#8217;s Digital India Act is in late-stage consultation. Singapore&#8217;s Model AI Governance Framework will harden into binding rules within 24 months.</p><p>The &#8220;one global compliance framework&#8221; approach that Chinese companies relied on through 2024 is dead. Asian AI regulatory fragmentation is the new baseline, and the cost of cross-border AI compliance will become a material P&amp;L line for any Chinese company with serious international ambitions.</p><p>For Chinese clients planning Asian expansion in 2026-2027, I&#8217;m currently advising on Korea-Japan-Southeast Asia AI compliance playbooks in four languages. If your company has Korean exposure and you&#8217;d like to think through your compliance posture, you can book a consultation directly at wzklaw.com?src=ss.</p><p>The 2026 window is closing fast. Build the architecture now, while it&#8217;s still cheap.</p><p>&#8212;&#8212;&#8212;</p><p>Mike Wu, Attorney-at-Law &#183; Guangdong Jinglang Law Firm &#183; License 144012510953782</p><p>Cross-border practice &#183; 4 languages (CN/EN/ES/JA)</p><p>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p><p>Bar verification: credit.acla.org.cn</p>]]></content:encoded></item><item><title><![CDATA[China's Three Cross-Border Data Paths: What Most General Counsels Get Wrong]]></title><description><![CDATA[# China&#8217;s Three Cross-Border Data Paths: What Most General Counsels Get Wrong]]></description><link>https://attorneymikewu.substack.com/p/chinas-three-cross-border-data-paths</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/chinas-three-cross-border-data-paths</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Sat, 30 May 2026 17:54:55 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p># China&#8217;s Three Cross-Border Data Paths: What Most General Counsels Get Wrong</p><p>Most companies do not need a CAC Security Assessment. The real trap is the middle tier &#8212; and that&#8217;s exactly where in-house teams keep falling.</p><p>I am a cross-border lawyer based in Guangzhou. Roughly eight out of ten data compliance inquiries I receive begin with the same anxious question: &#8220;Do we need to file a Security Assessment with the Cyberspace Administration of China?&#8221;</p><p>The honest answer, for the majority, is no. But many of those same companies *do* fall under the Standard Contract Filing or PI Protection Certification track &#8212; and that obligation is routinely overlooked, sometimes for years, until a counterparty&#8217;s legal team or a regulator&#8217;s spot check forces a panicked retrofit.</p><p>This newsletter walks you through the framework as it stands today under China&#8217;s *Regulations on Promoting and Standardizing Cross-Border Data Flows* (effective March 22, 2024), the *Personal Information Protection Law* (PIPL) Article 38, and the *Measures for Security Assessment of Outbound Data Transfer* (effective September 2022). I&#8217;ll also flag three blind spots I see in nearly every audit I run.</p><p>## The Three-Tier Framework</p><p>Think of cross-border data transfer obligations in China as three concentric circles. The smallest, innermost circle is the most regulated; the outermost is exempt.</p><p>**Tier 1 &#8212; Mandatory CAC Security Assessment.** This is triggered if any one of the following applies:</p><p>- A Critical Information Infrastructure Operator (CIIO) transfers personal information or important data abroad;</p><p>- Any data handler transfers **important data** abroad;</p><p>- A non-CIIO transfers **personal information of one million or more individuals** (non-sensitive) cumulatively, counted from January 1 of the current year;</p><p>- A data handler transfers **sensitive personal information of ten thousand or more individuals** cumulatively, counted from January 1 of the current year.</p><p>A key piece of regulatory relief in the 2024 update: if your data has not been formally designated as &#8220;important data&#8221; by an authority or publicly announced as such, you are *not* required to file as such. That said, I advise clients to maintain internal classification records anyway &#8212; if an industry catalog is later released, or if you receive a notification, you need to pivot quickly.</p><p>**Tier 2 &#8212; Standard Contract Filing or PI Protection Certification.** For non-CIIOs, the thresholds are:</p><p>- Non-sensitive personal information of **one hundred thousand to under one million** individuals; or</p><p>- Sensitive personal information of **fewer than ten thousand** individuals.</p><p>The legal basis sits in PIPL Article 38, which provides three lawful pathways for transferring personal information abroad: Security Assessment, PI Protection Certification, and the CAC Standard Contract. Tier 2 covers the latter two.</p><p>**Tier 3 &#8212; Exempt.** Transfers falling into the following categories do not require any of the above formal procedures:</p><p>- Non-CIIO transfers of non-sensitive PI involving **fewer than one hundred thousand** individuals;</p><p>- Transfers necessary to perform a contract with the individual (cross-border purchase, remittance, ticketing, hotel booking, visa application);</p><p>- Cross-border HR management conducted under lawful internal rules or collective agreements;</p><p>- International trade, cross-border logistics, academic cooperation, and global manufacturing/marketing activities where no personal information or important data is involved;</p><p>- Emergency transfers to protect a natural person&#8217;s life, health, or property.</p><p>## What the 45 Working Days Really Mean</p><p>The statutory review timeline for a Security Assessment is 45 working days, extendable. Clients ask me, almost reflexively, &#8220;So we can have approval in 45 days?&#8221;</p><p>In practice, the bottleneck is rarely the formal review window. It&#8217;s the intake completeness check, the supplemental submission rounds, and the informal pre-filing alignment with provincial cyberspace authorities. I generally counsel clients to decouple their compliance timeline from product launch timelines &#8212; building a generous buffer is cheaper than the alternative.</p><p>## Three Blind Spots I See in Almost Every Audit</p><p>**Blind spot 1: confusing the 100k threshold with the Security Assessment trigger.**</p><p>The 100,000-individual threshold for non-sensitive PI sits inside Tier 2 (Standard Contract Filing). The Security Assessment trigger for non-sensitive PI is **one million**. Treating 100k as the assessment trigger over-reports your obligations and burns legal budget on the wrong pathway.</p><p>**Blind spot 2: mixing sensitive and non-sensitive PI in a single headcount.**</p><p>PIPL defines sensitive PI specifically: biometrics, religious beliefs, specific identity, medical health, financial accounts, location tracking, and information of minors under 14. The thresholds are counted *separately*:</p><p>- Non-sensitive: 100k / 1M</p><p>- Sensitive: 10k</p><p>A company with 8,000 sensitive records and 50,000 non-sensitive records lands in Tier 3 (exempt on both counts). A company with 12,000 sensitive records lands in Tier 2 regardless of non-sensitive volume. The two lines never merge.</p><p>**Blind spot 3: starting the cumulative count from the wrong date.**</p><p>The regulation says &#8220;cumulatively since January 1 of the current year.&#8221; Not since company incorporation. Not since contract execution. Not a rolling 12-month window. **Every January 1, the counter resets.**</p><p>For cross-border e-commerce and SaaS companies, this matters enormously. A single peak season &#8212; Black Friday, Singles&#8217; Day, year-end sales &#8212; can push the cumulative volume past a tier boundary. Smart legal teams run a quarterly reconciliation in April, July, and October, with a final check before December 31.</p><p>## What This Means for You</p><p>If you run cross-border operations touching China &#8212; whether as a multinational with a Chinese subsidiary, an outbound Chinese company sharing data with overseas affiliates, or a foreign SaaS vendor serving Chinese enterprise customers &#8212; three actions belong on your roadmap this quarter:</p><p>1. **Run a baseline classification.** Inventory your data flows by sensitivity, headcount, and destination jurisdiction.</p><p>2. **Map your tier honestly.** Don&#8217;t over-file. Don&#8217;t under-file. Document the rationale.</p><p>3. **Maintain an internal &#8220;important data&#8221; identification log**, even if you currently fall outside the formal trigger.</p><p>If you&#8217;d like a tailored review for your specific data flows, I work with cross-border counsel and in-house teams in English, Chinese, Spanish, and Japanese. Reach out at wzklaw.com/contact.php?source=substack&amp;src=ss &#8212; happy to compare notes on your specific scenario.</p><p>&#8212;&#8212;&#8212;</p><p>Mike Wu, Attorney-at-Law &#183; Guangdong Jinglang Law Firm &#183; License 144012510953782</p><p>Cross-border practice &#183; 4 languages (CN/EN/ES/JA)</p><p>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p><p>Bar verification: credit.acla.org.cn</p>]]></content:encoded></item><item><title><![CDATA[Why My Work Email Is mike@wzklaw.com — Not Gmail, Not QQ]]></title><description><![CDATA[# Why My Work Email Is mike@wzklaw.com &#8212; Not Gmail, Not QQ]]></description><link>https://attorneymikewu.substack.com/p/why-my-work-email-is-mikewzklawcom</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/why-my-work-email-is-mikewzklawcom</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Fri, 29 May 2026 16:20:59 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p># Why My Work Email Is mike@wzklaw.com &#8212; Not Gmail, Not QQ</p><p>It&#8217;s not about security. Here&#8217;s the real reason.</p><p>I&#8217;m a cross-border lawyer based in Guangzhou. I spent 15 years in computer science before entering the legal profession, and the last 8 years in international practice across Latin America, Japan, and the English-speaking world. I work in four languages.</p><p>When clients first contact me, one question comes up a lot &#8212; especially from fellow lawyers: &#8220;Mike, why are you running your own email domain? Isn&#8217;t Gmail safer? Isn&#8217;t it easier?&#8221;</p><p>Today I want to answer that honestly, because most of the answers I see online are, frankly, dishonest.</p><p>## The Uncomfortable Admission Most Lawyers Won&#8217;t Make</p><p>Let me start with something most &#8220;self-hosted email evangelists&#8221; refuse to say out loud:</p><p>**A self-hosted email is NOT more secure than Gmail.**</p><p>Google&#8217;s security team has thousands of engineers. They have decades of adversarial experience, global anti-phishing infrastructure, and threat intelligence I will never match as a solo lawyer running my own mail server. Even with 2FA, DKIM, SPF, DMARC properly configured &#8212; and I do configure them, my CS background helps &#8212; I&#8217;m at best close to Gmail&#8217;s baseline. I&#8217;m not &#8220;beating&#8221; Google on raw attack resistance.</p><p>So if you ever see a lawyer-blogger telling you &#8220;self-hosted email is safer, hire me to set it up&#8221; &#8212; please close that tab. That pitch isn&#8217;t honest.</p><p>Then why bother? Because the real question is not &#8220;will it be hacked?&#8221; The real question is: **where does the data physically live, which jurisdiction governs it, and who ultimately controls access to it?**</p><p>That question has three answers, and all three matter for a cross-border lawyer.</p><p>## Reason One: The Lawyer&#8217;s Duty of Confidentiality</p><p>China&#8217;s Lawyers Law imposes a statutory duty of confidentiality on lawyers regarding client information acquired in practice.</p><p>This duty doesn&#8217;t say &#8220;use a specific email provider.&#8221; It says: protect client information. Period.</p><p>Now think about what happens when a client sends me sensitive material &#8212; banking records, share structures, family dispute details &#8212; over Gmail. The moment that email is transmitted, a copy lives on Google&#8217;s servers, physically located offshore. If Google ever accesses, scans, retains, or hands over that data &#8212; whether for compliance, internal audit, lawful request, or any other reason &#8212; I have **zero control** over the process. I won&#8217;t even know.</p><p>Strictly speaking, this isn&#8217;t a &#8220;violation&#8221; of that duty. Chinese law doesn&#8217;t dictate email providers. But it does sit at the edge of the duty. When I physically hand client data to a third party I cannot constrain &#8212; especially one outside Chinese jurisdiction &#8212; my ability to fulfill my confidentiality duty is structurally weakened.</p><p>A custom domain doesn&#8217;t make data invisible. It puts the question of &#8220;where does this live, who can access it&#8221; back into the lawyer&#8217;s hands. That&#8217;s the first reason.</p><p>## Reason Two: PIPL Cross-Border Data Transfer (The Decisive One)</p><p>This is the reason that actually made me commit.</p><p>China&#8217;s Personal Information Protection Law (PIPL), Articles 38&#8211;43, governs the cross-border transfer of personal information. Lawful pathways include: a government security assessment, certification by a designated body, signing the standard contractual clauses, or &#8212; critically &#8212; obtaining **separate, specific consent** from the individual.</p><p>So here&#8217;s the operative question: **when a Chinese lawyer uses Gmail to handle Chinese clients&#8217; personal data, is that a cross-border transfer?**</p><p>My professional judgment: **yes.**</p><p>Gmail&#8217;s servers are physically offshore &#8212; primarily in the United States and other non-China nodes. When a Chinese lawyer sends or receives client personal data (names, ID numbers, addresses, contracts, dispute facts) through Gmail, the data crosses the border at the moment of storage. Legally, this is no different from exporting a database from a domestic server to an offshore one.</p><p>To do this compliantly under PIPL, the lawyer would need to:</p><p>1. Inform the client of the overseas recipient&#8217;s identity, contact, purpose, and methods</p><p>2. Obtain the client&#8217;s **separate consent** (not a checkbox in a privacy policy &#8212; separate, specific consent)</p><p>3. Depending on volume and classification, potentially undergo a Cyberspace Administration of China security assessment</p><p>Realistically &#8212; does any solo practitioner run that workflow for every client? **Almost no one.**</p><p>What about Tencent&#8217;s QQ Mail or NetEase 163? Data stays domestic, so PIPL&#8217;s cross-border issue is sidestepped. But a different problem appears: the lawyer still cannot constrain Tencent&#8217;s or NetEase&#8217;s access. Highly sensitive client data sits in a provider&#8217;s domestic data center, and the law firm&#8217;s emails are not on any &#8220;confidentiality exemption list&#8221; when the provider runs internal audits or responds to regulatory inquiries.</p><p>The real value of a custom domain on compliant in-country infrastructure is that I can choose:</p><p>- **Data residency** &#8212; I host on a compliant in-country provider; PIPL cross-border issue does not arise</p><p>- **Access rules** &#8212; beyond me and authorized ops, no third party scans or retains email content</p><p>- **Auditability** &#8212; I can show clients a complete, explainable data-handling chain</p><p>This isn&#8217;t &#8220;more secure.&#8221; It&#8217;s **more compliant.** Those are different words and they matter.</p><p>## Reason Three: The Lowest-Cost Step in Building Cross-Border Trust</p><p>The third reason is the most practical.</p><p>My clients write in English, Spanish, and Japanese. When an overseas client first contacts me, seeing `someone1987@gmail.com` versus `mike@wzklaw.com` produces meaningfully different professional impressions. The latter:</p><p>- Matches the firm&#8217;s domain (wzklaw.com/contact.php?source=substack&amp;src=ss)</p><p>- Can be cross-verified against the Chinese bar registry (credit.acla.org.cn, license 144012510953782)</p><p>- Reliably reaches enterprise inboxes (Outlook, Gmail) with proper SPF/DKIM/DMARC, avoiding spam folders</p><p>I&#8217;ve had Mexican, Chilean, and Japanese clients tell me &#8212; explicitly &#8212; that their first due-diligence step was matching my email domain against the firm&#8217;s website. For cross-border work, this is table stakes.</p><p>## What This Means For You</p><p>If you&#8217;re a lawyer &#8212; especially a cross-border lawyer &#8212; here are three concrete steps:</p><p>1. **Get a custom domain.** A few hundred RMB or USD a year. No technical barrier.</p><p>2. **Enforce SSL/TLS and 2FA.** Never use POP 110 or IMAP 143 in plaintext. 2FA is a floor, not a choice.</p><p>3. **Know where your provider physically stores the data.** Many &#8220;business email&#8221; services use a custom domain but store data in Google Workspace or Microsoft 365 offshore servers. **Domain ownership and data residency are two different things.** PIPL looks at the second.</p><p>And if you&#8217;re a client &#8212; overseas, in China, or doing cross-border work &#8212; it&#8217;s a fair question to ask any lawyer you hire: &#8220;Where does my data live? Can you explain the path?&#8221; A lawyer who can answer that clearly is a lawyer who&#8217;s thought about it.</p><p>## One Last Honest Line</p><p>There is no absolutely secure system. Not Gmail. Not Tencent. Not self-hosted. Anyone telling you otherwise is selling something.</p><p>I made this choice not because I&#8217;m &#8220;better.&#8221; I made it because, as a cross-border lawyer, I want my data-handling path to be fully explainable to every client, and defensible under PIPL, the Lawyers Law, and a foreign client&#8217;s scrutiny.</p><p>That&#8217;s the whole reason.</p><p>If this resonates, I write here every week or two &#8212; on cross-border legal practice, PIPL, Latin American compliance, AI and the law, and what an actual practicing China lawyer thinks about all of it. No courses, no funnels, just honest field notes.</p><p>If you have a cross-border matter, you can reach me through wzklaw.com/contact.php?source=substack&amp;src=ss or book a consultation at wzklaw.com/contact.php?source=substack&amp;src=ss.</p><p>&#8212;&#8212;&#8212;</p><p>Mike Wu, Attorney-at-Law &#183; Guangdong Jinglang Law Firm &#183; License 144012510953782</p><p>Cross-border practice &#183; 4 languages (CN/EN/ES/JA)</p><p>Site: wzklaw.com/contact.php?source=substack&amp;src=ss &#183; Book consultation: wzklaw.com/contact.php?source=substack&amp;src=ss</p><p>Bar verification: credit.acla.org.cn</p>]]></content:encoded></item><item><title><![CDATA[From Qiaopi Letters to Bilingual Shareholders’ Agreements: What a Teochew Film Taught Me About Cross-Border Wealth]]></title><description><![CDATA[From Qiaopi Letters to Bilingual Shareholders&#8217; Agreements: What a Teochew Film Taught Me About Cross-Border Wealth]]></description><link>https://attorneymikewu.substack.com/p/from-qiaopi-letters-to-bilingual</link><guid isPermaLink="false">https://attorneymikewu.substack.com/p/from-qiaopi-letters-to-bilingual</guid><dc:creator><![CDATA[Attorney Mike Wu]]></dc:creator><pubDate>Mon, 25 May 2026 06:40:00 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CPqj!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F59488b40-e478-4074-a6bd-4cba2fe3b58e_144x144.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p># From Qiaopi Letters to Bilingual Shareholders&#8217; Agreements: What a Teochew Film Taught Me About Cross-Border Wealth</p><p>A Teochew-language film opened at 9.0 on Douban this month. Here&#8217;s why a cross-border lawyer cried in the theater &#8212; and what it means for any Chinese family with assets abroad.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://attorneymikewu.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Attorney's Substack! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>I&#8217;m Mike Wu. I practice cross-border law out of Guangdong, China, in four languages (Chinese, English, Spanish, Japanese). I&#8217;m also Teochew (Chaoshan) by origin &#8212; a small region in southern China with an outsized diaspora across Southeast Asia, and lately, across Latin America.</p><p>This week I watched *Letters to Grandma* (&#12298;&#32473;&#38463;&#23351;&#30340;&#24773;&#20070;&#12299;), the third Teochew-language film by director Lan Hongchun, released nationally on May 3, 2026. The film opened at 9.0 on Douban. Ninety-five percent of the dialogue is in Teochew. It was shot on location in Shantou&#8217;s old quarter and at the Thai-style temple in Chaozhou.</p><p>The plot, in one sentence: a grandmother in Shantou has lived her whole life believing her husband &#8212; who fled south during the civil war to escape conscription &#8212; would one day return. Her grandson secretly travels to Thailand to look for him. He discovers the grandfather died in 1960. The stranger registered as the gravetender is a woman the family has never heard of.</p><p>The director has said over 90% of the plot comes from real overseas Chinese stories he gathered while filming the documentary *Flavors of the Four Seas*.</p><p>It is, on the surface, a film about memory, separation, and the silent griefs of a generation that left home and never returned.</p><p>It is also, for someone in my profession, the most concise lecture on cross-border legal risk I have ever sat through.</p><p>## I. The Qiaopi System Was Brilliant &#8212; and Insufficient</p><p>Between 1864 and 1911, roughly 2.94 million Teochew people emigrated to Southeast Asia. Their lifeline to home was the **qiaopi** (&#20392;&#25209;) &#8212; a &#8220;letter-and-remittance-in-one&#8221; delivered by a private network of water-couriers, remittance houses, and door-to-door messengers. There was no SWIFT, no central bank clearing, no foreign exchange license. The whole system ran on Teochew clan reputation. In 2013, UNESCO inscribed the qiaopi archives on the Memory of the World Register.</p><p>I have enormous respect for what qiaopi accomplished. As a piece of pre-modern financial infrastructure built by an ethnic minority across multiple jurisdictions, it was extraordinary.</p><p>But it could not solve three things:</p><p>1. When a family member died abroad, the family back home often didn&#8217;t know.</p><p>2. The family rarely knew what assets, business interests, or new relationships existed overseas.</p><p>3. Even when they eventually found out, no one knew which country&#8217;s law applied, who to call, or how many years it would take.</p><p>The grandmother in the film lives her entire life never learning her husband died in 1960. This is not dramatic license. This is what was statistically normal for diaspora families of that era.</p><p>## II. The Modern Form of the Same Problem</p><p>Fast-forward to today. The Chinese &#8212; and particularly the Teochew &#8212; diaspora is no longer just in Southeast Asia. It is in Mexico, Brazil, Peru, Spain, Japan, the United States. The capital flows are larger. The legal complexity is greater. The family structures are more cross-jurisdictional than ever.</p><p>And yet, three patterns keep landing on my desk:</p><p>### Pattern One: Scattered overseas assets, no inventory</p><p>A founder dies. The family knows there&#8217;s &#8220;something&#8221; in Malaysia, &#8220;some shares&#8221; in Mexico, &#8220;an account&#8221; in Bangkok, and &#8220;maybe some crypto.&#8221; No spreadsheet. No list. No designated successor.</p><p>In my experience, **cross-border probate starts at one year per jurisdiction**. Three-country estates routinely take three years. Add a contested overseas marriage or an unacknowledged child, and five to eight years is realistic. Legal fees compound the pain.</p><p>### Pattern Two: Handshake deals still run the diaspora economy</p><p>Teochew business networks operate on extraordinary levels of in-group trust. A few sentences in Teochew dialect and both sides know whether the other is &#8220;one of us.&#8221; This trust has built fortunes.</p><p>But the same trust, applied to cross-border deals without paperwork, has destroyed them.</p><p>I have seen cases where a Chinese investor put up the entire capital for a Southeast Asian factory, registered the shares in a &#8220;trusted villager&#8217;s&#8221; name, and ten years later discovered:</p><p>- No nominee shareholding agreement was ever signed</p><p>- No capital contribution records exist in writing</p><p>- The nominee got married locally, and under local law the spouse now claims community property in the company</p><p>What started as a simple favor between fellow villagers becomes a multi-year cross-border family-and-commercial litigation across two or three jurisdictions.</p><p>### Pattern Three: Zero planning for residency, marriage, and succession</p><p>The typical mature-stage configuration of a Chinese entrepreneur who has been overseas for fifteen years: physically resident in Kuala Lumpur or Bangkok, a local family, assets in four or five countries, unclear tax residency, no will, no trust, no insurance-based succession structure.</p><p>When something happens, **every jurisdiction takes its own cut according to its own rules**. China applies its conflict-of-laws rules. Malaysia may apply both civil and religious inheritance law if a Muslim spouse is involved. Thailand applies its own civil and commercial code. Add U.S. green card status or a European residency, and estate tax exposure stacks up fast.</p><p>## III. What I Tell My Clients</p><p>When a Chinese entrepreneur &#8212; Teochew or otherwise &#8212; sits across from me planning an outbound investment, I push the same checklist:</p><p>**Before going out:**</p><p>- Holding structure and tax residency designed with both lawyer and accountant before the first dollar moves</p><p>- Cross-border capital flow compliance (to avoid later characterization as illicit outflow)</p><p>**While operating overseas:**</p><p>- All material contracts bilingual; governing law, jurisdiction, and arbitration seat explicit</p><p>- Key transactions documented in writing, email, and bank records</p><p>- Every share transfer, capital increase, and dividend formalized through corporate resolutions</p><p>**Family layer:**</p><p>- Pre-marital property agreements for cross-border marriages (and ideally signed *before* the wedding &#8212; many jurisdictions don&#8217;t enforce post-marital agreements the same way)</p><p>- Trusts or life insurance structures for risk isolation on significant assets</p><p>**Succession layer:**</p><p>- Overseas asset inventory updated annually</p><p>- Separate wills drafted under each asset jurisdiction&#8217;s law (a single will often fails in multi-jurisdictional probate)</p><p>- Access arrangements for keys, wallets, and accounts pre-positioned with trusted parties (this matters especially for crypto)</p><p>## IV. What This Means for You</p><p>If you are a Chinese entrepreneur with assets, businesses, or family members across borders &#8212; or a Latin American, Japanese, or Western counterpart working with Chinese partners &#8212; the lesson from a small Teochew-language film with a 9.0 Douban rating is this:</p><p>A century ago, our families relied on a single qiaopi letter to hold two homes together across an ocean. The system was beautiful, and it broke families.</p><p>Today, that role belongs to a properly drafted bilingual shareholders&#8217; agreement, a clean corporate structure, and a multi-jurisdictional estate plan. None of these are exotic. All of them are within reach of a one- to two-day engagement with the right lawyer.</p><p>**Sentiment belongs to people. Wealth and succession belong to institutions.**</p><p>The most expensive cross-border legal problems I have ever handled are problems that could have been prevented in their entirety with two or three documents drafted before the founder&#8217;s first overseas trip.</p><p>If you are sitting on a structure that &#8220;we&#8217;ll formalize later,&#8221; or if you have overseas assets without an inventory &#8212; please don&#8217;t wait. The cost of structuring before is rounding error. The cost of litigating after is generational.</p><p>I take direct consultations in Chinese, English, Spanish, and Japanese. You can book through wzklaw.com/booking.php?src=ss or reach me at mike@wzklaw.com.</p><p>&#8212;&#8212;&#8212;</p><p>Mike Wu, Attorney-at-Law &#183; Guangdong Jinglang Law Firm &#183; License 144012510953782</p><p>Cross-border practice &#183; 4 languages (CN/EN/ES/JA)</p><p>Site: wzklaw.com  Book consultation: wzklaw.com/booking.php</p><p>Bar verification: credit.acla.org.cn</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://attorneymikewu.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Attorney's Substack! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>