Tools › Entity types

Identity and government IDs

Redact person names from text, JSON, and CSV

Names have no format, no checksum, and infinite variety, so this is the type that depends entirely on the model. Redactly extends each span across the whole word so you get Jane Doe, not just Doe.

Try it on the live API No signup. 2,000 characters, 20 runs per 10 minutes.
Output appears here.

How Redactly detects person names

  • Detected by the model and then extended across contiguous word characters so partial surnames are completed.
  • Works on non-Latin scripts, where a two-character name is a full token rather than a fragment.
  • Company and organisation names are reported separately as org.company_name.

Why redact person names?

A name is the join key that turns an anonymous record into an identifiable person.

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": "Account owner Jane Doe requested a statement reissue.", "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

Does Redactly redact person names automatically?

Yes. Send text to the API and every detected type is redacted, including person names. To redact only this type, pass the value identity.person_name in the entities filter. No training or configuration is required.

What happens to person names after redaction?

With style set to replace, each match becomes [identity.person_name] — the entity type in square brackets. Setting style to mask replaces every character with a block character, and remove deletes the span entirely.

Related entity types

Redact person names in production

Get an API key and send your first request in a minute. Plans start at $24/month.

See pricing