Offline PII Redactor & Scrubber

Luhn + GB ID + IBAN

Run our offline PII redactor in browser RAM—scrubbing personally identifiable information with Luhn, IBAN Mod-97, SSN, and China ID checksums.

100% Client-Side in Browser RAM · 0 Bytes Uploaded · Try Airplane ModeVerify 0 bytes sent in Network tab

or drop a text or data file here · Ctrl V to paste · or drop .txt, .md, .csv · Ctrl V to paste
  • 0 bytes uploaded — try Airplane Mode
  • Luhn / IBAN / GB ID checksums
  • Live entity count breakdown

Instant Before & After Preview

Luhn / IBAN / SSN / China ID verified
Before (Input)audit-record.txt
Inspector: compliance@example-bank.org · Host: 10.24.88.14
Citizen ID: 110105199003070017 · EIN: 12-3456789
IBAN: DE89 3704 0044 0532 0130 00 · Card: 4532-0151-1283-0366
After (Output).txt
Inspector: [[EMAIL-01]] · Host: [[IP-01]]
Citizen ID: [[ID-01]] · EIN: [[TAX-01]]
IBAN: [[IBAN-01]] · Card: [[CARD-01]]

How it works

How to scrub PII from text without uploading files

Validate real identifiers with cryptographic and modular checksums so version strings and random numbers never trigger false alarms.

  1. Drop or paste raw textLoad customer exports, support tickets, or compliance notes straight into browser memory.
  2. Inspect color-coded entity badgesReview category totals (EMAIL, TEL, CARD, IBAN, ID, KEY) and toggle any custom name or alias to redact globally.
  3. Copy redacted output or restore laterCopy the sanitized text, or keep the RAM session open (or export .redactkey) to reverse AI responses later.

FAQ

Frequently asked questions

How does PII Redactor avoid false positives on version strings or random numbers?

Every card number must pass Luhn, IBANs pass ISO 7064 Mod-97, China IDs pass GB 11643-1999 Mod-11 plus calendar birth validation, and version strings like v1.2.3.4 are ignored.

Does PII Redactor download any 100 MB AI model in the background?

No. It runs purely on deterministic TypeScript validators and custom entity matching under 30 KB with zero external model downloads or API calls.

Can I bind aliases like full company name and short name to one token?

Yes. Enter comma-separated aliases alongside the canonical name and longest-match-first sorting binds all variants to the same [[ORG-01]] token.