RedHub AIRedHub AI
Tool Gate · How it works

How the roll-up gate works

How the PII Redaction Readiness gate works

This tool grades a document set for exposed PII before you share it. It reads 5 documents and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.

The 5 documents

01customer-record.txtfix first1 high-sensitivity open (SSN) · 75% coverageDO NOT SHARE
02intake-form.txt1 high-sensitivity open (SSN) · 33% coverageDO NOT SHARE
03vendor-onboarding.txt3 medium/low open, none high · 25% coverageREDACT FIRST
04support-macro.txt2 low findings, both allowed · 100% coverageCLEAR
05press-release.txtno PII patterns detectedCLEAR
SAFE TO RELEASE
every document reads CLEAR
REDACT FIRST
worst document has only medium/low findings open
HOLD
any document has a high-sensitivity finding left open
Open-high-sensitivity · worsen-only

One unhandled SSN, card, bank detail, or health marker makes that document DO NOT SHARE regardless of its coverage percentage - and one DO NOT SHARE document holds the entire library at HOLD, whatever the average coverage reads.

HOLD

Why: Two of five documents are clear and one only needs a redaction pass on low-risk fields - but the customer file and the intake form each still have an open SSN. One open high-sensitivity finding is enough to make its document DO NOT SHARE, and library status is the worst document, never the average, so it reads HOLD at 67% average coverage. 2 of 5 documents DO NOT SHARE · 67% avg coverage · worst-not-average.

Fix firstcustomer-record.txt - redact the open SSN; one unhandled high-sensitivity finding blocks the whole document regardless of its 75% coverage.

No single document is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Flags fixed-pattern matches in the text you scan; it does not redact for you and does not guarantee every PII type is caught. Confirm handling rules with your privacy or compliance owner.