# Claude Code account and policy approval

Pair the actual sign-in arrangement with applicable training, retention and code-use decisions.

Dated provider categories plus a fictional decision scenario. No real account, agreement or approval is verified.

Source: https://aona.ai/resources/guides/claude-code-personal-commercial-data-policy/
Sources checked: 2026-09-21

| Category | Dated documentation | Review implication |
| --- | --- | --- |
| Consumer, improvement allowed | Five-year retention described | Employer permission still required |
| Consumer, improvement disabled | 30-day retention described | Confirm actual preference and task |
| Commercial standard | No training absent opt-in; standard 30 days | Confirm agreement and provider route |
| Qualified ZDR | Specific enablement required | Do not infer it from plan name |
| Feedback report (/feedback) | Five-year path, including /bug and /share | Review the exceptional upload |

## Review checklist

- [ ] Verify the session’s account and provider
  Use administrative evidence, not an application logo or a copied API key.
- [ ] Separate standard terms from exceptions
  Record any opt-in, retention variation and covered feature explicitly.
- [ ] Record permitted code and recheck triggers
  Keep feedback sharing and local file permissions as linked decisions.

## Included example files

- README.md
- account-review.csv
- code-use-decision.md
- documented-account-categories.csv
- fictional-account-decision.md

## Source references

- Claude Code: Data usage: https://code.claude.com/docs/en/data-usage (2026-09-21)

Use the worksheet within the relevant legal, contractual and technical scope. It is not a certification or a record of an installed-product test.