Field noteOct 23, 20262 min read1 source

Zhipu's ZCode deletes data and announces compensation after data upload controversy

In one minute

Zhipu AI says it has completed remediation for a data-upload incident involving its ZCode AI coding tool.

What changed: Same event as Zhipu запустила для ZCode программу по восстановлению доверия пользователей.

TechNode reports that the company deleted all data objects in the affected Alibaba Cloud OSS bucket and deleted the bucket itself. Zhipu said the deletion was verified by the China Academy of Information and Communications Technology and NSFOCUS.

The controversy surfaced on September 18 after a developer found an encrypted file of about 313 MB in ZCode's local data directory. Reverse engineering reportedly indicated that it packaged an entire workspace, including source code, Git history, LFS caches, and global development configuration. In earlier versions, the upload feature was enabled by default and did not offer a clear disable option, according to the report.

ZCode 3.14.0, released September 19, removed the Repo Wiki entry and relevant repository-snapshot generation and upload paths. Zhipu later open-sourced ZCode; the Apache-2.0 codebase is now at version 3.14.3. The company says future uploads require user initiation, and says affected data was neither retained nor used for model training.

Paid users are to receive four weekly and four five-hour quota-reset cards, each valid for one month. Between September 28 and October 7, ZCode planned 100,000 free packages of 100 million tokens. The report does not independently establish what data left individual devices or independently verify deletion.

Evidence / sources

  1. 1technode.com/2026/09/29/zhipus-zcode-deletes-data-and-announces-compensation-after-data-upload-controversy
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAgent SecurityExplore the agent-security topic hub.
  2. 02topicSandboxExplore the sandbox topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract