Skip to main content
hc
Submit
skillsSource-backedReview first Safety ✓ Privacy ✓

Claude Code Zero Data Retention Review Capability Pack Skill

Expert Claude Code zero data retention review capability pack for auditing ZDR scope on Claude for Enterprise, disabled features, model availability, analytics limits, and third-party integration gaps before rollout.

by kiannidev·added 2026-06-13·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • This skill summarizes official ZDR scope; it must not claim ZDR covers chat on claude.ai, Cowork, third-party MCP servers, or Bedrock, Vertex, or Foundry routes.
  • ZDR is enabled per organization; new organizations require separate enablement by the Anthropic account team.
  • Disabled features such as Claude Code on the Web, Desktop cloud sessions, and `/feedback` are blocked at the backend regardless of client UI.
  • Claude Fable 5 is unavailable under ZDR; the `best` alias resolves to Opus for ZDR organizations instead.
  • Policy-violation sessions may still be retained for up to two years even when ZDR is enabled.

Privacy notes

  • ZDR review discussions often involve account emails, organization names, contract terms, and security architecture details that should stay in internal channels.
  • Claude Code Analytics under ZDR does not store prompts or model responses but still collects productivity metadata such as account emails and usage statistics.
  • Administrative data such as seat assignments and audit logs follow standard retention policies and remain in scope for compliance review.
  • Third-party MCP servers, local logs, hooks, and customer-managed observability stacks are outside Anthropic ZDR and need separate review.

Prerequisites

  • Claude for Enterprise account context and confirmation that Zero Data Retention is being evaluated or enabled.
  • Access to Anthropic account team or sales contact for ZDR enablement, because ZDR cannot be toggled from standard admin settings.
  • Inventory of Claude Code surfaces in use: terminal CLI, Desktop cloud sessions, web sessions, analytics, MCP servers, and third-party model routes.
  • Security, legal, or compliance stakeholders available to review scope boundaries and residual retention cases.

Schema details

Install type
package
Reading time
9 min
Difficulty score
82
Troubleshooting
Yes
Breaking changes
Yes
Source repository stats
Scope
Source repo
Package metadata
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-06-13
Retrieval sources
https://code.claude.com/docs/en/zero-data-retentionhttps://code.claude.com/docs/en/data-usagehttps://code.claude.com/docs/en/legal-and-compliancehttps://code.claude.com/docs/en/analyticshttps://code.claude.com/docs/en/admin-setuphttps://code.claude.com/docs/en/skillshttps://github.com/anthropics/claude-codehttps://developers.google.com/search/docs/fundamentals/creating-helpful-content
Tested platforms
ClaudeClaude CodeCodexCursorWindsurfGeneric AGENTS
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Claude Code zero data retention review capability pack for this organization."

# Required output
1) ZDR eligibility and enablement status summary
2) In-scope versus out-of-scope data flows matrix
3) Disabled feature and model availability assessment
4) Analytics, admin, and third-party integration implications
5) Privacy-safe rollout notes for security and legal review

About this resource

Knowledge Freshness

This capability pack is grounded in Claude Code zero data retention, data usage, legal and compliance, analytics, admin setup, and skills documentation verified on 2026-06-13. ZDR eligibility and feature availability can change with enterprise agreements; prefer live official docs and account-team confirmation over cached policy assumptions.

Retrieval Sources

Source Verification Notes

Verified against official Claude Code zero data retention documentation on 2026-06-13:

  • ZDR is available to qualified Claude for Enterprise accounts and requires separate enablement by Anthropic; it is not toggled from standard admin settings.
  • ZDR covers Claude Code inference on Claude for Enterprise; prompts and model responses are not stored after the response returns except where law or misuse review requires retention.
  • Claude Code on the Web, Desktop cloud sessions, and /feedback are disabled under ZDR because they require storing prompts or completions.
  • GitHub contribution metrics are not available for ZDR organizations; usage metrics remain on the analytics dashboard.
  • Claude Fable 5 is unavailable under ZDR; the best alias resolves to Opus for ZDR organizations.

Scope Note

This is not legal advice. Use it as a reusable review workflow for security, platform, and engineering teams preparing Claude Code rollout under Zero Data Retention on Claude for Enterprise.

