Tools › Entity types

Redact usernames from text, JSON, and CSV

Usernames are pseudonyms that are usually stable, public, and searchable, which makes them identifying in practice even when they are not identifying on paper.

How Redactly detects usernames

• Detected from a username, handle, or screen-name cue followed by the value.
• Captured after the cue with the value taken as written, including the @ form when the label precedes it.
• Email addresses are reported as contact.email instead, since that is the more specific type.

Why redact usernames?

A handle links every public post a person has made, which is often more revealing than their name.

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": "Username: quietriver88, joined the forum in 2024.", "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

• Email addressesRedact email addresses from text, JSON, and CSV with one HTTP call. Returns exact character offsets and keeps your structure intact.
• Profile URLsRedact URLs that point at a person, such as profile, portfolio, and social links.
• Person namesRedact personal names from free text, including partial names the model only half-captures.