What's inside

Speaker lines with a timestamp and mail headers are read as what they are - not as prose. On Android you can share a chat straight out of WhatsApp: unpii opens with the text already pasted in.

3/12/26, 9:14 AM - Julia Ostermann: Can you resend the access details?
3/12/26, 9:16 AM - Ben Krause: Sure, forwarding the email now.

From: Ben Krause <ben.krause@northpark-solutions.com>
To: julia.ostermann@web.com
Subject: Customer portal access

Hi Julia,
here are the access details. Call me at +49 151 22334455 if you have questions.
Best,
Ben

A JSON or CSV body is detected automatically: indentation and keys hold still, only the values are replaced - a hit inside a number is quoted correctly, so the result stays valid JSON. Without structure detection, the same marker lands unquoted and breaks the JSON.

You can also upload files and get them back redacted. Structure and formatting are preserved wherever that is lossless - anything that cannot be carried over cleanly is listed as a warning in the response. Before you download, the review view shows every hit. Supported formats: .docx and .pdf - a PDF comes back as an editable Word file.

Paste the AI's reply back in, markers turn into names again - happens in your browser, the text goes nowhere for this. Across several texts, the same person keeps the same number; that register lives in the tab, not with us.

Hello [PERSON_1],

This confirms your appointment on [DATE_1] at 2pm. If you have questions, reach us at [PHONE_1] or by email at [EMAIL_1].

Best regards

Internal IDs, ticket formats, project names: things nobody knows but you - catch them with your own rules. A rule is a pattern plus a category, testable live before it goes out, and fires reliably before the model has to guess. Start from a ready-made pack or import and export your own as a file. Here: an employee ID the model alone does not recognize.

The rule in this scene: M-\d{4}-[A-Z]

Some hits should stay: your own support address, the hotline, the product name. An allowlist entry protects exactly these terms - everything else keeps getting redacted.

The entry in this scene: support@nordlicht-consulting.com

Instead of [PERSON_1] you can assign your own label per category - useful when a downstream system expects specific placeholders or your documentation has a fixed convention.

The labels in this scene: PERSON → REDACTED-NAME EMAIL → REDACTED-EMAIL PHONE → REDACTED-PHONE

People get invented names instead of markers - the salutation in front of the name is kept. Text only, not files.

Everything here also works via API: text in, masked text plus findings with position, category and confidence out. An inspect-only endpoint reports the same findings without touching the text, and every output carries a signed receipt anyone can verify without us. The request below is the documented format, the response a real result.

curl -X POST https://unpii.me/api/v1/anonymize \
  -H "Authorization: Bearer ak_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Maria Keller (maria.keller@web.de) asked about invoice RECH-2026-4471."}'

{
  "anonymized": "[PERSON_1] ([EMAIL_1]) asked about invoice [ACCOUNT_1].",
  "spans": [
    {
      "start": 0,
      "end": 12,
      "category": "PERSON",
      "id": 1,
      "original": "Maria Keller",
      "score": 0.9981087446212769
    },
    {
      "start": 14,
      "end": 33,
      "category": "EMAIL",
      "id": 1,
      "original": "maria.keller@web.de",
      "score": 1
    },
    {
      "start": 55,
      "end": 69,
      "category": "ACCOUNT",
      "id": 1,
      "original": "RECH-2026-4471",
      "score": 0.9164328575134277
    }
  ],
  "uncertainSpans": [],
  "stats": {
    "request_id": "req-bh",
    "processed_chars": 70,
    "servedBy": "gpu"
  }
}