RedactProof VS PrivHaven

PrivHaven's answer:

Two things together. First, your file never leaves your computer: PrivHaven runs in the browser you already have, so there is no upload step and nothing for us to receive, store or lose.

Second, it leaves a record you can check. Pro exports a reproducible, tamper-evident report of what was found in a CSV file and what was done to each column. Anyone holding the original file can re-run our free, open source checker and get the same findings, without using PrivHaven and without trusting us. The report states facts, including what PrivHaven does not detect, and leaves the legal conclusion to your own DPO, auditor or counsel.

PrivHaven's answer:

If you use a cloud scanning service, the file has to be sent to it first. With PrivHaven it is processed on your own machine and never uploaded.

If you already use a tool that runs locally, the difference is the evidence. PrivHaven's report can be re-checked independently by anyone holding the original file, with an open source checker that does not include our engine, so "we scrubbed it" becomes something you can show rather than assert. Detection is checksum-validated for cards, IBANs and routing numbers, and the limits are published, so you know exactly what was and was not checked.

Scanning is free and unlimited with no account, and Pro is $14 per user per month.

PrivHaven's answer:

Small teams and solo practitioners, roughly one to fifty people, who share CSV exports that contain personal data: data and IT teams preparing test or analytics data, finance and accounting staff sending files to a vendor or adviser, and consultants handling client data. The common thread is that they cannot upload the raw file to a cloud tool, and someone may later ask them to show what was removed.

A secondary audience is anyone who wants to scrub a CSV before pasting it into an AI tool.

PrivHaven's answer:

PrivHaven started from a simple gap. Removing personal data from a file is easy to claim and hard to show. A cleaned export usually arrives with a promise that it was scrubbed, and no way for anyone to check.

So we built a scrubber that runs entirely in the browser, so the raw file never has to leave the machine it is on, and made its output checkable. Every run can produce a report that records the file's fingerprint, the exact rules that ran and what was found, and anyone holding the original file can reproduce those findings with an open source checker. We publish what PrivHaven detects and what it does not, because evidence is only useful if its limits are stated.