Tools › Entity types

Redact profile URLs from text, JSON, and CSV

URLs are ambiguous: a documentation link is harmless and a personal profile link is not. Redactly reports every http and https URL so you can decide, rather than leaving the decision to a guess.

How Redactly detects profile URLs

• Matched by regex for http and https URLs.
• The full URL is the span, including path and query string, because the path is often the identifying part.
• Runs independently of the model.

Why redact profile URLs?

Profile URLs frequently contain a real name or handle and resolve to a public page about the 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": "Applicant portfolio: https://example.com/people/jane-doe", "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

• UsernamesRedact handles and account usernames from transcripts, exports, and community data.
• Email addressesRedact email addresses from text, JSON, and CSV with one HTTP call. Returns exact character offsets and keeps your structure intact.
• Person namesRedact personal names from free text, including partial names the model only half-captures.