The cross-border decision: where your organization may ship its AI feature, defended with citations
The short answer
The cross-border decision is the module's payoff
Every earlier topic (the United States mosaic, the frameworks, the divergence, standards versus law) was an input. This topic produces the artifact they were for: a written, cited, defensible determination of where a specific AI feature may ship, and on what terms.
What you will be able to do
- Evaluate where your organization may lawfully ship a specific AI feature by running each destination jurisdiction through two questions in order: does its law reach this feature, and may the feature lawfully operate there given what it does with data and decisions.
- Distinguish the four defensible shipping outcomes for any jurisdiction (ship as built, ship with modifications, exclude the jurisdiction by geofencing or feature-gating, or delay pending change) and justify which one a given destination demands.
- Apply the territorial-scope rules that decide reach, so you never draw the map by your headquarters: the European Union's General Data Protection Regulation (GDPR) Article 3 (targeting and monitoring), the EU AI Act's Article 2 (output used in the Union), and the extraterritorial reach of laws like China's Personal Information Protection Law (PIPL) and Brazil's General Data Protection Law (Lei Geral de Proteção de Dados, LGPD).
- Judge whether a data-hungry AI feature (one that trains on or transfers user data across borders) can lawfully do so, using the correct legal basis, cross-border transfer mechanism, and data-localization check for each destination.
- Produce a cross-border shipping decision memo: a per-jurisdiction table stating the reach, the operative law, the conditions, the shipping call, and a citation for each, with the single riskiest destination flagged.
- Defend that memo against the two hardest challenges: that the feature "is fine because it is legal at home," and that a jurisdiction can be ignored because the organization has no office there.
- Sequence the operate-gate checks correctly (legal basis, then data localization, then transfer mechanism, then use and disclosure rules, then market-entry authorization), so you never design a transfer for data you cannot lawfully process or cannot lawfully move.
- Separate the market-entry question from the data-transfer question, so a feature served entirely inside a market is still tested for any filing, registration, assessment, or local-representative duty that conditions offering it there at all.
- Resolve a genuine conflict between two destinations' demands by choosing among the strictest-common version, per-jurisdiction versions, or geofencing, and naming which resolution you chose and why.
- Recognize that a shipping decision is a living commitment: a regulator's action (as in the ANPD Meta case) can change the answer for a destination overnight, so the memo carries review triggers, not a permanent verdict.
The ideas, one by one
Two gates, in order: reach, then operate
First, does the destination's law reach the feature (targeting, monitoring, output used, data processed)? Then, given that it reaches you, may the feature lawfully operate there (legal basis, transfer mechanism, localization, use and disclosure rules)? Applicability is not the decision; the operating call is.
The map is drawn by people and output, never by your office
GDPR Article 3, EU AI Act Article 2(1)(c), Brazil's LGPD Article 3, and China's PIPL Article 3 are all extraterritorial. The ANPD reached a United States company for processing Brazilians' data. List destinations by where your users, data subjects, and output are.
Every destination gets exactly one of four calls
Ship as built, ship with modifications (list them), exclude the jurisdiction (geofence or feature-gate), or delay pending change (with a trigger and date). A destination without exactly one call and its conditions is not a decision; it is an unanswered question.
A data-hungry feature lives or dies on legal basis and transfer mechanism
The Meta case turned on the legal basis for training (legitimate interests was found inadequate in Brazil and challenged in the European Union) and, for many features, on the cross-border transfer mechanism. For a feature that trains on user data, these two checks decide the operate gate.
"Legal at home" and "no office there" are the two fatal fallacies
Meta shipped one AI-training policy worldwide; Brazil suspended it for the same conduct. Reach follows the people, not the building. Run every destination through its own gates; never extrapolate from home or assume an office is required for a law to reach you.
Public data is not a free pass to train
The ANPD found that using "publicly available" posts to train AI still required a valid legal basis and adequate notice under the LGPD. Visibility is not a legal basis; the destination's data-protection law governs training on public data.
The decision is a living commitment
Regulators act in weeks (the ANPD suspended Meta in July and revoked in August 2024), adequacy decisions get challenged, transfer rules change. The memo carries review triggers and dates so a moved destination triggers a scheduled re-decision, not a headline.
Localization can override the transfer mechanism
A transfer instrument authorizes a permitted move; it cannot authorize a forbidden one. Where hard localization applies (Russia's 152-FZ), the data cannot leave, and the call narrows to in-country processing or exclusion. Check localization before relying on any transfer route, because it sits above it.
The decision is not only about walls; it is about doors
Some destinations (India's default-open transfer regime) are more permissive than a cautious team assumes, and over-complying delays a lawful launch. A defensible memo marks "ship as built" where the analysis supports it, correctly identifying open doors as well as closed ones.
Wire the decision into your operating framework
The memo is an input to the NIST Map function and a maintained record in an ISO/IEC 42001 management system, not a one-off in a lawyer's inbox. Framework-routed review triggers are what keep the decision alive when a destination moves.
Order the operate-gate checks: basis, then localization, then transfer, then disclosures, then market entry
There is no point arranging a transfer for data you have no basis to process, or a transfer instrument for data a localization rule forbids from leaving. Running the checks out of order produces confident answers to the wrong question. Market entry sits last only because its answer depends on none of the others, never because it matters least.
"Does any data cross a border?" is necessary and not sufficient
Serving a feature locally dissolves the transfer question and leaves the market-entry question completely untouched, so a four-check gate returns "ship as built" on a deployment that is not launchable. China administers filing duties for algorithmic recommendation and deep synthesis services and a security assessment plus filing for generative services with public opinion properties or social mobilization capacity, all independent of any transfer; Korea's AI Basic Act can require a foreign provider to appoint a domestic representative. Ask the second question at every border: does this market require an authorization, filing, registration, or representative before the feature may be offered here.
Recommend, do not just describe
An expert memo assigns a call, names the conditions with owners and dates, and recommends a resolution to any exclude-or-modify trade-off, leaving the cost/market choice to the business but not abdicating the legal judgment. A list of options without a recommendation stops one step short of the decision.
You run the structure; you route the hard parts to counsel
The professional's value is not knowing every jurisdiction's law but running the decision structure well enough to spot exposures, frame the questions, and know exactly where a qualified local lawyer must be brought in. The memo makes legal review targeted instead of open-ended.
The memo is the artifact
The output is not the knowledge that the world is complicated; it is a one-page, per-destination, cited decision with the highest exposure flagged, paired with the United States exposure map, and lodged in the accountability dossier the board audits.
Listen to it
The same lesson, talked through by two hosts as episode 46 of the podcast.
Real cases
These examples show the cross-border decision playing out on real features, with the reaching law and the shipping outcome named in each.
Example 1: Brazil halts Meta's AI training, then sets the terms (ANPD, 2024). This is your anchor. Meta shipped one privacy-policy change worldwide allowing training on public posts. On 2 July 2024 the ANPD issued a preventive measure suspending the processing of Brazilians' data for AI training, with a daily fine of 50,000 reais, finding an "imminent risk" to fundamental rights and rejecting Meta's legitimate-interests basis as inadequately safeguarded and disclosed (Future of Privacy Forum, 2024; The Register, 2024). On 30 August 2024 the ANPD lifted the suspension after Meta submitted a compliance plan: clearer notice, an opt-out simplified from eight steps to a far easier, directly linked form, exclusion of under-eighteens from training data, and pseudonymization during pre-training (ANPD, 30 August 2024). The whole arc is the four calls in miniature: Brazil went from "ship" to "exclude by force" to "ship with modifications" in two months. A company that had made a cross-border decision in advance would have shipped the Brazilian version with those safeguards from the start.
Example 2: The same feature paused in Europe on a different trigger (2024). In the same period, Meta paused plans to train its AI on European users' public posts after pressure from the Irish Data Protection Commission and complaints filed by the advocacy group noyb, again over the legal basis for the processing (TechCrunch, 2024). Two jurisdictions, two regulators, two separate pressure points, one feature. The cross-border decision is exactly the discipline of anticipating that the European Union and Brazil would each reach the feature on their own terms rather than treating "we launched it" as one global act. The detail worth carrying: the European and Brazilian objections landed on the same underlying weakness (the legal basis for training on users' data) but arrived through different doors (a regulator-plus-complaint route in Europe, a preventive measure in Brazil). A memo built in advance would have flagged the shared weak basis once and predicted that multiple jurisdictions would press on it, rather than being surprised twice.
Example 3: The EU AI Act reaching a feature by output, not marketing. Under Article 2(1)(c), a non-EU provider whose AI output is used in the Union is in scope even without targeting the European market (Regulation (EU) 2024/1689; William Fry, 2025). A practical instance: a third-country vendor whose scoring engine is consulted by an EU bank is reached because the output is used in the Union. For a shipping decision, this means a feature you never marketed in Europe can still require an EU column in your memo if its output flows there through a customer. The governance move this forces is unglamorous but essential: a business-to-business provider must instrument its customer relationships (through contract terms and questionnaires) to know where its output is actually used. "We did not know our output reached the EU" is not a defense once Article 2(1)(c) has pulled it into scope. Reach can arrive through someone else's use of your system, which is exactly why the destination list is drawn from output as well as users.
Example 4: China's transfer routes as an operate-gate condition (2024). A company moving Chinese users' data abroad to train a model must clear one of the PIPL's cross-border routes, a CAC security assessment, CAC certification, or a filed standard contract, with the March 2024 provisions (the Provisions on Promoting and Regulating Cross-Border Data Flows) easing thresholds for lower data volumes and exempting some small-volume transfers entirely (Clifford Chance, 2024). This is a concrete "ship with modifications" condition: the feature can operate, but only once the transfer mechanism is in place, and if the volumes are high, the security assessment can be a months-long gate that determines the launch date. The example also shows why the transfer check must precede the launch commitment: a team that promised a Q3 launch and only then discovered a security assessment was required would have to choose between slipping the date and shipping unlawfully, a choice a memo built in advance removes.
Example 5: Data localization forcing an architecture change. Where a destination requires certain personal data to remain within its borders, an AI feature designed to centralize training data in one global data center cannot operate as built. The defensible outcome is either local processing (a regional model or a local data store) or exclusion of the jurisdiction. This is the check that turns a paperwork modification into an engineering decision, and it belongs in the memo as a condition, not a footnote.
Example 6: The content-labeling divergence inside one product. China's measures effective 1 September 2025 require AI-generated content to carry explicit and implicit labels. (see Topic 6.4) A generative feature that ships without labels is a "ship as built" everywhere those labels are not required and a "ship with modifications" (add the label) in China. The same output, one modification, drawn by the destination's rule. The memo captures this as a per-jurisdiction condition, not a global product decision.
Example 7: The low-friction destination that is easy to over-lawyer. India's DPDP Act, 2023 permits cross-border transfer by default under a negative-list model, and as of mid-2026 no restricted-country list has been notified (DPDP Act 2023, Section 16; Mondaq, 2026). A team that assumed every jurisdiction is as restrictive as the European Union might waste months building a transfer mechanism India does not require. The lesson runs the other way from the Meta case: the cross-border decision is not only about finding the walls, it is about correctly identifying the open doors so you do not over-comply and delay a lawful launch. The defensible India row is often "ship as built" on transfer, with the caveat to check any sector-specific localization (such as payment data) that applies to the feature.
Example 8: Hard localization forcing an architecture choice. Russia's Federal Law No. 152-FZ requires Russian citizens' personal data to be stored in databases located in Russia, with criminal penalties for serious violations since late 2024 (Federal Law No. 152-FZ; Securiti, 2026). A feature that centralizes all training data abroad cannot meet this by any transfer instrument, because the data may not leave at all. The realistic calls collapse to two: build in-country processing so the data stays local, or exclude the jurisdiction. This is the example that shows a shipping decision reaching into engineering: localization can turn a legal call into a product-architecture decision, which is precisely why the memo must surface it early rather than discovering it at launch.
Example 9: Adequacy as the open door. The European Union and Japan recognize each other's data protection as adequate (mutual adequacy, 23 January 2019), so personal data flows between them without an added transfer mechanism (European Commission Implementing Decision 2019/419). For a feature operating between two mutually adequate jurisdictions, the transfer check is already satisfied, so a row that might have been "ship with modifications" (stand up standard contractual clauses) becomes "ship as built" on the transfer axis. The example completes the picture from Example 8: borders are not all walls; some are effectively open, and a good memo credits the open ones so the organization does not manufacture friction that the law does not require.
Example 10: One feature, one summer, three answers in one country. The Meta arc bears repeating as its own lesson in volatility: in June 2024 the AI-training feature shipped into Brazil; on 2 July 2024 it was suspended with a daily fine; on 30 August 2024 it was permitted again on conditions (Future of Privacy Forum, 2024). One product, one jurisdiction, three different lawful answers within roughly ten weeks. The example is why the fourth expert question ("what would change the answer?") and the review trigger are not optional flourishes but the core of a defensible decision: a memo without them would have been correct in June and dangerously wrong by July.
Example 11: The local deployment that passes every data check and still cannot launch. A company decides to serve its generative feature entirely inside China: infrastructure in China, training data collected and kept in China, no personal information leaving the country. On a transfer-centered analysis every cell is green, because the transfer question was dissolved rather than answered. What remains is a separate regime the transfer analysis never looked at. China's Provisions on the Management of Algorithmic Recommendations in Internet Information Services (in force 1 March 2022) impose a filing duty on providers of algorithmic recommendation services with public opinion properties or the capacity for social mobilization, and the Interim Measures for the Management of Generative AI Services (in force 15 August 2023) require providers of generative services with those attributes to carry out a security assessment as well as complete algorithm filing (Interim Measures, Article 17). Deep synthesis services carry their own filing duty, separately for the service provider and for the technical supplier behind it. The routes and their timing differ by service type, and the row a professional writes is not "cleared, no transfer" but "market-entry duties apply independently of transfer; confirm the applicable route with local counsel and treat it as a gating workstream with an owner and a date." This is the example that shows why the operate gate needs a fifth check: the four data checks are individually correct and collectively produce the wrong shipping call.
Example 12: The market-entry condition that is not about the product at all (Korea). South Korea's AI Basic Act, in effect since 22 January 2026, requires a foreign provider with no physical establishment in Korea to appoint a domestic representative once it crosses the revenue or Korean user thresholds set in the Enforcement Decree, which was itself revised with effect from 21 July 2026. Nothing about the feature changes to trigger this; what changes is how big you get in that market. The same Act also requires advance notice that a service runs on AI and labeling of generative output, and defines a high impact category with explanation, user protection, and human oversight duties for uses in areas such as healthcare, energy, and public services. Two lessons for the memo. First, a market-entry condition can attach to the provider rather than to the data or the output, so it is invisible to a checklist built around either. Second, a growth threshold is a review trigger: a row that is correct at launch can become non-compliant purely because the product succeeded, which is a trigger type most memos never think to write down.
Where people go wrong
- "It is legal at home, so we can ship it everywhere." The home-market fallacy, and the single most expensive belief behind a global launch. Legality at home tells you nothing about a destination's reach or requirements. Meta shipped one AI-training policy worldwide; Brazil suspended it for the same conduct that went unchallenged elsewhere. Every destination gets its own reach and operate-gate analysis; never extrapolate from home.
- "We have no office there, so their law cannot reach us." The office fallacy. The GDPR (Article 3), the EU AI Act (Article 2(1)(c)), Brazil's LGPD (Article 3), and China's PIPL (Article 3) are all extraterritorial. The ANPD reached a United States company for processing Brazilians' data. Reach is decided by where your users, their data, and your output are, not by where you have a building.
- "If the feature is lawful, the shipping decision is just yes." Reach is only the first gate. A reaching law may still let you ship, but only on conditions: a valid legal basis, a transfer mechanism, localization, disclosures. The decision is which of four calls (ship as built, ship with modifications, exclude, delay) applies, with the conditions named, not a bare yes or no.
- "Excluding a country means we failed." Exclusion (geofencing or feature-gating a jurisdiction) is a legitimate, often correct call. The failure is excluding by accident, not realizing you were reaching a jurisdiction, rather than by decision. A deliberate, cited exclusion is a governance success; an unnoticed one is the exposure.
- "Training on public data is fine because it is public." The Meta case turns exactly on this being false. The ANPD found that using "publicly available" posts to train AI still required a valid legal basis and adequate notice under the LGPD, and that legitimate interests did not suffice as deployed. Public visibility is not a legal basis for training; the destination's data-protection law still governs.
- "One legal basis works in every market." The legal basis you rely on at home (often legitimate interests) may fail at a destination that reads it more strictly or demands consent. Meta's legitimate-interests basis drew suspension in Brazil and a pause in the European Union. The operate gate may require a different basis per destination, and the memo must name it per row.
- "Once we decide, we are done." A cross-border decision decays. Regulators act (the ANPD moved in a single summer), adequacy decisions get challenged, transfer mechanisms get invalidated, laws change. The memo is a living commitment with review triggers and dates, not a permanent clearance. A stale shipping decision is how an organization becomes the next headline.
- "Cross-border data transfer is a paperwork step we can do after launch." Under the PIPL a high-volume transfer can require a CAC security assessment that takes months; under the GDPR a transfer needs a lawful mechanism before the data moves. The transfer mechanism can determine the launch date or force a local-model architecture. It is a gating condition, not an afterthought.
- "If a transfer mechanism exists, we can always move the data." A transfer mechanism authorizes a move the law permits under conditions; it cannot authorize a move the law forbids. Where hard data localization applies (as under Russia's 152-FZ for Russian citizens' data), the data may not leave at all, so no standard contract or assessment helps. Check localization before relying on a transfer route; localization overrides it, and the realistic calls become local processing or exclusion.
- "A strict-looking jurisdiction means we should over-comply to be safe." Over-compliance has a real cost: it can delay a lawful launch and burn engineering on requirements a destination does not impose. India permits transfer by default under its negative-list model, so building an elaborate transfer mechanism there may be wasted effort. The decision is about finding the open doors as much as the walls; mark a destination "ship as built" when the analysis supports it, rather than defaulting to the strictest posture everywhere.
- "Once we have an adequacy decision or a signed transfer mechanism, that leg of the memo is settled for good." Adequacy decisions and transfer mechanisms are themselves reviewable, not permanent clearances. The European Court of Justice struck down the original EU-US Privacy Shield in 2020, and its successor, the EU-US Data Privacy Framework, faces an active legal challenge as of mid-2026. A standard contractual clause signed years ago can also be superseded by an updated version. Treat every adequacy decision and every signed transfer mechanism as its own row with its own review trigger, not as a fact you filed once.
- "Building to the strictest country's rules makes us compliant everywhere." Strictest-common is one valid resolution, but only when requirements stack. Jurisdictions differ in kind, not only in degree: a hard-localization rule cannot be met by a strict global product that still centralizes data abroad, and a content-labeling mandate is a different axis from a consent requirement. Where requirements genuinely collide, the resolutions are per-jurisdiction versions or geofencing, and the memo must name which one it chose and why.
- "No AI-specific law in a country means the operate gate is empty there." The United Kingdom has no comprehensive AI statute, but a data-hungry feature still faces the UK data-protection regime and sector regulators; the operate gate is lighter, not absent. Just as "no federal AI law" did not mean "no law reaches AI" in the United States mosaic, "no AI statute" abroad does not mean "ship as built" by default. The data-protection basis and transparency duties still govern the training.
- "We can run the operate-gate checks in any order." Order matters. Design a transfer for data you have no basis to process and you have solved the wrong problem; arrange a transfer mechanism for data a localization rule forbids from leaving and you have bought an instrument that authorizes nothing. Run the checks basis first, then localization, then transfer, then use and disclosure, so each answer is meaningful before you spend effort on the next.
- "No data crosses the border, so the destination is clear." The most dangerous version of a correct sentence in this whole topic. Serving a feature locally does dissolve the transfer question, and it leaves the market-entry question entirely untouched. China imposes filing duties on algorithmic recommendation and deep synthesis services and a security assessment plus filing on generative services with public opinion properties or social mobilization capacity, none of which depends on data crossing a border; Korea's AI Basic Act can require a foreign provider to appoint a domestic representative. A four-check operate gate returns "ship as built" on exactly this deployment, which is why the fifth check exists. Ask both questions at every border: does data cross, and does this market require an authorization, filing, registration, or representative before the feature may be offered here.
- "A local build is the safe way to enter a strict market." Building in-country is the right answer to localization and to a slow transfer mechanism, and it answers neither of the questions that market entry asks. Localizing the architecture can even make the error harder to catch, because it retires the one check the team was worried about and leaves everyone feeling cleared. Localization and market entry are different gates with different owners and different clocks; satisfying one is not evidence about the other.
- "Listing the options is the same as deciding." A memo that lays out ship-with-modifications versus exclude for a destination but recommends neither has done the analysis and skipped the decision. The topic is named "the cross-border decision" for a reason: each row must carry one call, and any trade-off must carry a recommendation with its reason, leaving only the cost/market choice to the business.
Questions people ask
- What is cross-border shipping decision?
- A written, cited determination of where a specific AI feature may lawfully ship, and on what conditions, across every jurisdiction it reaches. It states, per destination, the reach basis, the operative law, one of four shipping calls, the conditions, and a review trigger. It is the international counterpart to the domestic exposure map and the payoff artifact of Module 6.
- What is reach gate?
- The first question in the decision: does a destination's law apply to the feature at all, decided by whether the feature targets or monitors people there or has its output used there. Reach is drawn by the geography of users and output, not by the company's office location.
- What is operate gate?
- The second question: given that a law reaches the feature, may the feature lawfully run there, decided by the legal basis for the data, the cross-border transfer mechanism, any data-localization requirement, the use restrictions and disclosures the destination imposes, and any market-entry authorization the destination requires before the feature may be offered there at all.
- What is market-entry authorization?
- The fifth operate-gate check: whether a destination requires a filing, a registration, a regulator's assessment, a licence, or the appointment of a local representative before a feature may lawfully be offered to people there. It is independent of the data-transfer check, so a feature served entirely inside a market moves no data across a border, passes every data check, and can still be blocked. The decision rule is that "does any data cross a border?" is necessary and not sufficient, and a second question must be asked at every destination.
- What is algorithm filing (China)?
- The registration of an algorithmic service with the Cyberspace Administration of China through the internet information service algorithm filing system. Under the Provisions on the Management of Algorithmic Recommendations in Internet Information Services (in force 1 March 2022), providers of algorithmic recommendation services with public opinion properties or the capacity for social mobilization must file specified information including an algorithm self assessment report, stated at within ten working days of providing services. The deep synthesis provisions extend filing to deep synthesis services and require the service provider and the technical supplier to file separately. It is a market-entry duty, entirely separate from the PIPL cross-border transfer routes administered by the same regulator.
Keep going
This lesson builds Governed AI program and portfolio delivery, and that page shows the roles that hire for it. Every Certified AI Governance Professional (CAIGP) lesson.
Watch the lesson and prove it
Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.
Watch the lesson and prove it →