If you pay for a Pro subscription, you can enable a Zero Data Retention mode where your code is processed in real-time, deleted immediately after a response is generated, and never stored or used for training.
Pro users gain access to a meaningful data protection option — Zero Data Retention — that ensures code is not stored or used for model training, but this protection is unavailable to free users and has carve-outs for specific models and features that may not be immediately obvious.
Cross-platform context
See how other platforms handle Pro User Zero Data Retention (ZDR) Option and similar clauses.
Compare across platforms →ZDR is a significant privacy protection for professional developers working with sensitive or proprietary code, but it is only available to paying Pro users and does not apply to models labelled '(no ZDR)' or features like Remote Indexing and Memories.
(1) REGULATORY FRAMEWORK: The ZDR option is directly relevant to GDPR Art. 5(1)(e) (storage limitation principle), Art. 25 (data protection by design and default), and Art. 32 (security of processing including encryption in transit). For US users, it addresses CCPA §1798.100 data minimization principles. The carve-out for 'no ZDR' models and persistent features (Remote Indexing, Memories, Recipes, etc.) creates partial compliance gaps that must be documented in any GDPR Article 30 Records of Processing Activities. (2)
Compliance intelligence locked
Regulatory citations, enforcement risk, and due diligence action items.
Watcher: regulatory citations. Professional: full compliance memo.