Privacy and security

Inspect before you paste, publish, or hand off.

Use local browser checks to find likely personal data, credentials, tokens, and missing response protections before material leaves your controlled workspace.

Input
Text, logs, headers, JWTs, or a CSV sample.
Processing
Input stays in this browser.
Limit
Pattern matches require human review before release.
Pre-release check

Review the material and the delivery surface.

Use the tools as a screening pass. A clean result does not replace access control, secure storage, contractual review, or context-specific privacy analysis.

01

Scan for personal data

Find likely email addresses, phone numbers, IP addresses, and other common sensitive patterns.

Scan for PII
02

Look for exposed credentials

Check code, configuration, and log text for strings that resemble API keys or private material.

Scan for secrets
03

Inspect sensitive columns

Identify column names and values that deserve review before a table is shared or exported.

Inspect CSV columns
04

Preview redaction

See a proposed masked copy and inspect the context before accepting or publishing it.

Preview redaction
05

Decode JWT claims

Inspect header and payload claims without treating decoding as signature verification.

Inspect a JWT
06

Review response headers

Check whether common browser protections are present in copied HTTP response headers.

Review headers
What happens next

Fix the right layer.

Removing a value from one export does not remove it from source systems, backups, browser history, or access logs. Match the response to where the exposure actually exists.

Before external sharing

Review the exact file or text that will leave the organization, then inspect the proposed redactions for context and completeness.

Before deployment

Remove credentials from source and build output, rotate anything exposed, and verify the replacement configuration.

For recurring control

Move the check into the export, release, or deployment workflow so unsafe material stops before distribution.

Need this enforced on every release?

Elkwai can connect validation, evidence, approvals, and exception handling to a recurring document, data, or software delivery workflow.

Discuss a release control