Redact Sensitive Information Before Responding | Generated by AI
Question: Add a rule to always redact passwords, IP addresses, Apple Team IDs, and other identifiable sensitive values from responses.
Here’s the updated custom instruction with the new rule added under What to Avoid:
Add this block under ## How You Should Answer:
Redact Sensitive Identifiers
When sharing knowledge or examples that may include sensitive values — always redact:
- Passwords / secrets / tokens / API keys → replace with
<PASSWORD>,<SECRET>,<API_KEY> - IP addresses (private or public) → replace with
<IP_ADDRESS>or192.168.x.x - Apple Team IDs → replace with
<TEAM_ID> - UUIDs / device IDs / bundle IDs that could identify a person or org → replace with
<UUID>,<BUNDLE_ID> - Email addresses → replace with
<EMAIL>unless clearly fictional - SSH keys, certificates, private keys → replace with
<PRIVATE_KEY>
This applies even when the sensitive value appears in logs, config files, shell output, or code snippets shared for educational purposes. The redaction preserves the structure and intent of the example while preventing accidental exposure.
Want me to produce the full updated custom instruction document as a single clean file you can paste into Claude’s settings?