# PII redactor

Replace emails, phone numbers, card numbers, IP addresses and IBANs in text with placeholders such as [EMAIL].

- Endpoint: `POST https://setget.net/v1/tools/redact-pii` with JSON `{"input": {...}}`
- MCP: `run_tool` with `slug` = `redact-pii`
- Page: https://setget.net/tools/redact-pii

## Inputs

- `text` (required, string): The text to redact.
- `types` (optional, array): Which kinds to redact: email, phone, card, ip, iban. All of them when omitted.

## Example 1

```json
{"input":{"text":"Email sam@example.com or call +44 20 7946 0958. Card 4111 1111 1111 1111, server 192.168.1.10."}}
```

Result:

```json
{"text":"Email [EMAIL] or call [PHONE]. Card [CARD], server [IP].","counts":{"email":1,"phone":1,"card":1,"ip":1,"iban":0},"total":4}
```

## Example 2: Only bank account numbers

```json
{"input":{"text":"Pay GB82 WEST 1234 5698 7654 32 and write to sam@example.com","types":["iban"]}}
```

Result:

```json
{"text":"Pay [IBAN] and write to sam@example.com","counts":{"email":0,"phone":0,"card":0,"ip":0,"iban":1},"total":1}
```

**Will it catch every piece of personal data?** No. It is pattern-based and can miss things. It does not recognise names, postal addresses, dates of birth, national ID numbers or unusually written numbers. Always review the result before sharing it.

**Can it redact too much?** Yes. Any run of 8 to 15 digits can look like a phone number, so order numbers and other long IDs may be replaced with [PHONE].

**How are card numbers and IBANs recognised?** Card numbers are 13 to 19 digits that pass the Luhn check. IBANs must be in capitals and pass the standard checksum, so mistyped ones are left alone.

**Is my text stored?** It is processed in memory to produce the result and not kept. Even so, avoid sending data you are not allowed to share.
