Using Payload Guard carefully

What it checks

The tool first validates JSON syntax. It then checks field names commonly used for passwords, API keys, access tokens, session identifiers, email addresses, and similar sensitive values. Safe-copy mode replaces matched values with labelled redaction markers while leaving the surrounding JSON structure readable.

A practical review workflow

1. Paste only the smallest payload needed for the task.
2. Select Inspect & format and correct any JSON error.
3. Review each detected item and its location.
4. Keep safe-copy mode on, copy the sanitized result, and inspect that copied result once more before sharing.

What it cannot prove

Pattern matching is not a security guarantee. An unfamiliar credential format, a secret stored under an ordinary field name, or sensitive business context may not be detected. Harmless values can also match a rule. Payload Guard does not revoke exposed credentials, inspect attachments, assess who should receive the data, or replace access control and security review.

Local processing and measurement

Formatting, inspection, and redaction happen in your browser. The application may record only fixed aggregate events such as tool open, validation error, or successful safe copy; the JSON, detected values, output, field names, and clipboard contents are not included.

If a real secret was exposed

Remove the shared copy where possible, rotate or revoke the affected credential with its provider, review access logs, and follow your organization’s incident process. Sanitizing a later copy does not make an earlier disclosure safe.