Developer identifiers

Redact device identifiers from text, JSON, and CSV

A device ID is a stable pseudonym that follows a person across sessions even after they clear cookies. It is personal data under GDPR when it can be linked back to an individual.

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

Output appears here.

How Redactly detects device identifiers

Detected from a device-ID cue such as device ID, serial, UDID, or IMEI, followed by the value.
Works on UUID and hash-style identifiers alike, because no format is enforced.
A MAC address or IMEI in the same payload is reported under its own more specific type.

Why redact device identifiers?

Persistent device identifiers undermine the assumption that an anonymised analytics export stays anonymous.

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": "Device ID: 8f14e45fceea167a5a36dedd4bea2543, app_version=3.2.1", "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 device identifiers automatically?

Yes. Send text to the API and every detected type is redacted, including device identifiers. To redact only this type, pass the value developer.device_id in the entities filter. No training or configuration is required.

What happens to device identifiers after redaction?

With style set to replace, each match becomes [developer.device_id] — 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 device identifiers in production

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

See pricing