November 16, 2026: Apple’s App Store Connect release notes say regulatory and license information moved to the new App Compliance page. This is a page move, not a rule that every app must upload specialist evidence. Check the functions your app actually offers in mainland China: Apple requires relevant declarations for apps offered there, while filing details and security assessment materials apply only when the stated feature conditions are met.
This guide is for independent developers preparing a new iOS app for the mainland China storefront.
It also helps developers with existing apps check declarations and verification status.
Teams offering generative AI, synthetic content, or end-to-end encrypted messaging should review the material requirements closely.
Last updated November 17, 2026; verified against Apple’s current release notes and China mainland compliance guidance.
01 Start with the China mainland App Compliance declaration
Treat the page as the place to answer Apple’s compliance questions and provide requested information—not as a universal request for every possible certificate. Apple’s guidance covers declarations for apps offered in mainland China. Whether you need to provide additional AI filing information or security assessment materials depends on the functions available to users there and the requirements Apple shows for that declaration.
The change announced on November 16, 2026 was the move of regulatory and license information into a dedicated App Compliance page in App Store Connect, as stated in Apple’s release notes. Keep these separate:
- Page location: where you manage the declaration and related compliance information.
- Declaration: your response about the app and its functions.
- Filing information: details that may apply to certain AI-generated or synthetic content services.
- Assessment evidence: documents that may apply to security-assessment declarations.
- Apple verification: Apple’s review of the supplied information.
- App Review: the review process for a submitted app version.
A page migration does not, by itself, prove that your app has a new legal obligation. Apple’s page and your app’s actual feature set determine what you need to enter. Regulatory applicability must be checked against the relevant authority’s requirements and your implementation; this guide is not a legal determination.
| Your app’s China storefront situation | What to check in App Store Connect | What not to assume |
|---|---|---|
| The app is offered in mainland China and has no relevant AI or security-assessment function | Complete the applicable declarations. If the function is absent or unavailable in mainland China, select the relevant negative response where Apple provides it. | That every app needs an AI filing record or a security assessment report. |
| The app offers AI-generated or synthetic content in mainland China | Review the relevant declaration, filing information, and any third-party authorization or agreement Apple requests. | That naming a model or SDK proves the service is properly filed. |
| The app distributes generated or synthetic content, or offers end-to-end encrypted instant messaging | Check whether the security-assessment declaration applies and prepare the evidence Apple specifies. | That the presence of a feature label alone proves an assessment is required—or completed. |
| The app is already available in mainland China | Review the app’s current declaration and verification status, including any deadline Apple displays. | That an old approval or an existing listing means the new verification step is complete. |
02 Apps without the listed features still need a declaration check
If your app is offered in mainland China but does not provide the relevant AI-generated or synthetic content functions there, do not submit as though it does. Apple’s China mainland compliance guidance explains that an app without the applicable function—or with that function disabled or region-blocked in mainland China—should use the corresponding negative declaration when available.
That answer is not the same as uploading a filing certificate. It records the scope of the app’s China offering. Keep your answers consistent with the production build and storefront configuration. If your app has a feature flag, regional endpoint, or remote configuration that can turn a function on, document how that control works and who can change it.
A common error is to answer from the product roadmap rather than the build and service users can access now. Another is to assume that any machine-learning feature counts as a generative content service. Read the exact wording in App Store Connect. Describe what users can do, what content the feature produces or distributes, and whether it is available in mainland China.
A negative declaration should match the shipped service, not merely the code path you intend to keep disabled. Recheck it after changing a feature flag, backend route, or regional availability setting.
03 AI-generated content requires a function and provider review
Apple’s guidance identifies AI-generated or synthetic content scenarios such as chatbots and image, video, voice, or face transformation services. Use those examples as prompts for a feature review, not as an exhaustive legal definition. The central question is whether your app offers the relevant service in mainland China.
For an applicable service, check the declaration fields and filing information Apple requests. China’s Interim Measures for the Management of Generative AI Services provide a regulatory reference for generative AI services. The National Internet Information Office also publishes generative AI service filing information. Use authoritative records to verify details; do not infer that a particular model name, API, or supplier relationship completes a filing.
If a third party supplies the model or underlying technology, Apple may ask for authorization or a service-use agreement. Prepare the document that establishes your right to use the technology in your app. Check that it identifies the relevant parties and scope, and that it covers the service you actually distribute. A generic vendor webpage or an SDK name in your project is not a substitute for a requested agreement.
| Review point | Evidence to assemble | Decision to make before submitting |
|---|---|---|
| User-facing function | Product flow, screenshots, and a short feature description | Does the app generate, transform, or distribute relevant content in mainland China? |
| Regional availability | Release settings, feature flags, and service routing | Is the function available, disabled, or blocked for mainland China users? |
| Filing details | Applicable authoritative filing information | Does the record match the service and provider used by this app? |
| Third-party technology | Authorization or service-use agreement, if requested | Does the document cover your intended use, not just access to a general platform? |
Keep a record of what you checked and when. If you change providers, add a new generation mode, or enable a previously blocked function, revisit the declaration before the next release. The 2026 filing information notice and Apple’s current page should be checked again at submission time because the details and records you rely on can change.
04 Security assessment declarations depend on the service and status
Apple’s China mainland guidance connects security-assessment declarations with cases including the distribution of AI-generated or synthetic content and end-to-end encrypted instant messaging. Do not collapse three different questions into one: whether the function exists, whether the assessment requirement applies, and whether the assessment has been completed and accepted.
For a relevant function, follow the exact App Store Connect fields and prepare the supporting proof or report Apple requests. The Internet Information Service Security Assessment Provisions are an official reference for the assessment framework. They do not let you infer the result for a particular app from a feature name alone. Confirm applicability and status with the responsible team and the relevant authority where needed.
A feature may be technically present but not available in mainland China. Conversely, a function can be provided through a backend service even if the client app contains little visible code for it. Review the complete user journey, including APIs and third-party components. Record any regional restrictions that matter to the declaration.
The National Internet Information Office’s filing inquiry system notice is another source to consult when checking official records. A public record can help confirm information, but it does not replace Apple’s own verification state or the supporting documents requested for your submission.
05 Existing apps need a status check, not an assumption
For a new submission, complete the applicable compliance information before you hand the version into the app submission workflow. For an existing app, open its current App Compliance information and check whether Apple marks the declaration as complete, awaiting verification, or unsuccessful. Follow any deadline displayed in the current Apple guidance or in App Store Connect; do not rely on a saved screenshot or an older release note for a date that may have changed.
Apple’s China mainland compliance page describes the verification arrangements for existing apps and the consequences for mainland China availability when verification is incomplete. Check the current wording and deadline directly before acting. If verification has not cleared, identify the missing field or document, correct it, and resubmit the requested information. Do not assume that an unresolved mainland China check automatically affects availability in other storefronts.
Use this status sequence:
- Not started: identify the app’s China availability and relevant features, then complete the applicable declarations.
- Submitted or awaiting verification: preserve the submitted answers and documents; monitor the status in App Store Connect.
- Needs correction or not verified: read Apple’s specific request, fix the affected information, and submit again.
- Verified: save a record of the status and the app version or service configuration it relates to.
These are workflow states to check, not a guarantee of approval. Apple’s verification of compliance information and App Review of a software version are separate processes. A successful review of an earlier build does not prove that a later declaration is complete.
06 Use a pre-submission checklist
Complete this review before you submit or update an app offered in mainland China. Each item should have an owner and a verifiable answer.
- [ ] Confirm that the app is available, or will be available, in the mainland China storefront.
- [ ] List the user-facing functions available in that storefront, including backend-powered features.
- [ ] Check whether the app generates, transforms, or distributes AI-generated or synthetic content.
- [ ] Check whether it offers end-to-end encrypted instant messaging or another function named in Apple’s current guidance.
- [ ] If a relevant function is absent or region-blocked, verify that the production configuration enforces that restriction.
- [ ] Complete each applicable App Compliance declaration in App Store Connect.
- [ ] If AI filing information applies, verify the details against authoritative records.
- [ ] If a third party provides the technology, prepare the authorization or service-use agreement Apple requests.
- [ ] If a security assessment declaration applies, confirm the required evidence and the actual assessment status.
- [ ] For an existing app, inspect Apple’s current verification status and deadline rather than relying on an old screenshot.
- [ ] Keep a copy of submitted responses, supporting documents, and the release configuration they describe.
- [ ] If you change a provider, feature flag, regional route, or content capability, review the declarations again.
This checklist is an operational handoff, not a substitute for legal advice or an approval prediction. If a requirement is unclear, ask the responsible compliance contact or relevant authority before representing that an assessment or filing is complete.
07 Keep compliance declarations separate from the Xcode submission
App Compliance information is managed in App Store Connect. It does not require a Mac simply to open the page and complete the declaration. A Mac becomes relevant if the project needs a new build, signing, an archive, or an upload. Apple documents the separate version workflow in its steps for submitting an app for review.
When both tracks are needed, hand off a compact record: the compliance status and any outstanding request; the app version and build identifier; the code and signing changes required; and the person responsible for uploading the build. This prevents a common release mix-up: treating a successful upload as proof that compliance verification is complete, or treating a completed declaration as proof that the binary has been submitted.
If you already have a reliable Mac and the workload is steady, using it may be the simplest choice. If you only need macOS for a release build or temporary signing task, compare the time and cost of maintaining hardware with a short-term remote environment. You can review CALMVPS Mac rental plans before deciding. Remote access does not complete App Compliance declarations; it only provides a Mac environment for the build and submission work that actually needs one.
08 FAQ
Which apps need an App Compliance declaration?
Apple says apps offered in mainland China must complete the relevant declarations in App Store Connect. That does not mean every app must submit AI filing records or security assessment documents. First review your app’s actual functions and China availability, then follow the fields and material requirements Apple currently displays for the applicable declarations.
How should I answer if my app has no AI features in mainland China?
If the app does not provide the relevant AI-generated or synthetic content functions in mainland China, use the applicable negative declaration in App Store Connect. The same distinction applies if those functions are disabled or region-blocked there. Keep evidence of the release configuration and regional restrictions, and do not upload specialist AI materials just because the app uses unrelated automation or machine-learning features.
What should I prepare if my app uses a third-party large language model?
Do not treat the model’s name or a vendor’s general statement as proof that your app meets Apple’s requirements. Check whether your app provides a listed generative or synthetic content service in mainland China. If it does, confirm the applicable filing information and prepare the authorization or service-use agreement Apple requests for third-party technology. Verify the provider’s records against authoritative information.
Could a failed security assessment check affect availability outside mainland China?
Apple’s China mainland compliance guidance describes the effect in relation to availability in the mainland China store. Do not infer that an unresolved verification automatically removes the app from every other storefront. Check the app’s App Store Connect status and Apple’s current notice, then contact Apple if the displayed regional impact is unclear.
09 Finish the declaration review before the build handoff
First confirm the app’s mainland China functions, complete the applicable App Compliance declarations, and resolve any verification request. Then handle Xcode build, signing, and upload as a separate release track. If you need macOS for that work but do not want to buy and maintain a dedicated Mac, a remote Mac can be a flexible option; if your Mac is already available or you need continuous local hardware access, keep using it. If the build is the remaining blocker, review the CALMVPS remote Mac order options and choose only if they fit your release workflow.