Core Workflow

  1. Confirm ZDR status: qualified Claude for Enterprise account, separate enablement by Anthropic, and per-organization scope rather than account-wide inheritance for new orgs.
  2. Map deployment surfaces: terminal Claude Code on Claude for Enterprise, Desktop cloud sessions, Claude Code on the Web, analytics, MCP integrations, and any Bedrock, Vertex, or Foundry routes that follow provider retention.
  3. Document in-scope inference: prompts and model responses during Claude Code sessions on Claude for Enterprise are processed in real time and not stored by Anthropic after the response returns, except where law or misuse review requires retention.
  4. Document out-of-scope flows explicitly:
    • Chat on claude.ai and Cowork sessions.
    • Third-party MCP servers and external integrations.
    • Administrative seat and account metadata under standard policies.
    • Claude Code Analytics productivity metadata without prompt storage.
  5. Review disabled features under ZDR: Claude Code on the Web, Desktop cloud sessions, and /feedback submission, plus any future features requiring prompt or completion storage.
  6. Review model availability: Fable 5 unavailable; confirm /model picker and best alias behavior for ZDR organizations.
  7. Review analytics impact: contribution metrics with GitHub integration are not available for ZDR organizations; usage metrics remain.
  8. Capture residual retention cases: policy-violation sessions retained up to two years under standard ZDR policy.
  9. Produce rollout guidance: approved surfaces, blocked workflows, user comms, and third-party data-handling follow-ups.

Capability Scope

  • ZDR eligibility and enablement workflow review.
  • In-scope versus out-of-scope data flow matrix.
  • Disabled feature and model restriction assessment.
  • Analytics and contribution-metrics limitation review.
  • Third-party MCP and provider-route boundary checks.
  • Privacy-safe enterprise rollout notes.

Compatibility

Native

  • Claude Code / Claude: use as an Agent Skill when preparing enterprise security reviews, admin setup docs, or ZDR rollout checklists.

Manual Adaptation

  • Codex, Cursor, Windsurf, and Generic AGENTS workflows: use the workflow as a deterministic compliance checklist for Claude Code ZDR evaluations.

Required Inputs

  • Organization plan, ZDR enablement status, and Anthropic account contact.
  • List of Claude Code surfaces and integrations currently in use or planned.
  • Required analytics, audit, admin, and collaboration features for the rollout.
  • Known third-party MCP servers, observability tools, and alternate model routes.

Production Rules

  • Do not equate ZDR with zero logging everywhere; local hooks, MCP servers, and customer-managed telemetry remain customer-controlled surfaces.
  • Do not promise contribution metrics or GitHub analytics for ZDR orgs.
  • Block or redesign workflows that depend on cloud session storage or /feedback.
  • Confirm each new organization receives separate ZDR enablement.
  • Document provider-specific retention when using Bedrock, Vertex, or Foundry.
  • Keep legal and security review separate from this operational checklist.
  • Redact account identifiers and contract details in public summaries.

Review Matrix

Topic Under ZDR Action
Terminal Claude Code inference on Enterprise Prompts/responses not stored after response Approved primary surface
Claude Code on the Web Disabled Remove from rollout plans
Desktop cloud sessions Disabled Use local terminal sessions
/feedback Disabled Use internal issue reporting instead
Claude Code Analytics usage metrics Available without prompt storage Enable with metadata review
GitHub contribution metrics Not available Plan alternate ROI signals
Fable 5 model Unavailable Confirm Opus or other allowed models
Third-party MCP servers Out of scope Review each vendor separately

Output Contract

  1. ZDR enablement and organization scope summary.
  2. In-scope versus out-of-scope data flow matrix.
  3. Disabled features and model restrictions list.
  4. Analytics and admin capability impact notes.
  5. Third-party and residual-retention follow-ups.
  6. Privacy-safe summary suitable for security review or rollout comms.

Duplicate Check

Checked content/skills, content/guides, generated catalog text, and open pull requests for Claude Code zero data retention, ZDR review, and enterprise data-handling workflows. Official docs describe ZDR directly, but no skills entry provides a reusable ZDR review capability pack with rollout matrix and third-party boundary contract.

Editorial Disclosure

Submitted as an independent source-backed HeyClaude content entry by kiannidev. It is based on public Claude Code documentation, the public Anthropic claude-code repository, and Google Search Central helpful-content guidance. No paid placement, referral link, affiliate link, or vendor sponsorship is used.

#claude-code#zero-data-retention#enterprise#compliance#capability-pack

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.