Tools › Entity types

Redact passwords from text, JSON, and CSV

Passwords have no shape, so this type is inferred from context: a password label followed by a value. It is imperfect by nature, which is why it is worth using alongside a secrets manager rather than instead of one.

How Redactly detects passwords

• Detected from a password or passphrase cue followed by the value; the value must contain a digit or be a credential-style token.
• No format or length assumption is made.
• Rotating anything this catches is still the right response: redaction protects the copy, not the secret.

Why redact passwords?

A plaintext password in a shared log is a live credential, not a historical record.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "DB_PASSWORD=hunter2-prod, host=db.internal.example.com", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Related entity types

• API keysRedact AWS, OpenAI, Anthropic, GitHub, Google, Slack, and Hugging Face API keys from logs and pasted text.
• Private keysRedact PEM private keys, header and body, from logs and pasted configuration before they are stored or shared.
• Login credentialsRedact username and password pairs from pasted transcripts, config files, and support threads.