Tools › Use cases

Use case

Redact data before sharing with vendors

Vendor due diligence and incident response both start with sending data to someone outside the company. The fastest safe option is to send a redacted copy and describe what was removed, rather than to negotiate a data processing agreement for a one-off review.

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

What this gives you

  • Returns exact character offsets, so you can log which spans were removed without storing the values.
  • The response lists every entity found, which doubles as the record for your vendor file.
  • Style and threshold are per request, so a stricter pass is one field away.
  • Nothing is retained server-side, so the redacted copy is the only copy that leaves.

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": "Contract with Northwind Trading Ltd, signed by Priya Raman, priya@example.com", "threshold": 0.4}'

Questions

Can I lower the threshold for a stricter pass?

Yes. The threshold is per request between 0 and 1, default 0.5. A lower value keeps more borderline detections.

Do you keep a copy of what I send?

No. Request bodies are redacted in memory and not written to storage.

Related