Contact details

Redact IP addresses from text, JSON, and CSV

Under GDPR and most privacy regimes an IP address is personal data. It is also the field most often left in a log paste when a customer sends you a stack trace.

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

Output appears here.

How Redactly detects IP addresses

Matched by regex with every octet validated to the 0-255 range, so version strings and dates do not match.
Runs independently of the model, which means an address in an otherwise empty log line is still found.
The pattern covers IPv4, with every octet validated to the 0-255 range; IPv6 strings are left to the model.

Why redact IP addresses?

Logs are routinely pasted into tickets, chat, and LLM prompts, carrying user IPs with them.

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": "2026-10-26T09:14:02Z client 203.0.113.47 GET /v1/redact 200.", "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 IP addresses automatically?

Yes. Send text to the API and every detected type is redacted, including IP addresses. To redact only this type, pass the value contact.ip_address in the entities filter. No training or configuration is required.

What happens to IP addresses after redaction?

With style set to replace, each match becomes [contact.ip_address] — 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 IP addresses in production

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

See pricing