Redact IMEI numbers from text, JSON, and CSV
An IMEI uniquely identifies physical hardware and survives factory resets, so it links every later owner of that device to the original record.
How Redactly detects IMEI numbers
- Matched by regex for exactly 15 digits, then confirmed with the Luhn checksum used by IMEIs.
- The checksum is what separates an IMEI from an arbitrary 15-digit order number.
- Runs independently of the model.
Why redact IMEI numbers?
IMEI plus a name is a device-ownership record, which is sensitive in warranty, insurance, and law-enforcement contexts.
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": "Replacement approved for IMEI 356938035643809, model SM-A546B.", "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 IMEI numbers automatically?
Yes. Send text to the API and every detected type is redacted, including IMEI numbers. To redact only this type, pass the value device.imei in the entities filter. No training or configuration is required.
What happens to IMEI numbers after redaction?
With style set to replace, each match becomes [device.imei] — 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
- MAC addressesRedact hardware MAC addresses from network logs, DHCP dumps, and device inventories.
- Device identifiersRedact device IDs and installation identifiers from analytics payloads and crash reports.
- IP addressesRedact IPv4 addresses from access logs, error traces, and analytics exports with a format check per octet.
Redact IMEI numbers in production
Get an API key and send your first request in a minute. Plans start at $24/month.
See pricing