Check Data Handling before Using Matter Material
Decide which material may enter the chosen tool and record the unresolved access or processing questions.
What changed since this was written
- Claude Code: inspect diagnostic records before sharing
Claude Code 2.1.274 and 2.1.275 fixed cases where connection errors and plugin records could display access tokens or passwords. Updating does not remove information already saved or shared.
Recommended action: Ask IT to apply an approved release containing these fixes. Before sending logs or screenshots to support, check for credentials and matter details. If a credential may have been disclosed, stop sharing the record and follow your organization’s incident process with the security team.
Sources: Claude Code 2.1.274, Claude Code 2.1.275
- Computer History can record activity beyond your chat
This optional macOS feature saves app and website activity as memories and a timeline. At launch, it excluded the EEA, UK and Switzerland; access also depended on plan and workspace settings.
Recommended action: This feature can record activity across apps and websites, so get your organization’s approval before turning it on. Check which apps and sites are excluded, how to pause recording and how to delete saved activity. Try it without client material first; permission to use chat does not cover background recording.
Sources: ChatGPT / Codex
- Record & Replay became available in more European countries
The July rollout added the EU, UK and Switzerland. Record & Replay still required macOS and an enabled Computer Use feature; the announcement did not cover other recording features.
Recommended action: If you want to record a task for later reuse, first check that Record & Replay is available and approved in your workspace. Practise with a made-up document and watch the recording for unintended content before reusing it. This announcement does not establish availability of the separate Computer History feature.
Sources: ChatGPT / Codex
- Material under review must not become the reviewer’s instructions
Codex Action guidance clarified that instruction files inside proposed changes are untrusted material, even when named
AGENTS.md.Recommended action: If your team uses AI to review GitHub changes, ask the maintainer where its trusted instructions come from. Review instructions inside submitted files as content, not commands to follow.
Sources: Codex Action PR instruction security clarification, Claude Code Action simplified prompt guardrails, Claude Code Action non-user actor handling
- GitHub can check for exposed access keys before changes are shared
GitHub made scanning through its connected tools generally available for repositories with Secret Protection enabled.
Recommended action: Ask your maintainer to scan proposed changes for passwords and access keys before sharing them. A clean scan does not mean the files are free of confidential client information.
Sources: GitHub MCP Server secret scanning GA, Claude Code GitHub Actions, Claude Code hooks
Before pasting text, uploading a file or connecting a source, identify the matter, purpose, tool, account or workspace, and people who will receive the output. Use synthetic material while these arrangements are unresolved. Approval for one product or plan does not establish approval for every feature or external service.
Checks before use
-
Confirm your organization’s authorization for this use, including any client or matter restrictions. Check the applicable provider terms and actual settings for processing, retention, training use, access and connected services. Record the source of each answer and unresolved questions for the responsible privacy or security reviewer.
-
Supply only material needed for the task. Check images, attachments, comments and metadata as well as visible text. Replacing a name may leave identifying context; do not call a document anonymous merely because direct identifiers were removed. Keep any reidentification key separately with restricted access. ICO (UK)
-
Confirm the output’s intended recipient and storage location before sharing. Record what was supplied, the relevant account or workspace, the review decision and remaining restrictions under your organization’s recordkeeping rules. If an unauthorized disclosure is suspected, stop the affected activity and follow the actual incident process.
Synthetic worked example and correction
Synthetic example: a test file uses “Person A”, but its comment contains the original name and its text identifies the only surgeon in a small village. The reviewer withholds that file, prepares a genuinely synthetic replacement for testing and checks comments and context. A pseudonym alone did not settle the disclosure decision.
Review screen and activity capture separately from chat. For Computer History or Record & Replay, check current regional and workspace availability, what apps or sites can be captured, and the actual pause and deletion controls. Test with synthetic activity and inspect the saved record before reuse. Leave capture disabled while its scope or authorization is unresolved. OpenAI
For Claude Code, ask IT to apply an approved release containing fixes for credentials appearing in diagnostic records. Before sending logs or screenshots to support, check for credentials and matter details. If a credential may have been disclosed, stop sharing the record and follow your organization’s incident process with the security team. Claude Code