Using ISMS Copilot from China

Using ISMS Copilot from mainland China

ISMS Copilot serves users in China and users who travel there. We do not block mainland connections, we do not degrade them on purpose, and we never ban an account for the country you are in or the country you travel to.

What works without special setup

• The site and the app. chat.ismscopilot.com and docs.ismscopilot.com are public sites; nothing on our side blocks a mainland IP.
• Email and password sign-in. Create your account and sign in with an email address and a password. This path needs no third-party identity provider.
• The Chinese interface. ISMS Copilot ships a full Chinese (zh) interface: switch the language in Settings, or set your browser to zh-CN. Answers follow: ask in Chinese and the assistant answers in Chinese.
• Chinese framework questions. The assistant covers the frameworks organisations in China work with: the Cybersecurity Law (revised consolidated text in force 1 January 2026), the Data Security Law, the Personal Information Protection Law (PIPL), MLPS 2.0 (GB/T 22239-2019), and the CAC cross-border data routes. See the China framework pages under Chat, Frameworks: China PIPL and China MLPS 2.0.

The single-sign-on caveat

The Google and Microsoft sign-in buttons depend on those providers' networks. From mainland China they may not load. Use the email-and-password path instead; you can set up two-step verification from an authenticator app afterwards.

What we do not promise

We do not promise guaranteed network reachability of our sites from inside mainland China. No honest foreign service can promise that: network paths differ by carrier, city and moment, and we have no mainland test point. If a page loads slowly or fails, that may be the network path; it is not evidence of an intentional block from us. (If you can, check our status page or contact support to rule out an outage on our side.) We also do not advise, assist, or discuss circumventing network controls, and the assistant will not do so either.

Where your data lives

Database and document storage are in the EU (Frankfurt). Sessions we detect as originating from mainland China are pinned to model providers whose terms welcome China users, on hosts outside mainland China, with EU-hosted failover. Detection is server-side and best-effort: it reads the client IP our edge reports and matches it against China-allocated network ranges; it is not an identity check and not a block. The data processing agreement documents the no-mainland-endpoint data path; see the Trust Center.

If something does not work

Check troubleshooting first, then contact support from the sidebar help button. Tell us the city, carrier, and what you saw (an error, a timeout, a blank page): it helps us separate our problems from network-path problems.