Redaction infrastructure
for sensitive data

Built for teams that can't afford to leak a single field.

Private beta · MCP Server is live →
Product preview

Detection
and context

Fifty entity types read the way a person would, not by brittle regex. Every match carries a confidence score you can set a floor on, so review effort goes where the model is unsure.

See how detection works
intake-form.pdfclaims-export.csvonboarding.docxsupport-call.wavid-scan.jpegaccess-audit.logaccounts.json

Alice Johnson

Reached out on Tuesday about the transfer that failed. Best contact is [email protected], or by phone on +1 (415) 555-0142 during business hours.

Account details

The card ending in 1111 (4111 1111 1111 1111) was declined twice, so the payment was retried against GB29 NWBK 6016 1331 9268 19 and cleared the same evening.

Identity was confirmed against 123-45-6789 when the account was opened. The session originated from 192.168.1.42, which matches her registered office.

Audit 12Chat
Redact the financial fields but leave the contact details for the support team.
Done. Four changes staged:
  • Payment card, tokenized
  • IBAN, blacked out
  • Government ID, pseudonymized
  • Contact details, left as they are
Good, but keep the last four of the card so support can match it.
Updated. The card now tokenizes all but the last four digits, and the other three changes are unchanged.
Changes (4)Reject AllAccept All
Describe changes…

Redaction
and masking

Black out, mask, hash, tokenize, or plug in your own anonymizer, per entity type. The same document under the same policy redacts the same way every time.

See redaction options
GOVERNMENT ID · 123-45-6789PII Redaction
blackout
██████████
mask
•••-••-6789
hash
a3f9c1e8
tokenize
‹ssn_8f2a›

Audit
and evidence

Every detection carries its own trail: how it was found, how confidence moved, which conflicts were settled, and under which policy it was redacted.

See the audit trail
PII Redaction12
CONTACT6
PHONE NUMBER+1 (415) 555-014275%
EMAIL ADDRESS[email protected]50%
EMAIL ADDRESS[email protected]METADATA50%
FINANCIAL4
PAYMENT CARD NUMBER4111 1111 1111 111190%
IBANGB29 NWBK 6016 1331 9268 1985%
IDENTITY2
GOVERNMENT ID123-45-678985%
PAYMENT CARD NUMBER
4111 1111 1111 1111
×
Pattern match
credit-card
pattern · 05/09/2026, 00:59:38
30%
Refined
context · 05/09/2026, 00:59:38
65%
Model match
fastino/gliner2-privacy-filter-PII-multi
model · 05/09/2026, 00:59:38
90%
Conflict resolved
vs monetary amount (10%)
structural · 05/09/2026, 00:59:38
90%
Selected for redaction
pseudonymize 1.0.0 · §164.514(b)(1)
pseudonymize · 05/09/2026, 00:59:38
90%

Put it against your own documents

Nvisy is in private beta. Tell us what you need to redact and we will see whether it is a fit.

Security & compliance
GDPR
SOC II
HIPAA