PDF PII Redactor — Remove Personal Data, Not Just Cover It avatar

PDF PII Redactor — Remove Personal Data, Not Just Cover It

Pricing

Pay per event

Go to Apify Store
PDF PII Redactor — Remove Personal Data, Not Just Cover It

PDF PII Redactor — Remove Personal Data, Not Just Cover It

Finds emails, phone numbers, SSNs, card numbers and more in a PDF and deletes them from the file, then draws the black box. Verified after saving: if the text is still extractable, the document is not charged.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Austin Cooley

Austin Cooley

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 days ago

Last modified

Share

PDF PII Redactor — actually remove personal data, not just cover it

Finds emails, phone numbers, Social Security numbers, credit card numbers, IBANs, IP addresses and dates of birth in a PDF, deletes them from the file, then draws the black box.

The difference that matters

Most tools that call themselves redactors draw a black rectangle over the text and save the file. The words are still there, in the content stream, underneath the box.

Select-all and copy gets them back. So does pdftotext. So does any PDF parser written in the last twenty years. Real documents have been leaked exactly this way — including court filings, published with "redacted" names that anyone could recover by dragging a cursor across them.

This Actor uses PyMuPDF's redaction annotations, which remove the glyphs from the page before the box is painted.

Then it checks. After saving, the output is re-opened and re-parsed. If any of the text we claimed to remove is still extractable, the document is marked failed and you are not charged for it.

What it finds

TypeNotes
Email addresses
Phone numbersRequires separators or a country code, so bare invoice numbers survive
US Social Security numbersNNN-NN-NNNN
Credit card numbersLuhn-checked — real cards pass, order numbers almost never do
IBANInternational bank account numbers
IP addressesIPv4, correctly bounded so version strings are not eaten
Dates of birthMM/DD/YYYY
Anything elseSupply your own regex — employee IDs, case numbers, internal references

The patterns are deliberately conservative. A false positive silently destroys real content in someone's document, which is worse than a miss they can catch by reading it.

Pricing

Charged per page that actually had something redacted. A 60-page contract with personal data on 3 pages costs 3 pages, not 60. Pages we did not touch are free — which means the work of finding the matches happens before anything is billable.

Nothing is charged for a document that fails, or for one whose redaction could not be verified.

Output

Each document returns a signed link to the redacted PDF, the page counts, a breakdown of what was found by type, and the verification result.

What it is not

It does not do face blurring, image redaction, or handwriting. It does not find names or street addresses — those need a language model and produce false positives that quietly delete the wrong words. If you need those, this is the wrong tool and I would rather say so here than take the run.

Scanned documents with no text layer have nothing to search. Run them through Searchable PDF OCR first, then through this.