← Back to the blog

STORY 06 / Data use & retention

Training permission and retention are different questions.

Claude’s consumer policy illustrates why buyers should separate conversation history, model-improvement permission, deletion, and exceptions.

Published consumer policyConfigurable permission; exceptions applyConsumer retention documentation dated July 1, 2026

The cited consumer article covers Free, Pro, and Max, not a universal rule for commercial products or API agreements. Retention is not the same as permission to train.

What the policy says

Anthropic’s consumer retention documentation says model-improvement permission can allow relevant conversations and coding sessions to remain in de-identified training pipelines for up to five years. It also describes a backend deletion period of up to 30 days after deletion, subject to exceptions.

Those are different clocks for different purposes. The article excludes Incognito conversations from model improvement and says disabling improvement does not undo training already underway or completed. Feedback, safety, and legal exceptions also matter.

Ask separate questions

A business should not collapse its data review into a single yes-or-no privacy question. Ask which information is stored, which uses are allowed, when deletion begins, what exceptions exist, and which agreement covers the actual service.

  • Distinguish consumer settings from commercial contractual commitments.
  • Confirm deletion timing and exceptions rather than assuming automatic expiration.
  • Minimize the information submitted until the required terms are established.

A PRACTICAL THADDEUS WORKFLOW

Plan the information path before the upload.

Use a Thaddeus assignment to prepare a requirements checklist from public policies and approved information. Local project records help preserve the checklist and decisions, but the processing terms of each service still need review.

Try this assignment

Using these public service policies, separate retention, training permission, deletion, and exceptions into a comparison table. Cite each relevant passage. Mark anything the sources do not establish. Do not upload confidential records.

Local files do not establish no-training or zero-retention terms. Thaddeus operations may involve external processing; any required commitments must be supported by the applicable agreement.

Sources & further reading

Educational information, not a security audit, professional advice, or guarantee. The assignment is an example to evaluate, not a completed demonstration. Historical incidents and product capabilities do not establish comparative safety. Confirm current policies and agreements for your intended workflow.