What to check for
- Credentials
- Access tokens
- Network identifiers
- Personal support contacts
Developer log sanitisation
Remove secrets from logs before sharing them with AI.
SanitiseAI helps developers clean stack traces, deployment logs, support payloads, and environment snippets before sending them to AI tools, vendors, or public issue trackers.
What to preserve during review
- Error messages
- Sequence of events
- Service names where safe
- Debugging context
In practice
A worked example
Synthetic input and expected readable output. This small example demonstrates one replacement, not complete coverage. Try it in the tool and review the result.
01 / Source text
Deploy failed: password=ExampleOnly_42! upstream timeout; retry after backoff.
02 / Expected output
Deploy failed: password=[Secret 1] upstream timeout; retry after backoff.
Follow the workflow
- Use a minimal failing log excerpt, not a full environment dump.
- Keep secret detection enabled and review credentials, connection strings and embedded payloads.
- Rotate any real credential already exposed. Redacting a later copy cannot revoke a leaked secret.
Put the workflow into practice.
Start with an example. Review every result before sharing.