Claude Code Feedback Prompt Bypasses Training Opt-Out
Key insights
- Submitting feedback via Claude Code's prompt can enable training data use even for developers who globally opted out of training.
- Recent visual and placement changes to the feedback prompt make it more prominent, increasing the likelihood of accidental engagement.
- Anthropic has not publicly clarified whether the feedback consent pathway overrides global training opt-out settings.
Why this matters
Developers who rely on global opt-out settings to protect client data from model training now face an undocumented secondary consent pathway that can void those protections with a single click. The ambiguity creates concrete compliance risk for teams building on Claude Code under contracts that prohibit third-party training on session data. If Anthropic's terms allow feedback submission to supersede global data controls, every enterprise deployment using Claude Code needs to audit its consent posture before the next billing cycle.
Summary
Claude Code's optional 'How is Claude doing?' feedback prompt has a consent problem developers are only now fully mapping. Users on r/ClaudeAI have documented recent visual and placement changes to the prompt, reigniting scrutiny of a buried terms clause: submitting feedback through this interface can authorize session data for model training, even if the developer has globally opted out of training data collection.
The mechanism is a consent layering issue. Global opt-out settings do not appear to cover feedback-triggered data submission, creating a secondary channel that operates independently of a developer's stated preferences.
Essentially: (Anthropic, Claude Code developers) are at odds over where opt-out consent boundaries actually apply.
- The feedback prompt received updated visual treatment and repositioning, making it more prominent and raising accidental interaction likelihood.
- Developers who engage with the prompt may be contributing session data to model training despite believing their global settings protect them.
- The r/ClaudeAI community is actively warning members to skip the prompt entirely until Anthropic clarifies the scope.
Anthropics silence on the claim leaves developers managing the risk through avoidance rather than informed consent.
Potential risks and opportunities
Risks
- Enterprise teams using Claude Code under data-protection contracts could face breach-of-contract claims from clients if session data reached Anthropic's training pipeline through the feedback channel without explicit per-interaction consent
- Anthropic faces GDPR and CCPA enforcement scrutiny if EU or California-based developers can demonstrate session data was collected for training without clear layered consent disclosure at the point of feedback submission
- Developer trust erosion could accelerate Claude Code churn toward competitors (GitHub Copilot, Cursor, Codeium) if Anthropic does not publish a clear consent architecture within 30 to 60 days
Opportunities
- Competing AI coding tools (Cursor, GitHub Copilot, Codeium) can differentiate on explicit, single-toggle training consent with no secondary override pathways, targeting enterprise procurement teams now scrutinizing Claude Code
- Privacy-focused enterprise AI deployment consultancies gain a clear pitch: auditing AI coding tool consent configurations for teams operating under GDPR, HIPAA, or client data-protection obligations
- Anthropic can recapture developer trust by publishing a public consent architecture document and shipping a unified training opt-out that covers all data channels including feedback, converting a reputational liability into a transparency differentiator
What we don't know yet
- Whether Anthropic's terms of service explicitly state that feedback submission overrides global training opt-out, or whether this is a legal interpretation gap that Anthropic disputes
- How many Claude Code sessions have reached Anthropic's training pipeline via the feedback channel from developers who believed their global opt-out was in effect
- Whether enterprise, Teams, or API-tier accounts face the same feedback consent override as individual developers, or whether different contract terms apply
Originally reported by reddit.com
Read the original article →Original headline: r/ClaudeAI: Claude Code's 'How Is Claude Doing?' Feedback Prompt Has Evolved — Developers Flag Training-Data Consent Trap