Aureus Sovereign › Briefings

Sending material to a mainland service: what changes

Two systems, one country, and a border that matters for data in ways it does not for most other things. What is actually different, separated from what is merely assumed.

Published 5 October 2026

The short answer. Capability is no longer the distinguishing question; several mainland models are competitive and some are open-weight, which creates options a Hong Kong organisation may find attractive. What changes is that the material leaves Hong Kong's legal system for a different one, and that a set of questions which have settled answers for an established Western vendor have different answers, or no published answer, for a mainland one. The difference is jurisdictional and contractual rather than technical.

This briefing is deliberately narrow. It is not about geopolitics, and it takes no view on which models are better. It is about what a Hong Kong organisation should establish before submitting its material.

1. Hong Kong and the mainland are separate data jurisdictions

This is the point that surprises people, and everything else follows from it. Under one country, two systems, Hong Kong and the mainland operate distinct legal regimes, and data protection is one of the areas where they are genuinely distinct. Hong Kong has the Personal Data (Privacy) Ordinance. The mainland has its own framework, including a personal information protection law and separate rules on cross-border transfer.

A transfer from Hong Kong to Shenzhen is a cross-border transfer for these purposes. It is not domestic simply because it does not leave the country, and treating it as domestic is the most common analytical error in this area.

What follows is that the question is not whether the organisation trusts the vendor. It is which law governs the material once it arrives, and that is a question for advisers rather than for the procurement form.

2. There are three quite different things people mean by "a mainland service"

They carry different exposures and are routinely spoken of as though they were one thing.

The third row deserves attention, because it is frequently overlooked and it inverts the analysis. Several capable models developed in the mainland are published as open weights, meaning the model can be downloaded and run on the organisation's own machines or its own cloud tenancy in Hong Kong. Material submitted to a model running on infrastructure the organisation controls does not cross a border at all, and the cross-border questions above simply do not arise. What arises instead is a licensing question, an infrastructure cost, and the need for someone to keep it running — real costs, but different ones.

3. What is genuinely different about a hosted mainland service

Four things, stated plainly.

• The governing law and the forum. The contract will specify both. They will not be Hong Kong's, and that is a commercial term to negotiate or accept rather than a surprise to discover later.
• The circumstances of lawful access. Every jurisdiction has them, including the ones Western vendors operate under. The relevant question is whether the organisation understands them for this jurisdiction as well as it does for the others it already accepts.
• Content moderation applies to inputs and outputs. Services offered in the mainland operate under content rules, which can mean a submission is refused, filtered or logged for reasons unrelated to its confidentiality. For ordinary commercial material this is usually a nuisance rather than a risk, but it is a behaviour to expect rather than to be startled by.
• Documentation and negotiating posture may differ. The published terms of the largest Western vendors have been examined by a great many legal departments and have converged. A newer or smaller vendor's terms have not necessarily had that scrutiny, which cuts both ways: more room to negotiate, and more that has to be read rather than recognised.

4. What is usually assumed and is not distinctive

Three assumptions recur and none of them is a difference.

That the models are less capable. On published benchmarks several are competitive with the best available, and on Chinese-language work some are ahead. Capability is a poor reason to choose between them in either direction.

That data goes somewhere with a Western vendor and nowhere with a mainland one, or the reverse. Material submitted to any hosted service is processed on somebody else's infrastructure under somebody else's law. The questions are identical; only the answers differ.

That a Hong Kong organisation is on home ground with a mainland vendor. It is not, for data purposes, for the reason set out in section one.

5. The case where this is straightforwardly sensible

An organisation with mainland operations, mainland customers and a substantial volume of Chinese-language work has reasons to use a mainland service that have nothing to do with anything above. It may already transfer data across that border under existing arrangements, the model may simply be better at the language, and the vendor may be easier to deal with commercially.

Where that applies, the position is unremarkable: the transfer arrangements already exist, the AI service is one more destination under them, and the questions in section three are answered once during procurement.

6. What to settle before anything is submitted

• Whether the intended material is personal data, and if so whether the existing cross-border arrangements cover this transfer.
• Which of the three arrangements in section two is actually under consideration — the answer is often not the one assumed.
• What the contract says about processing location, retention, model training and sub-processors, read rather than summarised by the vendor.
• Whether the open-weight route removes the question entirely for the intended use, and what it would cost to take it.
• Whether the organisation's own privacy notices and client engagement terms are consistent with the transfer.

None of that is exotic. It is the same due diligence any new processor receives, applied to a destination whose answers have not yet become familiar.

This briefing sets out questions, not requirements. What the Personal Data (Privacy) Ordinance, a listing obligation or a contractual undertaking requires of a particular organisation is a matter for that organisation's own advisers.