The Dim Sum Guide: localizing security advice for Chinese-speaking readers

Digital-security advice that is translated into a new language but still lists the same Western apps often fails the reader who lives in China or inside a Chinese-language toolchain. The default messenger, app store, payment method and legal setting are not the ones most English guides assume. Localization means rewriting the advice around the tools and risks that reader actually has, not just turning the sentences into another language.

This page is not legal advice about China and not a covert operations guide. The point is that copied advice can be useless or even misleading. The principles of a device lock and of updates in the Android and iPhone and iPad guides still apply; what changes is the store path, the everyday app and the social meaning of some settings.

Chinese-speaking readers are not one group

Someone living in mainland China, someone in the diaspora and someone who travels between countries do not share the same threats or the same tools. A good guide says so and offers at least two paths, not a single script.

1. For a reader who lives on the mainland, start from the tools and stores that are actually on the device, not from a store that may not open at all.
2. For a reader in the diaspora, ask whether they still talk with family on the same domestic messenger or mostly on tools local to the host country; they often have both.
3. For someone who travels, look at border changes in digital security while traveling and, if detention along the way is a realistic risk, line that up with planning for detention risk.
4. Do not summarise these three audiences in one sentence that begins “Chinese users should…”

Start from the tool that is opened every day

Many guides talk about Gmail, WhatsApp, Google Play and iCloud. For a reader who mostly uses WeChat, domestic stores and real-name requirements, those examples are either unavailable or they carry a different risk.

1. Ask what the audience actually uses for messaging, payment and news.
2. Ask where installation is possible for them: the manufacturer’s store, Apple’s official store, or another source they already know.
3. Ask what sharing a phone number, a national ID or a real name means inside that service.
4. Do not treat WeChat as only a messenger; for many people, payments, official accounts and a large part of daily life sit there. Advice that says “just delete it and go somewhere else,” without a workable alternative path, is usually not followed.

Write stores and updates for the life of that device

A screen lock and security patches are still the priority. But telling someone to “update from Google Play” does not help if they do not have that store.

1. Write the update path with the real menu names in that language and put a review date on the page; interfaces change quickly.
2. For Android, base the text on the default store of that manufacturer or that region, not on the store the writer happens to use.
3. For iPhone, say which app appears in the store of that regional account and which does not; do not guess.
4. Do not take an installer from an unknown message or a third-party site just because it is advertised as an “international version.”

Do not hide legal and social risk

Using some access tools, or some ways of separating identities, may carry a different legal or social meaning in one jurisdiction than in another. Do not swap in the writer’s country, and do not turn the note into a circumvention recipe.

1. If you talk about an access path, treat it as access education and point to choosing circumvention routes, not to a hidden configuration for a particular network.
2. Do not say “just install this tool and there is nothing left to worry about.”
3. Explain the consequence of a real name, a registered SIM and an identity-tied account without offering an unlawful workaround.
4. If you yourself do not live in that environment, do not issue a hard rule without talking to someone who does.

Write at least two paths

A single script usually helps one audience and misleads the rest. It is better to separate a path “if you are on the mainland” from a path “if you live outside it or you travel.”

1. In each path, say which tool is assumed and which assumption does not hold.
2. If the reader lives both lives at once — work in one country and family in another, for example — say which accounts should not be mixed on the same device.
3. Talk about separating identities in language that matches the social pressure of that environment, not only in the terms used by English-language guides.

Test the translation with people who live there

Fluent Persian or English that has merely swapped app names is still not localization. Someone who sees those menus every day should walk the path on their own device.

1. Have at least one person from that context read the text and walk through the settings on their own device.
2. Write menu names in the language of that interface, even if the body of the guide is in another language.
3. Put a review date on the page so it is clear later when the advice needs to be refreshed.
4. If you have adapted someone else’s materials, respect that work’s licence and say what you changed. This page is not a survey of open-licence types; it is only a reminder that a translation made without looking at permission can be wrong both as a matter of rights and as a matter of care.

The same principles apply when localizing into other languages, including Persian: the examples should belong to the reader’s life, not to the writer’s default app store.

What this page does not say

This text does not publish an allowed or banned app list for China, and it does not give a specific configuration for getting around a particular network’s limits. It also does not replace a local lawyer. Its job is that a writer or a trainer, before translating a ready-made list, asks who the audience is, what tools they have, and what harm a single sentence for everyone would do.

Do not treat travel as the same as everyday life

A phone that is reasonable at home may raise new questions and new risks when it crosses a border. Apps, signed-in accounts and even the contents of the gallery take on another meaning in that moment.

1. Before a trip, see which accounts do not need to be on the device you carry.
2. Follow a strong lock and device encryption from the guide for that system.
3. Agree a contact plan with the people who are expecting you, outside that one app, if the app may be unavailable along the way or unsuitable for you.

Do not confuse written language with region

Simplified Chinese, Traditional Chinese and Persian or English written for a migrant do not share the same audience. Words, menu names and even news examples may be familiar to one reader and foreign to another.

1. Say which script and which context the text was written for.
2. Do not copy a political or news example from one region into another.
3. If the audience reads in more than one script, at least bring the key menu terms in the form they see on the device.

See payments and official accounts as separate from chat

In many readers’ lives, paying by code, following an institution’s or a business’s official account, and sending a personal message sit inside one app. Security advice that only sees “chat” is incomplete.

1. Ask whether cutting or limiting that app would close off daily life — shopping, transport, administrative contact — or not.
2. If you suggest a substitute, say which role it replaces: messaging, payments, or both.
3. Do not put payment and card details on a screen during group teaching.

Do not treat backup as the same as that app’s own sync

Making a copy of a device is covered in the backup guide. The point here is that syncing inside a cloud tied to the same identity may not be the same as “a copy you yourself can restore,” especially if the account is bound to a real name.

1. Ask the reader which files would be lost if they could not reach that account.
2. Do not leave the separate copy only on that same single phone.

Common mistakes

• A word-for-word translation of a Gmail, WhatsApp and Google Play list for a reader who cannot reach those services.
• Treating a mainland resident, a migrant and a traveller as one audience.
• Hiding a legal or social difference in order to make the text “simpler.”
• Leaving out real menu names and a review date.
• Not testing the text with someone who lives in that environment.

What to do today

1. If you are preparing teaching for a Chinese-speaking audience, rebuild the tool list with them rather than translating it.
2. Have at least one person from that context read the text and check the settings on their own device.
3. Put a review date on the page so it is clear when the advice will need to be refreshed.
4. Write at least two paths for two different contexts, not one script for everyone.
5. Do not swap in another country’s legal risk, and do not turn it into a hidden recipe.
6. If you adapted the text from another source, respect that source’s permission and write down the changes.

The name “Dim Sum” in this page’s title is a reminder of the same work: the meal should be laid out with the taste and the ingredients of that table, not as a fixed list from another kitchen that has merely been relabelled in a new language. Good security advice for a Chinese-speaking reader also starts from that person’s real life and does not hide serious differences of context for the sake of a smoother text.