Back to China Market Playbook
Curated briefingApproval and Storefront Availability

What Apple Actually Requires for Mainland China Availability

Apple’s current App Store Connect fields show exactly which China-mainland records an indie mobile team must keep separate.

The Thesis

Apple asks for ICP information, a game approval number, supporting documents, and matching entity data in separate places. Build your launch sheet the same way.

Key takeaways

  1. Plan China-mainland availability as a platform evidence workflow rather than a territory checkbox.
  2. Keep ICP filing information, a game approval number, business documents, and operator authorization distinct and consistent.
  3. Apple’s documentation explains App Store Connect fields; it does not replace the underlying official rules or route-specific advice.
On this page
  1. Start with the records Apple actually asks for
  2. Give names and titles one source of truth
  3. Apple’s form leaves most of the operation outside the frame
  4. Verify the live form before you set a date

Open Apple’s App Store Connect reference and “mainland China” stops looking like a single availability checkbox. Apple asks for named records and documents. Localization, App Review, an ICP filing number, and a game approval number each solve a different problem.

This article summarizes Apple’s platform documentation in our own words. It does not determine whether a particular app is in scope, satisfy Chinese law, or guarantee availability.

Start with the records Apple actually asks for

In the “Availability in China mainland” section of its App information reference, Apple says Chinese law requires additional documentation for some apps. It explains that some apps need a valid ICP Filing Number and that the number and metadata should match information filed with MIIT. It separately states that games must secure an approval number from the NPPA.

Apple also describes supporting documents for verification. For a game approval number, its page refers to the ISBN issuing letter or approval reply, a current business license, and, where applicable, authorization from the matching operator. The page covers other regulated app categories too, but a game studio should resist turning that broader list into a generic upload pile.

Keep one canonical studio record for every field that must match across systems. A punctuation change in the company name, a different operator, or an inconsistent translated title can block verification late in the release.

Give names and titles one source of truth

Create an “entity and title record” with the exact names used in contracts, official documents, platform accounts, and localized metadata. Assign one owner to approve changes. Then build a document matrix with these columns:

  • App Store Connect field;
  • underlying document or official record;
  • named entity and title on that record;
  • party that controls it;
  • expiration or refresh concern, if any;
  • verification status;
  • current platform feedback;
  • blocker and escalation contact.

Check this before the build is ready. Ask the proposed publishing partner to walk through the current title’s App Store Connect workflow and name the party that can see and change each field. You want to find mismatched developer accounts, operator authorizations, approval documents, and store records while there is still time to fix them.

Keep the mobile route separate from an international PC release. A Simplified Chinese Steam page does not produce Apple eligibility, and Apple documentation does not define what Steam visibility means.

Apple’s form leaves most of the operation outside the frame

Apple’s reference cannot tell you whether the game will receive NPPA approval, whether another filing applies, or whether an uploaded document will pass verification. MIIT and NPPA materials still govern their respective processes. Mainland Android channels, partner contracts, SDKs, payments, identity, minor protection, data, servers, support, and marketing all sit outside this page.

The page can change. A screenshot of an old form is not a durable requirements document. Nor should a platform field be treated as legal interpretation for an edge case.

Verify the live form before you set a date

Open Apple’s App information reference, find the current “Availability in China mainland” section, and follow its official links. Compare the live wording with the documents your partner proposes to use. Keep every entity, title, approval, filing, authorization, and platform record consistent enough for a reviewer to verify it without guessing.

Search the site

Search resources and field guides

    Privacy settings

    Your language choice, open home-page sections, favorites, comparisons, and recent views stay in this browser. Nothing is uploaded.