Can public web data be used for AI training under China-facing compliance review?

Short answer: for a China-facing review, “publicly available” is not the same as “free to use for AI training.” Lawyer Lv Qingling would first separate access, acquisition, and permission for the specific model use.

The exact China-facing scope depends on the project’s processing facts and must be checked separately. Once that scope is identified, the permission review should separate technical access, the way the material was acquired, and whether it may be copied, stored, cleaned, used for training or fine-tuning, sent to a vendor, or reused in a commercial model workflow.

The first boundary is IP. Public webpages may contain text, images, audio, video, code, database structures, or other organized material. A purchase receipt or a dataset delivery file also does not prove that the vendor had the right to transfer the data for model training.

The second boundary is personal information and data security. If the dataset contains account data, contact details, voice, images, transaction records, customer service logs, location data, or combined fields that can identify a person, the project needs a separate personal-information basis and processing-purpose review.

The practical next step is one evidence-preserving table for one dataset batch: source, acquisition record, license or contract basis, data categories, intended model use, vendor access, retention or deletion path, and unresolved gaps. If a row cannot explain source rights or processing basis, treat that batch as restricted until reviewed.

This does not mean all public data is unusable in China-related AI projects. It means public access, data purchase, and AI training permission are different questions, and they should be documented before the dataset enters the training pipeline.