Tools › Entity types

Redact login credentials from text, JSON, and CSV

A username alone is low risk and a password alone is high risk; the pair is what lets someone sign in. Redactly reports the combined credential block when the text presents it as one.

How Redactly detects login credentials

• Detected from a login or credentials cue, including inline User: and Pass: pairs inside the value.
• Does not assume a separator: works for colons, equals signs, and plain prose.
• A password the model also flags is reported separately as credential.password.

Why redact login credentials?

Credentials in a support thread are usable immediately, by anyone with access to that thread.

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": "Login credentials — User: jdoe88 Pass: Spring2026", "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

• PasswordsRedact plaintext passwords from configuration dumps, tickets, and transcripts before they are shared.
• UsernamesRedact handles and account usernames from transcripts, exports, and community data.
• API keysRedact AWS, OpenAI, Anthropic, GitHub, Google, Slack, and Hugging Face API keys from logs and pasted text.